Hi Shawn ! > 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.
I think it's better to have only a navigation system, and we could use the force (Luke) to debug / improve it. I watched the new navigation system and I think it's easier to maintain / understand / improve. IMHO. Maybe I'm wrong... ;^) > The issue I believe is classic navigation. yes > 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. maybe it could be possible to have a flexible filter engine: we could use a "filter" and "filterType" attribute to specify the filter condition and the filter engine. The default filter could be the current one (with "cumulation of rules"), but we could use a filterType="sql" and we could set filter with a SQL string... Not the easiest thing to do, anyway. So we could keep the "filter", "filterType" and "orderBy" attributes and remove "whereClause" I never worked with filter stuff, so I don't know if it's possible to make a refactoring of the filter engine. > Shawn Luca ------------------------------------------------------- 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
