This has come up before:
http://mail-archives.apache.org/mod_mbox/tapestry-users/200710.mbox/[EMAIL
PROTECTED]
and
http://www.google.be/search?hl=nl&q=jquery+T5+site%3Amail-archives.apache.org%2Fmod_mbox%2Ftapestry-users%2F&btnG=Zoeken&meta=
So it seems it would be possible but a whole lot of work and I don't
think someone embarked on that adventure yet.
Toby Hobson wrote, On 30/10/2008 17:04:
I agree that it would be nice to be able to swap out the JS implementation
because I am not a great fan of Prototype. Personally I would go with YUI or
GWT. However I believe Prototype is pretty much ingrained into T5 :(
Just my 2c worth!
Toby
2008/10/30 Onno Scheffers<[EMAIL PROTECTED]>
I just stumbled upon this link that lets you test the performance of
selectors in different Javascript libraries:
http://jamesdonaghue.com/static/peppy/profile/slickspeed/
Prototype doesn't look very good from that tests and that's pretty much in
line with my own feeling after having used JQuery for a while before being
introduced to Prototype through Tapestry 5. This made me wonder if it would
be possible to write a plugin for Tapestry that overrides the default
Javascript library or wether Prototype is hardwired into the Tapestry
internals?
I haven't researched it in any way yet, but I'm aware that some mixins,
client side validation and maybe even some core components would stop
working since they depend on Prototype. Is there anything else that depends
on it? Anything that cannot be overridden in a plugin?
Could the client-side behaviors be abstracted away so that multiple
implementations can be used?
Just wondering if this would be possible and what it would entail, since
tapestry 5 already allows so many other things to be configured, overridden
or replaced.
regards,
Onno
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
