On Tue, Jun 16, 2009 at 9:03 AM, Onno Scheffers<o...@piraya.nl> wrote: > The easy way (for me) is to expect the framework-specific implementation to > support CSS selectors, the hard way would be to rewrite all areas using > advanced selectors in the Tapestry.js file to use more simple selectors.
I don't see any point in rewriting any selector. Anyone trying this will have to deal with all the browser implementation differences that the Prototype/jQuery/Dojo/etc already done, and it's a lot of work. Let's just try to define exactly what are the Tapestry Javascript needs and create a JS framework independent API for that (something that Onno is already doing) and create a Prototype and jQuery implementations of it. Otherwise, we'll spend more time with Javascript itself than making Tapestry JS framework-independent (our goal here). By the way, great work, Onno! -- Thiago --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
