Hi, I know I'm waking up a long discussion which has come to rest for a while now, but as I encountered the situation again, I thought I might try to maybe express the concern / idea / problem in a different way which might yield a solution.
As far as I understand, the problem comes from two different uses of a list widget. The first usage is as a standalone widget which offers the user options. For this use it is convenient/important to save meta-information related to the selected option, which later plays a functional role in the program. The second use is as a part of a form, where a selection of an item in the list can (and should) be represented by something like an id field in a relational database. Then other information is normally irrelevant and one would like (upon submission of the form) to get ONLY the id value for this field. Other information, which might be important for the rendering of the widget is irrelevant for the submission. Now what a normal user would expect from a FORM controller is to supply upon submission all the relevant data to form submissions, and not ALL the data residing in the model of the list controller. This is, however, not the default behavior, rather ALL the data is included when one queries the form model. A workaround which has been suggested to me is to bind the "model" property of the list controller to the "model.id" property of the list controller. The problem with this kind of workaround is that one then loses the functional information which is perhaps important for other parts of the program. I realize that Martin is very reluctant to change the API in any way, and I can understand that. However I think that the form controller in its current form is incomplete. I don't think it makes any sense to modify the model property of the list controller so that the form will know which data to report on submission, especially since this data can be important. Anyways, just my two cents, and thanks for the great work with qooxdoo! Omri -- View this message in context: http://qooxdoo.678.n2.nabble.com/Adding-modelPath-property-to-qx-data-controller-List-tp6648554p6933073.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
