If we don't keep classic navigation, it doesn't seem like the new filter provides much (other than a little simplification) and muddies up xmlDataSource and other dataSources.
If we do keep classic navigation, then the documentation needs to explain when filter, whereClause, orderBy, sqlFilter, whether other dataSources can be used, and what combination of the these attributes can be used together. That is not a problem I think -- we would just need to lay it out in a chart.
The issue I believe is classic navigation.
1) do we need to keep it
2) can we keep it along side the new navigation system
3) will we be giving up flexibility in modifying the new system by trying to maintain the classic system
If the new filter can be made compatible with other DataSources, then it seems like that would be the best and that whereClause, and perhaps filter attributes could be depriciated for the sake of simplicity.
-- Shawn
Happily using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ DbForms Mailing List
http://www.wap-force.net/dbforms
