Hi Thiago,
that's awesome information! Thanks!
Kind Regards,
Wulf
-Original Message-
From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com]
Sent: Mittwoch, 5. Oktober 2011 19:38
To: Tapestry users; Ulrich Stärk
Subject: Re: Block parameter
On Wed, 05 Oct 2011 14:19:31
On Wed, 05 Oct 2011 14:19:31 -0300, Ulrich Stärk wrote:
This is obviously much better than fiddling with internal stuff if it
suffices your needs.
I don't think internal stuff is needed for both of the solutions. A
RenderCommand (which isn't internal) can be implemented and it receives
th
iel.de]
> Sent: Mittwoch, 5. Oktober 2011 15:43
> To: Tapestry users
> Subject: Re: Block parameter
>
> Rendering component markup directly from your component class is only
> useful for very simple
> components. What you want to do is to mimick some of Tapestry's inter
-
From: Ulrich Stärk [mailto:u...@spielviel.de]
Sent: Mittwoch, 5. Oktober 2011 15:43
To: Tapestry users
Subject: Re: Block parameter
Rendering component markup directly from your component class is only useful
for very simple
components. What you want to do is to mimick some of Tapestry's inte
Rendering component markup directly from your component class is only useful
for very simple
components. What you want to do is to mimick some of Tapestry's internals that
are abstracted away
for a reason. Now would be the time to start using a component template.
(If you really really have to d
