On 11/2/05, matthew clark <[EMAIL PROTECTED]> wrote: > And, if you use widgets across several pages, individual JS files will be > cached, saving bandwidth. If you build a JS file for each page, you'll only > be able to cache it for each page. Could cause bigger downloads.
I'm now starting to think in terms of generally having a JavaScript file for a library of widgets as being a better overall goal than JavaScript that is individual for a widget. It's good for caching and reduced roundtrips to the server. I do think, for flexibility's sake, it's good to also allow per-widget JavaScript. > Now, all that being said, I come from an unstructured web development > environment. Doing things inside the mega framework of TurboGears could > make my comments irrelevant. Not at all... no matter how cool we make TurboGears on the server-side, the browsers are still the same browsers and your comments are completely relevant. Kevin
