The dojo build system can compress its own and your (or tapestry) js packages all into one file. You'll probably have to dig around in manual.dojotoolkit.org to find more.
When you are really getting serious about optimizations though I would check out the jslinker provided with dojo as well. It will condense your js into ~exactly~ only the functions/code your app uses. I haven't actually run it myself but I know Andy has. On 10/31/06, Josh Long <[EMAIL PROTECTED]> wrote:
I'm experiencing a ridiculous slow down in speed on a front page because the initial page uses a few widgets whcih themselves use other dojo packages, few of which are included in the default dojo.js that comes bundled with tapestry. So, i built a dojo.js equivalent to te kitchen sink build with a few extra packages (dojo.dom, dojo.regexp, and more are a few packages i added for good measure.. anyway, this has worked out pretty well thus far: the front page loads all of the code from dojo/* in one js file (well, i do see two xmlhttp requests for the templates of a few widgets, of course, but everything else is readily available.) instead of in 40 seperate, non compressed, header-incurring requests. I have the tapestry source code checked out and have one more thing i want to do but im not sure what the right mechanism is: how do i get all the tapestry packages to be in one fle that i can load manually like i do dojo.js? that way id have only two files that i could tune individually that load the code specific to my app and theyd all be cacheable (ie, not paged trough xmlhttp, which is a problem fr example in FF pre 1.5. .) .js files and theyd all require only one round trip and no headers.. we have pretty bad latency are really looking to streamline individual requests to the server. Any help would definitely be appreciated... thanks, Josh
-- Jesse Kuhnert Tapestry/Dojo/(and a dash of TestNG), team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
