In got5, we miss the backward compatibility issue with project that use lot of prototype. In other hand, what is the use of importing prototype, when it's not needed.
As far as i can see in 5.2 CoreJavascriptStack, will be in charge of adding core part of js toolkit. So what would be the best way, to contribute to this core stack? for me it would be nice to - add prototype only if it's needed - set the order of core stack when using more than one toolkit ( jquery before prototype) - add core stack required when needed by a component (kind of @ImportCore) 2010/10/27 Thiago H. de Paula Figueiredo <[email protected]> > On Wed, 27 Oct 2010 17:30:16 -0200, iberck <[email protected]> wrote: > > Here there are more reasons to create the base components with jquery >> 46% of the applications on the web are made in jquery >> http://trends.builtwith.com/javascript/JQuery >> > > It's not just a matter of replacing Prototype with jQuery. Most of the > Tapestry apps and third-party packages built until use Prototype for their > JavaScript and backward compatibility is something very important to the > project. The JavaScript stacks is part of the solution to this problem. > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
