> > I understand your solution, but that just introduces a second "tapestry > supported" javascript library. What if yet another library is better at some > point, or some people prefer another one like yui or dojo (remember this was > the "preferred" in t4 days, not that long ago). > Do we really want to include jQuery as well in tapestry itself?
Like discussed earlier, the main point is to isolate Tapestry from framework-dependencies. Ideally Tapestry wouldn't force any JavaScript framework onto you, but a good first step is to create the isolation layer and offer a second framework-specific implementation as a proof-of-concept. After that nothing is stopping anyone from creating additional support for other frameworks or even a plain JavaScript implementation. For now jQuery is the most popular JavaScript framework with an awful lot of plugins available. A lot of people would like to use it instead of Prototype. > I would suggest having one or more projects on tapestry360 which contain > the javascript libraries. These can then be included using > @IncludeJavaScriptLibrary and a classpath location (preferably defined as a > constant), avoiding the double inclusion. I think the way to distribute it is not up to me. I'm first going to see if I can isolate things and get it all working in the first place. I am not a Tapestry committer. I'll just open up my work and then its up to the committers to decide what to do with it. They can just as well decide not to do anything with it altogether. Google already hosts quite a repository of JavaScript framework, so theoretically no framework needs to be included in Tapestry at all. It just gives you more ease-of-use and control if it is included. regards, Onno
