Mixins are always a bit harder since you're usually manipulating the dom after the default impl.
For something a trivial as pagelink, I'd argue that starting from scratch would be easier. On 12 Jun 2014 16:02, "Thiago H de Paula Figueiredo" <thiag...@gmail.com> wrote: > On Thu, 12 Jun 2014 10:41:10 -0300, Lance Java <lance.j...@googlemail.com> > wrote: > > Sounds like this issue would help you here >> https://issues.apache.org/jira/browse/TAP5-1611 >> > > In Barry's case, I think creating a ComponentCclassTransformerWorker to > apply a mixin to all PageLink, ActionLink and EventLink instances is the > way to go. No need to copy or subclass the link components. > > That doesn't I won't implement TAP5-1611. That's part of my to-do list in > the Month of Tapestry campaign. > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
