I have a question that has to do with API changes in the upcoming 0.8.3 release.
First, I would like to ask you to explain the reason why the "value" property of qx.ui.form.ListItem was deprecated in favor of using the userData property. To my mind, this makes a lot of things more complicated without gaining anything. I think there are good reasons that a ListItem, just as an <option> tag in HTML, has a label and a value. This is especially useful for a multi-language application where the labels can have arbitrary content, which, however, always correspond to a non-changing "value" which has the "real" meaning to the application. This also concerns the vanishing from such useful methods as qx.ui.form.List::findByValue() or the possibility that single-selection widgets such as the SelectBox, have a "value" - saving the developer to have to iterate through all the list box elements by hand and selecting one that corresponds to a specific value. Of course, I can always write my own widgets which implement this behavior. However, I don't see a good reason why the core framework makes things more difficult than it needs to be in this respect. Maybe you can enlighten me ;-) Cheers, Christian -- View this message in context: http://n2.nabble.com/deprecation-of-value-property-of-qx-ui-form-ListItem-SingleSelection-issues-tp3525628p3525628.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
