As a general rule, I don't think that's a good idea. On the other hand,
you can create a common superclass for both the mixin and the component
and put it in the base package.
On Tue, 21 May 2013 20:18:56 -0300, George Ludwig <georgelud...@gmail.com>
wrote:
If I wanted to extend the Autocomplete mixin, can I extend it as a
component?
I.e., my new class would extend autocomplete, but it would be in the
components package.
Just wondering if this is good Tapestry form or not...
I guess it would work, but as a general rule we suggest to avoid
inheritance. In this specific case I don't think it would work, as the
mixin is written to be used applied to a text field, while a component is
intended to be used standalone.
Why don't you create a component which uses the mixin instead of one that
extends the mixin?
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
