Hello Christian, I guess you did get something wrong in that change. We did not deprecate the value property on list items in favor of using userData. We removed the value property completely. If you want to have such kind of functionality, you are free to use the userData but it was not intended by us that everyone should use it instead of the value property.
One reason for removing the value property is already in your question. You said that a label is not enough and thats what we think too. But we also think that a second string storing a "pseudo value" is also not enough. In some cases, there are objects, related to that list item, in other cases, there are numbers related and so on. Maybe its enough in HTML but we are an application framework. But you are not the first one who is not that happy with that change. So we just decided to revert that change but remove the restriction of a string. That way, I can also use the value property in the data binding as well. http://bugzilla.qooxdoo.org/show_bug.cgi?id=2733 Regards, Martin panyasan wrote: > > 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-tp3525628p3533655.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
