About the discussion about "classic" mode versus "datalist" mode, some days ago I've posted a src code in which I rearrange the calls to classic inside the datalist structure. I've thinked a lot about it, and I'm not so sure that this is the right way. IMHO we must say clearly that the datalist approach have several benefits, but its only drawback make it unusable for a quite large application areas. So what can we do here?
- drop classic and focus on datalist, hoping this problem can be resolved: IMHO definitely no no, as for now I can't see a way out
- reorganize to better fit classic versus others: the way we've walked 'til now
- try to reengineer classic, removing that code from Table class and fit it in a way like datalist do. This may have many benefits, since classic is very coupled with other codes. Obviously we need deep informations on how it work. So I agree with Luca's works about documentation.
say this, me too on holydays til 9/9 (maybe I'll find Henner somewhere ;)
cheers, -- Sergio Moretti
------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 _______________________________________________ DbForms Mailing List
http://www.wap-force.net/dbforms
