Out of curiosity, has anyone that's claimed it's trivial to get jQuery working in Tapestry actually tried it?
IIRC, I ran into a bunch of issues with the load order of JS files. I think it had to do with Tapestry placing include lines at the bottom of the DOM but my document ready listener appearing well before then. So, Prototype loaded and my code wouldn't work. Having said that, this situation can be improved without switching all of Tapestry from Prototype. But, I don't want anyone to be deluded into thinking that because Prototype and jQuery can coexist, that it's trivial to do so in Tapestry. -- Kevin On Sun, Feb 1, 2009 at 6:03 PM, Thiago H. de Paula Figueiredo <thiag...@gmail.com> wrote: > Em Sun, 01 Feb 2009 15:45:49 -0300, Borut Bolčina <borut.bolc...@gmail.com> > escreveu: > >> IMHO creating more "high level" components and better documentation are >> the things to spend time on, if not even crucial and certainly not switching >> JS library just after the framework was released. > > I agree 100%, as you can easily use Prototype and JQuery side to side and > Javascript download sizes will be taken of by the new T5.1 Gzip asset > compression. > > -- > 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 > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
