tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Harner (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TAP5-1707) The RenderNotification Mixin should documented with an example
Date Wed, 02 Mar 2016 01:54:18 GMT

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

Bob Harner resolved TAP5-1707.
    Resolution: Fixed

See http://tapestry.apache.org/5.4/apidocs/org/apache/tapestry5/corelib/mixins/RenderNotification.html

> The RenderNotification Mixin should documented with an example
> --------------------------------------------------------------
>                 Key: TAP5-1707
>                 URL: https://issues.apache.org/jira/browse/TAP5-1707
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.3
>            Reporter: Steve Eynon
>            Assignee: Bob Harner
>            Priority: Trivial
>              Labels: bulk-close-candidate
> The RenderNotification Mixin seems to be an idiomatic way to generate render phase 'like'
events during an Ajax rendering. But alas the concept is a tricky one with a couple of gotchas
and could really do with a worked example (in the JavaDocs) to fully explain its usage.
> The email thread is :
> http://tapestry.1045711.n5.nabble.com/T5-2-Looking-For-A-RenderNotification-Mixin-Example-td4917771.html
> I've picked out some relevant bits...
> I would like some pre and post render events to be fired on a component after it's handled
an Ajax event and returned a Zone which it contains.
> <div t:type="Zone" id="zone">
>        <div t:type="Any" t:mixins="RenderNotification">
>                <!-- zone content ->
>        </div>
> </div>
> When the Any component renders as a whole, it receives the render phase methods which
are picked up the Mixin. The Mixin then fires its own component events with the same name,
which  bubble up the component hierarchy.
> But the beforeRender and afterRender triggered by this mixins are not render events,
so they should be handled by onBeforeRender[FromComponentId] and onAfterRender[FromComponentId]
methods or @OnEvent(value = "afterRender", component = "id"). In both cases, the component
id is optional.
> Nice one - I may have overlooked the onBeginRender() vs beginRender().

This message was sent by Atlassian JIRA

View raw message