Join the DZone community and get the full member experience.Join For Free
The bad news is that the client-side is directly linked to Prototype and Scriptaculous (which are bundled right inside the Tapestry JAR file). These were great choices back in 2006, when jQuery was new and undocumented (or so my quite fallible memory serves). It seemed safe to follow Rails. Now, of course, jQuery rules the world. I've been talking for a couple of years about introducing an abstraction layer to break down the Prototype/Scriptaculous dependency; meanwhile I've recently seen that Rails and Grails are themselves moving to jQuery.
So suddenly, I have a number of goals:
- Support Prototype/Scriptaculous and jQuery as substrate frameworks "out of the box"
- Make the built-in Tapestry library first class: documented and release-on-release compatible
- Keep backwards compatibility to Tapestry 5.2
Opinions expressed by DZone contributors are their own.