On Mon, 28 Feb 2011 17:36:55 -0300, wkm <w...@zanoccio.com> wrote:
I was afraid you were going to say that. :)
Is this the "tapestry-standard" way, or is it more of a workaround?
(basically, I'm wondering if I should refactor all of my wrapper
components as mixins, or just the text field ones.)
Mixins are the Tapestry way in this case. Way more reusable than component
subclassing or wrapping. You can use the same mixin for different
components instead of subclassing or wrapping each component. In addition,
it doesn't mess up with component id's and their labels.
--
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
