You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Igor Drobiazko (JIRA)" <de...@tapestry.apache.org> on 2008/02/07 12:56:08 UTC
[jira] Created: (TAPESTRY-2130) ActionLink should be able to update
several zones
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
[jira] Commented: (TAPESTRY-2130) ActionLink should be able to
update several zones
Posted by "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=12571886#action_12571886 ]
Renat Zubairov commented on TAPESTRY-2130:
------------------------------------------
Is it possible now to dynamically decide which zones will be updated? For example when form is sent as part of AJAX request then either "Errors" section will be updated or complete form will be replaced with something else?
> 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
[jira] Updated: (TAPESTRY-2130) ActionLink should be able to update
several zones
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-2130:
-------------------------------------------
Fix Version/s: 5.1
> 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
[jira] Commented: (TAPESTRY-2130) ActionLink should be able to
update several zones
Posted by "Davor Hrg (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568678#action_12568678 ]
Davor Hrg commented on TAPESTRY-2130:
-------------------------------------
just some thoughts... :
some parts of the page require the page to be processed so a zone around that part can be properly rendered.
however, tickers, chat messages, updateable statuses may be independent of the rest of the page,
zone should assume the component is dependent, and process the page normally,
and have a parameter with which we can say: "this zone is independent"
> 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
[jira] Commented: (TAPESTRY-2130) ActionLink should be able to
update several zones
Posted by "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
[jira] Commented: (TAPESTRY-2130) ActionLink should be able to
update several zones
Posted by "Thiago H. de Paula Figueiredo (JIRA)" <de...@tapestry.apache.org>.
[ 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
[jira] Updated: (TAP5-108) ActionLink should be able to update
several zones
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-108:
--------------------------------------
Issue Type: Improvement (was: Bug)
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Commented: (TAPESTRY-2130) ActionLink should be able to
update several zones
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571838#action_12571838 ]
Howard M. Lewis Ship commented on TAPESTRY-2130:
------------------------------------------------
The current design is organized around minimizing the amount of configuration necessary, and to let the server side decide what gets updated and how.
> 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