On Fri, 17 Dec 2010 15:40:13 -0200, Andreas Andreou <andy...@di.uoa.gr>
wrote:
i wouldn't worry about that js performance and i do believe that the
current is the
correct default behavior but i do understand that this change breaks
existing running apps.
I see three options:
- bring the ids back (framework change)
- implement some kind of postprocessor that adds an id to all labels
(application change,
but the code could eventually live in the framework)
- modify application js
One more option:
* Add a configuration symbol turn on or off the id generation. Default
value: true.
--
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
