Howdy! On Wed, 2007-03-07 at 10:10 +0100, Til Schneider wrote: > [EMAIL PROTECTED] schrieb: > > Sebastian Werner <[EMAIL PROTECTED]> writes: > > > >> Generally, before you start, I don't like the current structure because it > >> mix widgets with other features. The original intention for the "ui" > >> folder > >> was to contain widgets (only). The table use some special stuff like > >> models > >> and a custom selection manager. Maybe we can move the stuff which is not a > >> widget and integrate it with the other folder structure. > >> > >> e.g. > >> > >> *Model -> qx.model.* > >> *Renderer* -> qx.renderer.html.* > >> SelectionManager -> qx.manager.selection.* > >> etc. > > > > Your logic for this is perfectly reasonable. When actually working on the > > stuff, however, that gets very difficult to deal with -- especially for > > someone learning to work on qooxdoo. Having everything pertaining table > > (for > > example) in the same hierarchy makes it considerably easier to find what > > you're looking for. I guess my contention would be that all of this > > pertains > > to the table widget (part of the UI) and therefore is logically in the same > > namespace. I'd sure hate to split this up and make it even more difficult > > than it already is to find where changes need to be made (or even how > > something works). I've been actively working with Table for a couple of > > months now, and I still do lots and lots of grepping through the source to > > find what I'm looking for. Having it all over creation would make finding > > things a lot more difficult. > > I agree with you, Derrel. The table related models and renderers are in > such a manner special that it makes no sense using them for other > widgets as tables. Therefore it would be no advantage putting them > outside the table package. In contrast it would make things a lot more > complex, since it would be very difficult to determine the classes that > work together with a table.
Just did a grep through treevirtual and got 16 matches for the qx.ui.table namespace. I would also suggest to reconsider moving those parts out of the table namespace that are of some general interest to other widgets/parts of the system. Maybe something appears to be quite table-specific at first, but could be of more general use? Of course, you certainly have a much better idea of all the table stuff, so do what is best for further development of the table, Andreas ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
