> > IMHO, the whole Prototype/jQuery compatibility problem is that both > define a $() function and they work differently, so you can't use code > based on both of them at the same time without modification. Some time > ago I used a jQuery color picker in a project. Even using the > jQuery.noConflict() method, I still needed to replace $() fror > jQuery() in the color picker code.
This simply means that particular plugin didn't adhere to the jQuery plugin guidelines (http://docs.jquery.com/Plugins/Authoring). A plugin should never use $() directly otherwise it will indeed break the jQuery.noConflict method. You cannot blame the framework for a faulty plugin. Besides that, the issue is that people want to work with what they know. If Tapestry can remove the dependency on Prototype, people that want to use Prototype are free to do so. If they rather use jQuery, they can as well. If you have to use both (if you are using Chenillekit for example), you'll have to include both, but then you can only use plugins that are written the way they should have been written. Summary: having Prototype and jQuery rely on the same function (the > same name) both with different functionalities screwed us. Not really. A jQuery plugin screwed you. regards, Onno
