On Tue, 06 Nov 2012 22:41:17 -0200, Paul Stanton <p...@mapshed.com.au>
wrote:
.. and then if you have a combination of potential mixins, you end up
with n * blocks, with n * fields.
Why don't you have a single mixin implementation that has the logic to
handle all the situations? Maybe delegating method calls to other mixins?
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
