To me this is a worthwhile exercise for two reasons: 1. Abstraction from prototype (or any 3rd party library for that matter) is a good thing, it will make Tapestry more modular and agile going forward 2. Using native JavaScript for core Tapestry is sensible even if its more work.
Libraries will gain in popularity and fizzle out, whats important is extensibility, and thats what these guys want to achieve. Peter ----- Original Message ----- From: "Thiago H. de Paula Figueiredo" <thiag...@gmail.com> To: "Tapestry users" <users@tapestry.apache.org> Sent: Monday, 15 June, 2009 20:09:52 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: Switch from Prototype to jQuery? Em Mon, 15 Jun 2009 13:06:14 -0300, Piero Sartini <li...@pierosartini.de> escreveu: > Maybe we would see way more components for tapestry if they could be > build with jquery. They can be built with jQuery. I even made one that I plan to opensource later. I don't know why other people haven't done components that build on jQuery. -- Thiago H. de Paula Figueiredo Independent Java consultant, developer, and instructor http://www.arsmachina.com.br/thiago --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
