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)" <ji...@apache.org> on 2009/07/31 12:12:14 UTC

[jira] Created: (TAP5-801) TriggerEvent component to trigger a component event during rendering

TriggerEvent component to trigger a component event during rendering
--------------------------------------------------------------------

                 Key: TAP5-801
                 URL: https://issues.apache.org/jira/browse/TAP5-801
             Project: Tapestry 5
          Issue Type: New Feature
          Components: tapestry-component-report
    Affects Versions: 5.1.0.5
            Reporter: Howard M. Lewis Ship
            Priority: Minor


It would be nice if it were possible to trigger an arbitrary component event during rendering; this is often useful to add JavaScript to a page (via calls to the RenderSupport environmental).

Currently this can be accomplished using Delegator and providing a Renderable object (as an anonymous inner class) ... but that's ugly, i.e.

<t:delegate to="wireEventHandlers"/>

public Renderable getWireEventHandlers()
{
  return new Renderable()
  {
    public void render(MarkupWriter writer)
   {
     ...
   }
  };
}


I would rather something like:

<t:triggerevent event="wireEventHandlers"/>

void onWireEventHandlers()
{
  ...
}

The MarkupWriter could be passed as the event context, for handlers that need to write markup as well as perform other functions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (TAP5-801) TriggerEvent component to trigger a component event during rendering

Posted by "Igor Drobiazko (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Drobiazko reassigned TAP5-801:
-----------------------------------

    Assignee: Igor Drobiazko

> TriggerEvent component to trigger a component event during rendering
> --------------------------------------------------------------------
>
>                 Key: TAP5-801
>                 URL: https://issues.apache.org/jira/browse/TAP5-801
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-component-report
>    Affects Versions: 5.1.0.5
>            Reporter: Howard M. Lewis Ship
>            Assignee: Igor Drobiazko
>            Priority: Minor
>
> It would be nice if it were possible to trigger an arbitrary component event during rendering; this is often useful to add JavaScript to a page (via calls to the RenderSupport environmental).
> Currently this can be accomplished using Delegator and providing a Renderable object (as an anonymous inner class) ... but that's ugly, i.e.
> <t:delegate to="wireEventHandlers"/>
> public Renderable getWireEventHandlers()
> {
>   return new Renderable()
>   {
>     public void render(MarkupWriter writer)
>    {
>      ...
>    }
>   };
> }
> I would rather something like:
> <t:triggerevent event="wireEventHandlers"/>
> void onWireEventHandlers()
> {
>   ...
> }
> The MarkupWriter could be passed as the event context, for handlers that need to write markup as well as perform other functions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (TAP5-801) TriggerEvent component to trigger a component event during rendering

Posted by "Igor Drobiazko (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Drobiazko reassigned TAP5-801:
-----------------------------------

    Assignee: Igor Drobiazko

> TriggerEvent component to trigger a component event during rendering
> --------------------------------------------------------------------
>
>                 Key: TAP5-801
>                 URL: https://issues.apache.org/jira/browse/TAP5-801
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-component-report
>    Affects Versions: 5.1.0.5
>            Reporter: Howard M. Lewis Ship
>            Assignee: Igor Drobiazko
>            Priority: Minor
>
> It would be nice if it were possible to trigger an arbitrary component event during rendering; this is often useful to add JavaScript to a page (via calls to the RenderSupport environmental).
> Currently this can be accomplished using Delegator and providing a Renderable object (as an anonymous inner class) ... but that's ugly, i.e.
> <t:delegate to="wireEventHandlers"/>
> public Renderable getWireEventHandlers()
> {
>   return new Renderable()
>   {
>     public void render(MarkupWriter writer)
>    {
>      ...
>    }
>   };
> }
> I would rather something like:
> <t:triggerevent event="wireEventHandlers"/>
> void onWireEventHandlers()
> {
>   ...
> }
> The MarkupWriter could be passed as the event context, for handlers that need to write markup as well as perform other functions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (TAP5-801) Add Trigger component to trigger a component event during rendering

Posted by "Igor Drobiazko (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Drobiazko closed TAP5-801.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 5.2.0.0

> Add Trigger component to trigger a component event during rendering
> -------------------------------------------------------------------
>
>                 Key: TAP5-801
>                 URL: https://issues.apache.org/jira/browse/TAP5-801
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-component-report
>    Affects Versions: 5.1.0.5
>            Reporter: Howard M. Lewis Ship
>            Assignee: Igor Drobiazko
>            Priority: Minor
>             Fix For: 5.2.0.0
>
>
> It would be nice if it were possible to trigger an arbitrary component event during rendering; this is often useful to add JavaScript to a page (via calls to the RenderSupport environmental).
> Currently this can be accomplished using Delegator and providing a Renderable object (as an anonymous inner class) ... but that's ugly, i.e.
> <t:delegate to="wireEventHandlers"/>
> public Renderable getWireEventHandlers()
> {
>   return new Renderable()
>   {
>     public void render(MarkupWriter writer)
>    {
>      ...
>    }
>   };
> }
> I would rather something like:
> <t:triggerevent event="wireEventHandlers"/>
> void onWireEventHandlers()
> {
>   ...
> }
> The MarkupWriter could be passed as the event context, for handlers that need to write markup as well as perform other functions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (TAP5-801) TriggerEvent component to trigger a component event during rendering

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TAP5-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737484#action_12737484 ] 

Howard M. Lewis Ship commented on TAP5-801:
-------------------------------------------

Perhaps a better name would just be "trigger", i.e., <t:trigger event="wireEventHandlers"/>

> TriggerEvent component to trigger a component event during rendering
> --------------------------------------------------------------------
>
>                 Key: TAP5-801
>                 URL: https://issues.apache.org/jira/browse/TAP5-801
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-component-report
>    Affects Versions: 5.1.0.5
>            Reporter: Howard M. Lewis Ship
>            Priority: Minor
>
> It would be nice if it were possible to trigger an arbitrary component event during rendering; this is often useful to add JavaScript to a page (via calls to the RenderSupport environmental).
> Currently this can be accomplished using Delegator and providing a Renderable object (as an anonymous inner class) ... but that's ugly, i.e.
> <t:delegate to="wireEventHandlers"/>
> public Renderable getWireEventHandlers()
> {
>   return new Renderable()
>   {
>     public void render(MarkupWriter writer)
>    {
>      ...
>    }
>   };
> }
> I would rather something like:
> <t:triggerevent event="wireEventHandlers"/>
> void onWireEventHandlers()
> {
>   ...
> }
> The MarkupWriter could be passed as the event context, for handlers that need to write markup as well as perform other functions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (TAP5-801) Add Trigger component to trigger a component event during rendering

Posted by "Igor Drobiazko (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Drobiazko closed TAP5-801.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 5.2.0.0

> Add Trigger component to trigger a component event during rendering
> -------------------------------------------------------------------
>
>                 Key: TAP5-801
>                 URL: https://issues.apache.org/jira/browse/TAP5-801
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-component-report
>    Affects Versions: 5.1.0.5
>            Reporter: Howard M. Lewis Ship
>            Assignee: Igor Drobiazko
>            Priority: Minor
>             Fix For: 5.2.0.0
>
>
> It would be nice if it were possible to trigger an arbitrary component event during rendering; this is often useful to add JavaScript to a page (via calls to the RenderSupport environmental).
> Currently this can be accomplished using Delegator and providing a Renderable object (as an anonymous inner class) ... but that's ugly, i.e.
> <t:delegate to="wireEventHandlers"/>
> public Renderable getWireEventHandlers()
> {
>   return new Renderable()
>   {
>     public void render(MarkupWriter writer)
>    {
>      ...
>    }
>   };
> }
> I would rather something like:
> <t:triggerevent event="wireEventHandlers"/>
> void onWireEventHandlers()
> {
>   ...
> }
> The MarkupWriter could be passed as the event context, for handlers that need to write markup as well as perform other functions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (TAP5-801) Add Trigger component to trigger a component event during rendering

Posted by "Igor Drobiazko (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Drobiazko updated TAP5-801:
--------------------------------

    Summary: Add Trigger component to trigger a component event during rendering  (was: TriggerEvent component to trigger a component event during rendering)

> Add Trigger component to trigger a component event during rendering
> -------------------------------------------------------------------
>
>                 Key: TAP5-801
>                 URL: https://issues.apache.org/jira/browse/TAP5-801
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-component-report
>    Affects Versions: 5.1.0.5
>            Reporter: Howard M. Lewis Ship
>            Assignee: Igor Drobiazko
>            Priority: Minor
>
> It would be nice if it were possible to trigger an arbitrary component event during rendering; this is often useful to add JavaScript to a page (via calls to the RenderSupport environmental).
> Currently this can be accomplished using Delegator and providing a Renderable object (as an anonymous inner class) ... but that's ugly, i.e.
> <t:delegate to="wireEventHandlers"/>
> public Renderable getWireEventHandlers()
> {
>   return new Renderable()
>   {
>     public void render(MarkupWriter writer)
>    {
>      ...
>    }
>   };
> }
> I would rather something like:
> <t:triggerevent event="wireEventHandlers"/>
> void onWireEventHandlers()
> {
>   ...
> }
> The MarkupWriter could be passed as the event context, for handlers that need to write markup as well as perform other functions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (TAP5-801) Add Trigger component to trigger a component event during rendering

Posted by "Igor Drobiazko (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TAP5-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Drobiazko updated TAP5-801:
--------------------------------

    Summary: Add Trigger component to trigger a component event during rendering  (was: TriggerEvent component to trigger a component event during rendering)

> Add Trigger component to trigger a component event during rendering
> -------------------------------------------------------------------
>
>                 Key: TAP5-801
>                 URL: https://issues.apache.org/jira/browse/TAP5-801
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-component-report
>    Affects Versions: 5.1.0.5
>            Reporter: Howard M. Lewis Ship
>            Assignee: Igor Drobiazko
>            Priority: Minor
>
> It would be nice if it were possible to trigger an arbitrary component event during rendering; this is often useful to add JavaScript to a page (via calls to the RenderSupport environmental).
> Currently this can be accomplished using Delegator and providing a Renderable object (as an anonymous inner class) ... but that's ugly, i.e.
> <t:delegate to="wireEventHandlers"/>
> public Renderable getWireEventHandlers()
> {
>   return new Renderable()
>   {
>     public void render(MarkupWriter writer)
>    {
>      ...
>    }
>   };
> }
> I would rather something like:
> <t:triggerevent event="wireEventHandlers"/>
> void onWireEventHandlers()
> {
>   ...
> }
> The MarkupWriter could be passed as the event context, for handlers that need to write markup as well as perform other functions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (TAP5-801) TriggerEvent component to trigger a component event during rendering

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/TAP5-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737484#action_12737484 ] 

Howard M. Lewis Ship commented on TAP5-801:
-------------------------------------------

Perhaps a better name would just be "trigger", i.e., <t:trigger event="wireEventHandlers"/>

> TriggerEvent component to trigger a component event during rendering
> --------------------------------------------------------------------
>
>                 Key: TAP5-801
>                 URL: https://issues.apache.org/jira/browse/TAP5-801
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-component-report
>    Affects Versions: 5.1.0.5
>            Reporter: Howard M. Lewis Ship
>            Priority: Minor
>
> It would be nice if it were possible to trigger an arbitrary component event during rendering; this is often useful to add JavaScript to a page (via calls to the RenderSupport environmental).
> Currently this can be accomplished using Delegator and providing a Renderable object (as an anonymous inner class) ... but that's ugly, i.e.
> <t:delegate to="wireEventHandlers"/>
> public Renderable getWireEventHandlers()
> {
>   return new Renderable()
>   {
>     public void render(MarkupWriter writer)
>    {
>      ...
>    }
>   };
> }
> I would rather something like:
> <t:triggerevent event="wireEventHandlers"/>
> void onWireEventHandlers()
> {
>   ...
> }
> The MarkupWriter could be passed as the event context, for handlers that need to write markup as well as perform other functions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.