On Tue, 21 May 2013 23:52:49 -0300, George Ludwig <georgelud...@gmail.com>
wrote:
Why don't you create a component which uses the mixin instead of one
that
extends the mixin?
Well, I've already got that component. I'd like to simplify it and have
better control over it, and am exploring my options. My thought would be
to subclass it and apply its behavior to a textfield within the
subclassed .tml
You cannot apply a component to another component like you can with
mixins. Or I really didn't undertand what you described above, as what you
describe, IMHO, doesn't need to involve a component subclassing a mixin,
just mixin applied to a component.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
