tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (TAP5-1065) Non-visual mixin to generate events as it begins/ends rendering (useful for generating matching JavaScript)
Date Sat, 20 Mar 2010 02:06:27 GMT

     [ https://issues.apache.org/jira/browse/TAP5-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Howard M. Lewis Ship reassigned TAP5-1065:
------------------------------------------

    Assignee: Howard M. Lewis Ship

> Non-visual mixin to generate events as it begins/ends rendering (useful for generating
matching JavaScript)
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1065
>                 URL: https://issues.apache.org/jira/browse/TAP5-1065
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.2.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>
> Often when dealing with Blocks and Ajax, you can't rely on a container's afterRender
render phase event, since the container itself doesn't render (just blocks or components within
the container). This can make it difficult to generate matching JavaScript when that is itself
necessary.  A kludgey approach involves
> delegating to an inner class that implements Renderable, but that is most ugly.
> A RenderNotifier mixin could fire a "beginRender" and "afterRender" event from the corresponding
phases. A container could add handlers for those phases to handle the events.

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


Mime
View raw message