On Fri, Oct 15, 2010 at 10:29 AM, Michael Gentry <mgen...@masslight.net> wrote: > I'm not sure this always makes sense to do. One of our applications > has a couple wizard-like interfaces where you answer a few items and > move through until the end. Each page had a tiny little bit of > page-specific JavaScript to be delivered in addition to the common > JavaScript (Prototype, Tapestry, etc). If Tapestry is always > re-packaging all of the JavaScript, plus the small page-specific > JavaScript, into a single JavaScript file, isn't this more wasteful? > The browser can't cache Prototype, but has to re-download it each > time, right? >
That is exactly what drove the changes in JavaScript aggregation for 5.2. What's you'll see now is a request for a core.js (the core JavaScript stack: prototype, etc.) plus additional requests for each "non-stack" JS file (if any). In both 5.1 and 5.2, per-page JavaScript initialization is in a <script> tag. > Thanks, > > mrg > > > On Fri, Oct 15, 2010 at 12:19 PM, Howard Lewis Ship <hls...@gmail.com> wrote: >> That article doesn't take into account the things that Tapestry does for you: >> - Combines prototype.js with other JS files to form a single JS file >> (this is done on-the-fly) >> > > --------------------------------------------------------------------- > 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 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
