> > Maybe it doesn't have to be plain js since there's a lot to be gained from > these libraries. Perhaps all Tapestry's .js files could be moved to a > tapestry-prototype module, each of those files could then be reimplemented > in a tapestry-jquery module. > A problem remains with script snippets written directly from > renderSupport.addScript() > It sounds pretty cumbersome to maintain multiple modules though.
The main reason for the plain-Javascript solution is indeed that you will need to support the Javascript files for each and every framework you're going to support in the future. This will make writing new components quite a lot of work as well because you will need to write/update the code for all supported libraries. By sticking to plain Javascript, you don't have that problem. regards, Onno
