In fact, there was this wiki about a "confirm" mixin: http://wiki.apache.org/tapestry/Tapestry5AndJavaScriptExplained
On Wed, Oct 21, 2009 at 8:50 AM, Inge Solvoll <inge.tapes...@gmail.com>wrote: > My solution posted on the blog includes stopping the event, doing some > confirmation and finally triggering the event manually after. I really > learned a lot about javascript in general, and about Prototype and > Tapestry.js specifically in this process. I strongly recommend spending > some > hours digging into these things while creating something you need, it gets > a > lot easier with a little bit of experience :) > > I will rewrite it to a mixin when I get the time! > > On Tue, Oct 20, 2009 at 11:14 PM, Thiago H. de Paula Figueiredo < > thiag...@gmail.com> wrote: > > > Em Tue, 20 Oct 2009 18:47:14 -0200, Inge Solvoll < > inge.tapes...@gmail.com> > > escreveu: > > > > Yes, you are very possibly right :) > >> > > > > :) > > > > I believe it ended up as a component because of some of the dead end > >> streets I mentioned. > >> > > > > Do they include how to stop an event in JavaScript? If I was going to > > implement something like that now (and I need one), that's what I would > try > > to do. And I would need to research and learn JavaScript events. > > > > I have some EventLink-like components, so I need a mixin approach . . . > > > > > > -- > > 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 > > > > >
