Hey,
Thanks for the details on this. Creating the form and controller based on a
JSON schema is kind of an edge case I think but still an interesting task.
Using selections in forms is always a problem because we now have two
models. On one hand, we have the model which holds the data for the options.
On the other hand, we have the selection which should be one or more (in
case of multi selection) items of the options model. If we now want to
select something of the selection, we need to use exactly the same model
object we use in the list. With primitive types this is easy because "12" ==
"12", no matter where it comes from. But when it comes to objects, you sure
know that ({}) != ({}) which brings up the problem here!
The thing you doing with the id is breaking up the structure of the
selection handling using always the same object by adding a primitive
placeholder for that object. This could be interesting but also irritating
in some ways. Sure it would be much easier in your scenario but I try to
think of all other scenarios...
I think we already have a bug for that:
http://bugzilla.qooxdoo.org/show_bug.cgi?id=3668
Do you think that could also solve your problem?
Regards,
Martin
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/Form-Binding-with-List-Binding-tp5121281p5296172.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
