On Sun, Dec 2, 2012 at 10:00 AM, Lenny Primak <[email protected]>wrote:
> I disagree with the statement that most people are going to be using > Prototype or JQuery, but not both. > We have a lot of legacy components that use Prototype, but our new > components use JQuery. > Those components need to function properly on the same page. > We use noConflict mode and Tapestry-JQuery right now > I agree that for upgrades, the default should be the combined stack, or even no jQuery. jQuery will loads as a module, not a library, so it will be included only if the page needs it ... for instance, if you use the Autocomplete mixin (which is now based on the Bootstrap Typeahead plugin, which needs jQuery). I think for new apps created in 5.4, Prototype support should be off by default and I think the Maven archetype will reflect that. I'm also thinking about an annotation for which "foundation" is needed, so that a component that really needs Prototype can advertise that, and get a meaningful server-side error, rather than an ugly client-side failure. -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
