Jean Luc,
On Fri, Apr 25, 2008 at 7:52 AM, Jean Luc <
[hidden email]> wrote:
> A common case, I suppose: you have a transient field in a form that is only
> used to support a decision or to be copied into a real field. Example: a
> drop down box with the widgets (in a multi-widget form) near a button
> "Duplicate Widget". The action behind the button would duplicate the model
> part of the indicated widget so it will have to reference the
> currently-selected item in the dropdown box.
Like you said, using a separate instance for this is the way to go. I
often have an instance called "ui" that stores this type of state
which is very much tied to the way the UI is done, and which is never
sent to services. Plus"ui" has the the additional benefit of being a
short name :).
Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog:
http://www.orbeon.com/blog/Personal Blog:
http://avernet.blogspot.com/Twitter -
http://twitter.com/avernet--
You receive this message as a subscriber of the
[hidden email] mailing list.
To unsubscribe: mailto:
[hidden email]
For general help: mailto:
[hidden email]?subject=help
OW2 mailing lists service home page:
http://www.ow2.org/wws