You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Thiago H. de Paula Figueiredo (JIRA)" <de...@tapestry.apache.org> on 2008/06/06 23:20:45 UTC

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

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

Thiago H. de Paula Figueiredo commented on TAPESTRY-2130:
---------------------------------------------------------

I think this issue could be also applied for forms and any other component that can trigger an event.
Howard, how would Tapestry know what needs to be updated? I didn't get you comment. Wouldn't the developer know better what needs to be updated? I really miss T4's AJAX flexibility in T5 (multiple places to be updated).

> 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
>             Fix For: 5.1
>
>
> 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