You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by "Craig McClanahan (JIRA)" <ji...@apache.org> on 2006/04/26 08:14:54 UTC

[jira] Moved: (SHALE-127) [Shale] Add Dialog-scoped Transitions

     [ http://issues.apache.org/struts/browse/SHALE-127?page=all ]

Craig McClanahan moved STR-2445 to SHALE-127:
---------------------------------------------

      Project: Shale  (was: Struts Action 1)
          Key: SHALE-127  (was: STR-2445)
    Component:     (was: Shale)
      Version:     (was: 1.2.4)
    Assign To:     (was: Struts Developer Mailing List)

> [Shale] Add Dialog-scoped Transitions
> -------------------------------------
>
>          Key: SHALE-127
>          URL: http://issues.apache.org/struts/browse/SHALE-127
>      Project: Shale
>         Type: Improvement

>  Environment: Operating System: Mac OS X 10.3
> Platform: Macintosh
>     Reporter: David Geary
>     Priority: Minor

>
> In practice, transitions are frequently applied to all states in a dialog; for
> example, you might have menu links that are hardwired to wizard panels. The
> transitions associated with those links are applicable regardless of the
> wizard's state (IOW, they are scoped to all states in a dialog).
> Currently Shale only supports transitions scoped to a single dialog state. I
> would like to see  transitions that are automatically applied to all of a
> dialog's states:
> <dialogs>
>    <dialog name="Registration"...>
>          <!-- The "exit" transition is applied to all states in this dialog -->
>          <transition outcome="exit" target="..."/>
>          <view name="User Information"...>
>             <!-- The "next" transition is only applicable for the User
> Information state -->
>             <transition outcome="next" target="..."/>
>          </view>
>       ...
>    <dialog>
> </dialogs>
> Currently, you can make a transition applicable to all of a dialog's states by
> copying and pasting the transition into every state. But that violates the DRY
> principle, is error prone and tedious, and makes dialog-config.xml difficult to
> read.

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org