As a start, anything that deals with Javascript should be moved away from the core, since it's not essential. a tapestry-ui module would be great starting point.
When i say forcing, i mean that Prototype is already built-in, rather than letting me choose which Javascript framework do i want. Thiago H. de Paula Figueiredo wrote: > > On Wed, Jun 10, 2009 at 11:32 AM, ice<fra...@gmail.com> wrote: > >> It seems a bit awkward to have a project called tapestry-core that >> depends >> in two third-party javascript libraries. > > The problem is: how would Tapestry do that? Not using any framework? > This would mean the committers would need to spend an awful lot of > time rewriting something that Javascript frameworks already do. Not > only this, but also to cope with the insonsistencies between browsers. > Defining an API that could be implemented in Prototype, jQuery or > another framework? More viable, but still a lot of work. > >> It's not just java developers who are affected by using Prototype,but >> also >> designers, as it is the case in my project. > > Tapestry is not forcing you to use any Javascript framework, just to > use jQuery.noConflict() and jQuery() instead of $() when you want ot > use jQuery. > > -- > Thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > > -- View this message in context: http://n2.nabble.com/Switch-from-Prototype-to-jQuery--tp2245624p3056449.html Sent from the Tapestry Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
