Tapestry-jquery has rewritten all of Tapestry's js in jquery. That's quite a bit more then simply adding jquery to your app as a JavascriptStack.
My personal preference is to use Tapestry's existing (Prototype) js (since it has withstood the test of time and is widely used), use jQuery in no-conflict mode, and add only jquery plug-ins I need. Furthermore, Twitter-Bootstrap has some pretty nice jQuery plug-ins, and it really isn't very difficult to wrap these plugins as Tapestry common components for my app(s). Using the custom event bridge I mentioned in an earlier thread, I can also trigger Prototype custom events from jQuery, and listen for Prototype custom events from jQuery code. This means I can trigger or listen to any Tapestry client-side events using jQuery. On Mon, Aug 13, 2012 at 7:26 AM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > On Sun, 12 Aug 2012 22:12:52 -0300, Ray Nicholus <rnicho...@widen.com> > wrote: > > Jquery should really be part of a JavascriptStack. in fact, it should >> probably be its own stack. You can add any jquery plugins and >> stylesheets to this stack as well. >> > > Hasn't tapestry-jquery done this already? > > -- > Thiago H. de Paula Figueiredo > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org> > For additional commands, e-mail: users-h...@tapestry.apache.org > >
