Hello Andreas,
Fink, Andreas wrote: > > If the model property of the ListItems is necessary for the SelectBox to > work,... > It is only necessary if you want to use the model selection. If you don't care about the model selection and the whole data binding stuff, you can just go without the model property. Fink, Andreas wrote: > > ... I think it should check this property for uniqueness and throw an > exception or at least gives a warning. > The current implementation only has references from the list to the list items which means we can not check with one list item if the model is unique. Thats a task the list would have to do but i'm not sure whats the benefit of that. Usually the model property is set by the binding controller which is in charge of that. Fink, Andreas wrote: > > Another idea is to set the model property of the ListItem to the label > value by default (if no model is provided during constructor call to also > allow null to set). I think this wouldn't break existing code and increase > the usability of both widgets. > Hm, I am not sure about that. In the first place, this sounds not a bad idea but somehow I have a bad feeling about it. Maybe its because I don't see the problem you are trying to solve with that. Maybe you can explain a little bit whats the problem with not having a model set. Regards, Martin -- View this message in context: http://qooxdoo.678.n2.nabble.com/Discussion-for-ListItem-SelectBox-improvements-tp5296939p5297450.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
