The change in JavaScript is to support several goals: - A good transition from Prototype.js to jQuery (or perhaps something else in the future) - Reduce the total amount of JavaScript sent to the client - Allow more of the JavaScript to transfer in parallel - Make it easier to override Tapestry's built-in behaviors - Improve page loading speed
Having a single JavaScript event handler added to document.body, rather than having N handlers attached to N DOM elements, is a big win performance-wise. It also allows any particular DOM element to change the behavior by adding a specific event handler at that DOM level and not allowing the event to propagate up. The Tapestry docs have been updated with more information, such as: http://tapestry.apache.org/javascript-modules.html On Wed, Nov 12, 2014 at 3:13 AM, Paul Stanton <pa...@mapshed.com.au> wrote: > Hi, > > so like many developers (i'm guessing) I'm not quite up to speed with all > these new javascript frameworks: requirejs, closure, etc etc and to be > honest I really didn't see a problem with the namespace model of the past. > I'm not open to learning but it seems like a paradigm far removed from what > i'm used to. it doesn't seem object oriented at all for example. > > that aside, can someone please point me (and other readers) to some basic > examples to get us started in this brave new world. the first thing I would > like to achieve is to be able to call some page or component specific > marshalling code with page/component context parameters. > > your helpful attitudes will be appreciated! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- 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 @hlship
