> 1) Defining an framework-independent API to be used by Tapestry (events, > DOM manipulation, selectors, etc). Maybe there's something similar out > there, not necessarily Tapestry-related.
Sizzle selector (http://sizzlejs.com/) might be a nice contender, but I haven't looked into it indepth yet. > 2) Reimplement Tapestry.js in other Javascript frameworks (I guess jQuery > would get some votes here :)). > 3) Reimplement Tapestry components. > > Another issue would be define a Tapestry-IoC symbol (just like > SymbolConstants.PRODUCTION_MODE) to define the default Javascript framework > to be used. This way, we could have a single Autocomplete mixin, for > example, that looks what JS framework to use and our templates and page > classes would be JS framework-independent. But that's the easy part. :) I'll dig into the code the next couple of days to get familiar with the way things work right now and see what I can do. regards, Onno
