[
https://issues.apache.org/jira/browse/LABS-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simone Gianni resolved LABS-164.
--------------------------------
Resolution: Fixed
> WEB: SmartForm : events
> -----------------------
>
> Key: LABS-164
> URL: https://issues.apache.org/jira/browse/LABS-164
> Project: Labs
> Issue Type: Wish
> Components: Magma
> Reporter: Simone Gianni
> Assignee: Simone Gianni
>
> SmartForm must support at least change events.
> This can be accomplished rather simply, saving the binding in the session in
> its "Map of strings" form, and then checking which fields have been modified.
> When a field modification is detected, a modification event must be sent to
> registered listeners or aspects.
> Listeners are a good way to compose reusable elements.
> For example, a default listener could intercept changes in a list property X,
> and populate a list Y calling a method of X like X.getChildren or similar.
> Such a preimplemented, configurable listener could be added to a form like
> this :
> new SmartForm(...).addListener(new
> SubSelectionListener("state","region","getRegions"));
> Obviously, listeners must have an interface that permits to modify the
> SmartForm (like for example changing lists or view customizer), raise
> "validation" errors etc..
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
