tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thiago H. de Paula Figueiredo (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TAP5-108) ActionLink should be able to update several zones
Date Tue, 10 Feb 2009 01:28:59 GMT

    [ https://issues.apache.org/jira/browse/TAP5-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672102#action_12672102

Thiago H. de Paula Figueiredo commented on TAP5-108:

What if any event handler method that can return a Zone or Block could also receive a <zone
id, block or zone to render> map? Not only ActionLink, but also EventLink, Form, etc. This
would be very T5-ish (contrasted with T4's updateComponents) and could be implemented only
changing Tapestry internal services, without breaking existing code.

> ActionLink should be able to update several zones
> -------------------------------------------------
>                 Key: TAP5-108
>                 URL: https://issues.apache.org/jira/browse/TAP5-108
>             Project: Tapestry 5
>          Issue Type: Improvement
>    Affects Versions: 5.0.15
>            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.

View raw message