- The Book of Dojo
- The Dojo Book, 0.4
- Part 1: "Introduction"
- Part 2: "Out of the Box" Dojo
- Part 3: "The Dojo Programming Model"
- Part 4: "More on Widgets"
- Part 5: "Connecting the pieces"
- Part 6: "Customizing Dojo Builds for Better Performance"
- Part 7: "Utilities"
- Part 8: "Internationalization and Accessiblity"
- Part 9: "Dojo Community"
- Part 10: "Fresh From The Shed" Dojo
- BookWriting
- Glossary
Part 6: "Customizing Dojo Builds for Better Performance"
Submitted by Carla on Fri, 02/02/2007 - 22:40.
When all of your testing is done and you're ready to distribute your application, you don't want to have to use a bulky source, or have the various resource used by your application scattered all over the place. As a web developer, you want a way to lower the number of file requests and the overall download size of your application code. Dojo provides a robust system that not only solves these problems, but also allows incremental loading of infrequently used resources. The following sections will show you how to build a profile that suits your needs and how to create a Dojo release to include in your HTML file.
Additionally, the build system allows for the creation of a compressed package file that contains all of the script code needed for your app, no more and no less, through an Ant build step.
The loader system allows you to list a single script include file which will then find and fetch resources as they are needed for your application from the Dojo source tree. This means in the simplest case, no build process is required and yet there is no need to include a script tag for every resource that is to be loaded.
Additional performance optimizations can be had by adjusting the web server or application code. Included in this section are some tips on both server side and client side changes that can make your application run faster.
