On Fri, 28 Aug 2009, MartinWittemann wrote: > 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
That's the way to go, cool! Cheers, Fritz -- Oetiker+Partner AG tel: +41 62 775 9903 (direct) Fritz Zaucker +41 62 775 9900 (switch board) Aarweg 15 +41 79 675 0630 (mobile) CH-4600 Olten fax: +41 62 775 9905 Schweiz web: www.oetiker.ch ------------------------------------------------------------------------------ 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
