Krycek wrote: > > I don't think this advantage should be restricted to those using the form > object. It's the kind of thing that is useful everywhere, so it should be > part of the widget itself. Like a "modelPath" property in the list > controller as was suggested in another thread. >
Sure, I don't mind. But the advantage of the approach I suggested would be that you could re-use the widget in different forms with a different "modelPath". I don't know how realistic this use case is, but it somehow seems more "logic" to me to have the form controller determine what is useful for the form instead of the widget itself - which, it seems to me, should be agnostic about the data it contains. --- After all, it is the FORM which is interested in the data, not the widget. But I don't really care too much, as long as the solution frees me from having to write redundant code. Cheers, Christian -- View this message in context: http://qooxdoo.678.n2.nabble.com/Databinding-problem-Creating-form-model-stopped-working-tp5314091p5317524.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
