You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2007/11/19 22:01:13 UTC
[jira] Created: (TAPESTRY-1920) Tapestry should be smarter about
event handler methods refiring events with the same name
Tapestry should be smarter about event handler methods refiring events with the same name
-----------------------------------------------------------------------------------------
Key: TAPESTRY-1920
URL: https://issues.apache.org/jira/browse/TAPESTRY-1920
Project: Tapestry
Issue Type: New Feature
Components: tapestry-core
Reporter: Howard M. Lewis Ship
An idiom that's evolving is for a component or mixin to receive an event via an event handler method, and then refire the event with a different context to obtain information or behavior from its container.
Currently, you must either a) fire a differently named event or b) expressly trigger the event on the container's resources.
It would be nice if Tapestry was smarter, and woul track which event(s) a component or mixin is currently handling, and would automatically skip the component if another event of the same name was triggered. Basically, roll the b) logic above directly into ComponentResources/ComponentPageElement.
--
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-58) Tapestry should be smarter about event
handler methods refiring events with the same name
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-58:
-------------------------------------
Issue Type: Improvement (was: Bug)
> Tapestry should be smarter about event handler methods refiring events with the same name
> -----------------------------------------------------------------------------------------
>
> Key: TAP5-58
> URL: https://issues.apache.org/jira/browse/TAP5-58
> Project: Tapestry 5
> Issue Type: Improvement
> Affects Versions: 5.0.15
> Reporter: Howard M. Lewis Ship
> Priority: Minor
>
> An idiom that's evolving is for a component or mixin to receive an event via an event handler method, and then refire the event with a different context to obtain information or behavior from its container.
> Currently, you must either a) fire a differently named event or b) expressly trigger the event on the container's resources.
> It would be nice if Tapestry was smarter, and woul track which event(s) a component or mixin is currently handling, and would automatically skip the component if another event of the same name was triggered. Basically, roll the b) logic above directly into ComponentResources/ComponentPageElement.
--
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-1920) Tapestry should be smarter about
event handler methods refiring events with the same name
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-1920:
-------------------------------------------
Fix Version/s: (was: 5.0.9)
5.0.10
> Tapestry should be smarter about event handler methods refiring events with the same name
> -----------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1920
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1920
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-core
> Reporter: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.0.10
>
>
> An idiom that's evolving is for a component or mixin to receive an event via an event handler method, and then refire the event with a different context to obtain information or behavior from its container.
> Currently, you must either a) fire a differently named event or b) expressly trigger the event on the container's resources.
> It would be nice if Tapestry was smarter, and woul track which event(s) a component or mixin is currently handling, and would automatically skip the component if another event of the same name was triggered. Basically, roll the b) logic above directly into ComponentResources/ComponentPageElement.
--
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-1920) Tapestry should be smarter about
event handler methods refiring events with the same name
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-1920:
-------------------------------------------
Fix Version/s: (was: 5.0.10)
5.0.11
> Tapestry should be smarter about event handler methods refiring events with the same name
> -----------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1920
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1920
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-core
> Reporter: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.0.11
>
>
> An idiom that's evolving is for a component or mixin to receive an event via an event handler method, and then refire the event with a different context to obtain information or behavior from its container.
> Currently, you must either a) fire a differently named event or b) expressly trigger the event on the container's resources.
> It would be nice if Tapestry was smarter, and woul track which event(s) a component or mixin is currently handling, and would automatically skip the component if another event of the same name was triggered. Basically, roll the b) logic above directly into ComponentResources/ComponentPageElement.
--
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-1920) Tapestry should be smarter about
event handler methods refiring events with the same name
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-1920:
-------------------------------------------
Fix Version/s: (was: 5.0.11)
5.0.12
> Tapestry should be smarter about event handler methods refiring events with the same name
> -----------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1920
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1920
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-core
> Reporter: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.0.12
>
>
> An idiom that's evolving is for a component or mixin to receive an event via an event handler method, and then refire the event with a different context to obtain information or behavior from its container.
> Currently, you must either a) fire a differently named event or b) expressly trigger the event on the container's resources.
> It would be nice if Tapestry was smarter, and woul track which event(s) a component or mixin is currently handling, and would automatically skip the component if another event of the same name was triggered. Basically, roll the b) logic above directly into ComponentResources/ComponentPageElement.
--
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-1920) Tapestry should be smarter about
event handler methods refiring events with the same name
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-1920:
-------------------------------------------
Fix Version/s: (was: 5.0.7)
5.0.8
> Tapestry should be smarter about event handler methods refiring events with the same name
> -----------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1920
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1920
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-core
> Reporter: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.0.8
>
>
> An idiom that's evolving is for a component or mixin to receive an event via an event handler method, and then refire the event with a different context to obtain information or behavior from its container.
> Currently, you must either a) fire a differently named event or b) expressly trigger the event on the container's resources.
> It would be nice if Tapestry was smarter, and woul track which event(s) a component or mixin is currently handling, and would automatically skip the component if another event of the same name was triggered. Basically, roll the b) logic above directly into ComponentResources/ComponentPageElement.
--
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-1920) Tapestry should be smarter about
event handler methods refiring events with the same name
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-1920:
-------------------------------------------
Fix Version/s: (was: 5.0.12)
5.0.13
> Tapestry should be smarter about event handler methods refiring events with the same name
> -----------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1920
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1920
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-core
> Reporter: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.0.13
>
>
> An idiom that's evolving is for a component or mixin to receive an event via an event handler method, and then refire the event with a different context to obtain information or behavior from its container.
> Currently, you must either a) fire a differently named event or b) expressly trigger the event on the container's resources.
> It would be nice if Tapestry was smarter, and woul track which event(s) a component or mixin is currently handling, and would automatically skip the component if another event of the same name was triggered. Basically, roll the b) logic above directly into ComponentResources/ComponentPageElement.
--
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-1920) Tapestry should be smarter about
event handler methods refiring events with the same name
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-1920:
-------------------------------------------
Fix Version/s: (was: 5.0.13)
5.0
> Tapestry should be smarter about event handler methods refiring events with the same name
> -----------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1920
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1920
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-core
> Reporter: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.0
>
>
> An idiom that's evolving is for a component or mixin to receive an event via an event handler method, and then refire the event with a different context to obtain information or behavior from its container.
> Currently, you must either a) fire a differently named event or b) expressly trigger the event on the container's resources.
> It would be nice if Tapestry was smarter, and woul track which event(s) a component or mixin is currently handling, and would automatically skip the component if another event of the same name was triggered. Basically, roll the b) logic above directly into ComponentResources/ComponentPageElement.
--
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-1920) Tapestry should be smarter about
event handler methods refiring events with the same name
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-1920:
-------------------------------------------
Fix Version/s: 5.0.7
Priority: Minor (was: Major)
> Tapestry should be smarter about event handler methods refiring events with the same name
> -----------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1920
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1920
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-core
> Reporter: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.0.7
>
>
> An idiom that's evolving is for a component or mixin to receive an event via an event handler method, and then refire the event with a different context to obtain information or behavior from its container.
> Currently, you must either a) fire a differently named event or b) expressly trigger the event on the container's resources.
> It would be nice if Tapestry was smarter, and woul track which event(s) a component or mixin is currently handling, and would automatically skip the component if another event of the same name was triggered. Basically, roll the b) logic above directly into ComponentResources/ComponentPageElement.
--
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-1920) Tapestry should be smarter about
event handler methods refiring events with the same name
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-1920:
-------------------------------------------
Affects Version/s: 5.0
> Tapestry should be smarter about event handler methods refiring events with the same name
> -----------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1920
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1920
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.0
> Reporter: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.0
>
>
> An idiom that's evolving is for a component or mixin to receive an event via an event handler method, and then refire the event with a different context to obtain information or behavior from its container.
> Currently, you must either a) fire a differently named event or b) expressly trigger the event on the container's resources.
> It would be nice if Tapestry was smarter, and woul track which event(s) a component or mixin is currently handling, and would automatically skip the component if another event of the same name was triggered. Basically, roll the b) logic above directly into ComponentResources/ComponentPageElement.
--
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-1920) Tapestry should be smarter about
event handler methods refiring events with the same name
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-1920:
-------------------------------------------
Fix Version/s: (was: 5.0.8)
5.0.9
> Tapestry should be smarter about event handler methods refiring events with the same name
> -----------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1920
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1920
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-core
> Reporter: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.0.9
>
>
> An idiom that's evolving is for a component or mixin to receive an event via an event handler method, and then refire the event with a different context to obtain information or behavior from its container.
> Currently, you must either a) fire a differently named event or b) expressly trigger the event on the container's resources.
> It would be nice if Tapestry was smarter, and woul track which event(s) a component or mixin is currently handling, and would automatically skip the component if another event of the same name was triggered. Basically, roll the b) logic above directly into ComponentResources/ComponentPageElement.
--
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