On Thu, 08 Mar 2012 13:46:47 -0300, Jochen Frey <joc...@jochenfrey.com>
wrote:
My real concern is slightly different. It boils down to the fact that
it is incredibly hard (if not impossible in certain situations) to
determine the automatically generated ClientID of a component (that's
embedded in the current component) during @SetupRender.
Have you tried it in @AfterRender?
Worst of all, it really slows down adoption (or acceptance) of Tapestry
with JavaScript specialists.
I guess they wouldn't use Zones anyway . . . or am I wrong? (often I am).
Maybe this is a similar scenario to what we sometimes find with
BeanEditForm/BeanEditor: they're meant to be used as scaffolding, giving
nice results for more common scenarios, not meant to be used in heavy
customization ones.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
