You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shale.apache.org by "Craig McClanahan (JIRA)" <ji...@apache.org> on 2006/10/20 05:19:25 UTC

[jira] Resolved: (SHALE-153) Allow dialog substate to return information to calling state

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

Craig McClanahan resolved SHALE-153.
------------------------------------

    Fix Version/s: 1.0.4-SNAPSHOT
       Resolution: Fixed

The current shale-dialog implementation now supports a parent/child relationship between active dialogs, optimized for the case where the child is in a separate window or frame (typically a popup).  The client dialog has access to the parent DialogContext via the "parent" property, or by evaluating expressions like "#{dialog.parent}".  Therefore, a client action can access the "data" object of the parent DialogContext to synchronize state information, either programmatically or via expressions like "#{dialog.parent.data.foo}".  Therefore, marking this enhancement request as fixed.


> Allow dialog substate to return information to calling state
> ------------------------------------------------------------
>
>                 Key: SHALE-153
>                 URL: http://issues.apache.org/struts/browse/SHALE-153
>             Project: Shale
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.0.2
>            Reporter: Craig McClanahan
>            Priority: Minor
>             Fix For: 1.0.4-SNAPSHOT
>
>
> Received in email from Tijs Rademakers <t.rademakers AT chello.nl>:
> ======================================================
> Because I cannot add a enhancement request to the ASF Bugzilla site I would like to present a possible enhancement by e-mail for the Struts Shale project.
> I like the Shale Dialog Manager feature. The implementation of dialogs and subdialogs is very handy.
> Also the possibility to give a transition back from a subdialog to a parent dialog is great.
> But what I would like in addition to this is to have a subdialog give state back to the parent dialog.
> Here is an example for when this is useful:
>  
> A user is creating a bank account. This is the account dialog.
> On this account an account holder is already present. But the user wants to add an extra account holder.
> So the user starts a search client dialog (subdialog of the account dialog). When the client is found (the client dialog ends here)
> this client has to be added to the bank account as part of the account dialog.
> So here you would like to pass the client object from the client subdialog to the account parent dialog.
>  
> I think that with some changes to the StatusImpl class this should be possible.
> How do you think about this enhancement?
>  

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