> Some things, though, can't easily be changed. Most of the changes you are > suggesting would not be backward-compatible, meaning all of the code that > uses those widgets would have to change. The long-term goal is for Table > to > be obsoleted by a new member of the qx.ui.virtual.* family (not yet > written). Although the new virtual table will likely come into existence > within the next year, it will still be a number of years, probably, before > qx.ui.table.* can be dropped completely from the framework in favor of the > new widget, again for backward-compatibility reasons. The current Table > widget is given love and attention to ensure that it continues to work > properly and serve its function, but making significant changes to its API > is probably inappropriate at this point.
I'm not so sure. Especially given the perspective that the current Table will continue to be used for some time might merit careful changes to the API. Nobody wishes for API changes, but we have successfully managed those in the past, so existing applications could be migrated with reasonable effort. And there is probably still new code being written using the Table class. Nick, why don't you collect your findings in a bug. This is the best means of fueling them into our development process. It doesn't mean they get implemented any time soon, but they will be considered and are documented for the time where API changes are deemed appropriate. T. ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
