[jira] Commented: (TAPESTRY-2130) ActionLink should be able to update several zones

["Renat Zubairov (JIRA)" <de...@tapestry.apache.org>]

    [ https://issues.apache.org/jira/browse/TAPESTRY-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568650#action_12568650 ] 

Renat Zubairov commented on TAPESTRY-2130:
------------------------------------------

It would be also very nice to be able to define zones for update dynamically. As it is done in T4 we can dynamically decide which zones to update. We've developed a kind of framework on top of T4 where each component in processing/creation of event can decide wherever to update itself or not. 

Typical example of the use-case is login dialog implemented via Dojo dialog or similar modal dialogs, when user authenticate itself then some of the components on the page may decide to re-render themself.

That would make even more sense with event bulbing in T5.

> ActionLink should be able to update several zones
> -------------------------------------------------
>
>                 Key: TAPESTRY-2130
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2130
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: XHR/dhtml/Ajax
>    Affects Versions: 5.0.10
>            Reporter: Igor Drobiazko
>
> Unfortunately the ActionLink's parameter "zone" expect a single zone. Commonly, we want to update several parts of the client. It would be very nice to be able to update a bunch of zones after an action was triggered. This limitation is quite frustrating for people coming from T4 because "updateComponents" expected a list of component ids.

-- 
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org