Yes, you are very possibly right :) I believe it ended up as a component because of some of the dead end streets I mentioned. At some point, I found that I needed to use an EventLink WITHOUT a zone connected, and do my own zone connecting in the containing component (ConfirmLink), because I didn't want tapestry to hook up a zone that I really just wanted to remove anyway. But I had problems doing this in a clean way, and returned to the solution posted.
On Tue, Oct 20, 2009 at 10:20 PM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > Em Tue, 20 Oct 2009 18:13:41 -0200, Inge Solvoll <inge.tapes...@gmail.com> > escreveu: > > New component posted on my blog, an EventLink connected to a zone, with >> confirm dialog. >> > > It was implemented as a component. Shouldn't it be better implemented as a > mixin, so we can use them in other components that generate <a> tags? I > guess this implementation change wouldn't be hard to do. Am I right? > > -- > Thiago H. de Paula Figueiredo > Independent Java consultant, developer, and instructor > http://www.arsmachina.com.br/thiago > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
