Hello Andreas,
Fink, Andreas wrote: > > Improving the documentation is for sure the first step :) > Right, I openend up a bug report for doing so. http://bugzilla.qooxdoo.org/show_bug.cgi?id=3875 Fink, Andreas wrote: > > Maybe you should look at it from another perspective: > Looking at the property description of model in the API tells us: > "Model property for storing additional information for the including > object. It can act as value property on form items for example." > Why it shouldn't be possible to have more than one item with the same > ADDITIONAL information (it could have other information, the label, some > userData, etc.), except of, it hits a "bug" in the framework? > Or in the documentation. ;) Fink, Andreas wrote: > > I only thought, maybe the framework could be improved a little bit, by > finding a way of working with such a construct or if there is no way, > could give a better support to the developer by not accepting things that > for sure end up in an hard to track bug. > Thats generally what we are trying to do. But in this case its hard to get that done because the list item has no connection to all the other list items. So only the container (select box e.g.) knows its children. That means that I need to attach (and remove) listener to all model property in the containers children and react on changes. This is way too much overhead for an edge case and a warning. Regards, Martin -- View this message in context: http://qooxdoo.678.n2.nabble.com/Discussion-for-ListItem-SelectBox-improvements-tp5296939p5310978.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
