[ http://issues.apache.org/struts/browse/SHALE-113?page=all ]
Craig McClanahan resolved SHALE-113.
------------------------------------
Fix Version/s: 1.0.4-SNAPSHOT
Resolution: Fixed
The new event handling support addresses the requirement to provide an
application with enough information to support this feature. If you make the
"data" object you provide implement DialogContextListener, it will be
automatically registered as a listener for interesting events, including state
transitions within the dialog. In turn, this makes it very easy for the dialog
to provide boolean functions to which you can bind, say, the "rendered" or
"disabled" properties of the navigation buttons in the view, since only the
application can tell you for sure whether a particular control should be
rendered (or disabled) or not.
For use cases where a common pattern is implemented (such as "wizard dialogs"),
it is straightforward for the application developer to provide a common base
class for "data" beans that implements the common behavior for
first/previous/next/last type controls, or the like.
> [shale] Create "Dialog Aware" button panel component
> ----------------------------------------------------
>
> Key: SHALE-113
> URL: http://issues.apache.org/struts/browse/SHALE-113
> Project: Shale
> Issue Type: Improvement
> Components: Dialog
> Environment: Operating System: other
> Platform: Other
> Reporter: Ed Burns
> Priority: Minor
> Fix For: 1.0.4-SNAPSHOT
>
>
> There really should be a dialog aware button panel component that
> automatically
> generates next and previous buttons, greying things out as appropriate.
> The JSF CharacterCombat demo has some ideas on this.
> https://javaserverfaces-sources.dev.java.net/source/browse/javaserverfaces-sources/jsf-demo/characterCombat/
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
