Hi Martin, you're right that's too much overhead. Another idea and I promise it's the last one to not let us end up in a personal war about this topic. :D
Is it possible to catch the "too much recursion" exception inside the List and give a better exception description if the problem relies to duplicated models? Maybe a model property check in the catch block with a simple loop through all ListItems could then throw a more specific exception, something like "Duplicated model found. The model property of each List item has to be unique." A better documentation would for sure give the most developers the ability to find the solution their own and would decrease the numbers of questions on the mailing list. So that's a good way to go :) Regards, Andreas P.S.: By the way, a big compliment to you and the other persons of the support team. Somewhere else such threads would be marked as not worth discussing. -----Ursprüngliche Nachricht----- Von: MartinWittemann [mailto:[email protected]] Gesendet: Montag, 19. Juli 2010 09:23 An: [email protected] Betreff: Re: [qooxdoo-devel] Discussion for ListItem/SelectBox improvements 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 ------------------------------------------------------------------------------ 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
