On Tuesday 22 December 2009 12:24:32 i...@saksys.de wrote: > in 1.0 you deprecated may functions. I think i understand why. You're > trying to homogenise all functions. > So e.g. you changed .getSelected() method to .getSelection() for Tabviews, > but why you dont allow to you .removeAll() in container.Scroll but in > container.Composite? Because only one child can be inserted at the scroll container and "removeAll" would be misleading here.
> I know Scroll containers just can have one widget, but Tabviews can have > just one selected page also. Selection and child widgets are different things. A widget like the tabview can have multiple child widgets, but only one that is actually selected. That's the reason why the API is separating these two concepts. cheers, Alex ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
