I didn't check all the Tapestry code I wrote in the last few years, but I'm
pretty sure I used BeforeRenderTemplate and BeforeRenderBody to abort the
rendering of template and body. Removing the rendering would definitely
loose some flexibility. Because the rendering state diagram would look like
t
stry.1045711.n5.nabble.com/Simplify-the-number-of-render-phase-methods-tp5715191p5715715.html
Sent from the Tapestry - Dev mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additio
Il giorno giovedì 9 agosto 2012, Howard Lewis Ship ha scritto:
>
> I'd like to hear from anyone in the overall community that relies on
> the any of these annotations.
>
>
It sounds a good idea. I've checked in my code and i've never used that.
Cheers
--
Massimo Lusetti
--
Massimo
http://meri
On Fri, 10 Aug 2012 19:49:03 -0300, Bob Harner wrote:
Yeah, I'm not defending it at all.
I know. :) I just commented because I think it does use solutions which I
think are quite bad and inneficient, as the right way would be to provide
a ValueEncoder (which we end up needing anyway) and
Yeah, I'm not defending it at all. But it's out there, and it's easy to
use, so people are copying it.
On Aug 10, 2012 3:38 PM, "Thiago H de Paula Figueiredo"
wrote:
> On Fri, 10 Aug 2012 15:09:21 -0300, Bob Harner
> wrote:
>
> Out of the 10 Tapestry projects I searched through, the only
>> ref
On Fri, 10 Aug 2012 15:09:21 -0300, Bob Harner wrote:
Out of the 10 Tapestry projects I searched through, the only
references to BeforeRenderTemplate or AfterRenderTemplate that I found
were in SelectObject components -- code that had been copied from
http://wiki.apache.org/tapestry/Tapestry5Se
Out of the 10 Tapestry projects I searched through, the only
references to BeforeRenderTemplate or AfterRenderTemplate that I found
were in SelectObject components -- code that had been copied from
http://wiki.apache.org/tapestry/Tapestry5SelectObject
On Fri, Aug 10, 2012 at 12:34 PM, Howard Lewis
I think the plan is to deprecate in 5.4, and remove outright in 5.5 then.
On Fri, Aug 10, 2012 at 9:31 AM, Jochen Frey wrote:
> We use BeforeRenderTemplate in one place but that can be changed easily to
> use BeginRender. Sounds good to us.
>
>
> On Aug 10, 2012, at 7:23 AM, Ben Dotte wrote:
>
We use BeforeRenderTemplate in one place but that can be changed easily to use
BeginRender. Sounds good to us.
On Aug 10, 2012, at 7:23 AM, Ben Dotte wrote:
> Out of those I only see 1 reference to AfterRenderTemplate in our code,
> which could probably be moved to just AfterRender. This soun
Out of those I only see 1 reference to AfterRenderTemplate in our code,
which could probably be moved to just AfterRender. This sounds reasonable
to me.
Ben
On Thu, Aug 9, 2012 at 12:20 PM, Howard Lewis Ship wrote:
> I'm always looking for ways to streamline Tapestry on the server.
>
> One thin
I'm always looking for ways to streamline Tapestry on the server.
One thing that, I believe, is over-engineered is the available set of
render phases, aka, the component render state machine.
http://tapestry.apache.org/component-rendering.html
(I remember designing this current state machine whi
11 matches
Mail list logo
