Hi Martin, Improving the documentation is for sure the first step :) Qooxdoo does a great job, preventing developers of wrong API usage (type checks, allowed values, etc.) and I'm only talking about the SelectBox (or depending widgets) at the moment.
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? I absolutely confirm with you that the frameworks provided functionality is good enough for, let's say "every" use case. 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. Regards, Andreas -----Ursprüngliche Nachricht----- Von: MartinWittemann [mailto:[email protected]] Gesendet: Freitag, 16. Juli 2010 10:08 An: [email protected] Betreff: Re: [qooxdoo-devel] Discussion for ListItem/SelectBox improvements Hey, Hm, so you are saying that the framework should prevent or warn on every wrong usage of the API no matter where in the framework? Thats a lot of work to do only for the cases someone is using the API in a way not intended, especially if there is no real use case for using the API this way. I think a hint in the documentations saying how to use the API should be enough. Regards, Martin -- View this message in context: http://qooxdoo.678.n2.nabble.com/Discussion-for-ListItem-SelectBox-improvements-tp5296939p5300909.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
