Hello Jamie, such a use case is not covered by the framework itself. But I have an idea on how to get this nicely. You can write your own form renderer which takes all possible input fields on startup. The renderer offers one (or more) property(s) which define the "state" of the renderer which means which of the input elements should be shown. This state propertie(s) can be bound to the selection of your list for example which changes the visibility of the input fields. Thats the part for the UI, but you still have all the data in the model. Is that a problem? Regards, Martin -- View this message in context: http://n2.nabble.com/Dynamic-Forms-tp4920231p4923849.html Sent from the qooxdoo mailing list archive at Nabble.com.
------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
