Hi Jared. > Since the SelectBox widget can only ever have a single value selected, > shouldn't the SelectBox object override getSelection() such that it > returns a single value only and not always a one element array? The current getSelection() is coherent with the rest of the selection API, and IMHO it is fine. This way when you want the selection of a widget, you don't have to ask yourself "Do I get an array or do I get one widget ? Let's go check the doc". Furthermore, you can implement generic algorithms which retrieve the selected elements of several different widgets. Having a different return type would make it necessary to check the classname of the widget.
> I suitable default > behavior like initializing the model to the label value upon creation > would also make an immense amount of sense, no?! I agree with that. That would just be a "shorcut" for people have the same label and model properties values. But maybe some people want their model property set to "null" ? That would also be great to be able to initialize the model property in the constructor, instead of the deprecated value property. -- Loïc Bresson ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
