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.
On Tue, Jul 20, 2010 at 11:34 AM, panyasan <[email protected]> wrote:
>
> Hi Martin:
>
> I can confirm that the first error has disappeared with the latest trunk
> Thank you very much for looking into this so quickly and fixing it
> immediately!
>
> The second error (too much recursion) is still there - I will look further
> into that.
>
> Concerning the various suggestions on a simplified form binding for
> selection widgets: I am thinking of something like adding an argument to
> qx.ui.form.Form.add() like so:
>
> qx.ui.form.Form.add(IForm item, String label, (Function | AsyncValidator |
> null) validator, (String | null) name, Object options )
>
> options being a map. Options could have a valuePropertyChain, which tells
> the form-to-model binding how to find the scalar value of a form item value
> in a selection widget. So, for example,
>
> form.add(myCurrencySelectBox, "Choose Currency", null, "currency", {
> valuePropertyChain : "model.value"
> });
>
> would allow a direct, bidirectional model->form binding: whenever the model
> changes, the binding will iterate through the items by
> getModel().getValue()
> to find the right item(s) to select. Whenever the user changes the
> selection, the model will receive the value of the getModel().getValue()
> call on the selected item(s). This could have a different behavior for
> single-selection widgets (scalar) and mulit-selection widgets (array) -
> which would be more user-friendly. Or the model values are always arrays to
> be more consistent with the API.
>
> I think enhancement of form binding along these lines would make the life
> of
> developers who work with forms a lot incredibly easier and it would result
> in a lot of saved time us!
>
> Thanks for considering this,
>
> Christian
>
> --
> View this message in context:
> http://qooxdoo.678.n2.nabble.com/Databinding-problem-Creating-form-model-stopped-working-tp5314091p5316868.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
