...I would hazard a guess that you're also probably attempting to load content via a ContentPane while the document actually loads as well; this can be a common error to make, because you might think that you're lazy-loading things when in reality you're actually causing more requests to be made over the wire--and probably pushing up against that 2 connection limit most browsers have.

Its more than possible to write Dijit-based apps with a *lot* of widgets on a page and not have the browser load very slowly (dante mentioned a few public ones, there's a number of private ones as well), so I would be thinking that you're running across architectural issues as opposed to Dijit ones (Dijit can be very easy to abuse ;).
---

Probably you should be posting this thread in the Dijit support forum as well; dante's really good about looking over the entire forum set but probably you'll get better, more accurate help if you start a similar perf thread in Dijit support.

...I think you have some major server optimization you need to do; even though I did see what you were talking about with dojo freezing up the app, by far the sheer amount of tiling you're using is taking a long time, particularly when each image request is being served by php and not directly from a filesystem.

Loading the app in Safari and watching the network progress showed a small loading gap between LayoutContainer and SplitContainer; that might have just been bad timing on my part but I think your first step would definitely be to do a build and see what happens then.

I also think you would be better served by removing the other 3 JS libraries you're using and simply use the Dojo equivilents; not sure about your ajax one but the Walter Zorn library is pretty old and can step on a lot of other JS toes, so to speak.

Hi, your video was very helpful. Really appreciate that you did that up on the fly. However.. I just have one piece left. I did the new release... and I have my release folder intact. A few confirmations and a few questions.

Confirmations
1. I need to point to the dojo.js in my release/dojo/dojo folder.

Questions
1. Do I leave all the require statements in place?
2. I never used layer.js before... Do I need to include that and where should I include that?

In essence, how should the following segment be changed to utilize the built components?

I have changed it and so far I have not seen a change in the file size. So I anticipate that I am not doing something correctly.
My build file...

dependencies = {
        layers: [
                {
                        //For 0.9 you normally do not specify a dojo.js layer.
                        //Note that you do not need to specify dojo.js as a dependency for
                        //other layers -- it is always an implicit dependency.
                        name: "dojo.js",
                        dependencies: [
                                "dojo.parser"
                        ]
                },
                {
                        //This layer will be discarded, it is just used
                        //to specify some modules that should not be included
                        //in a later layer, but something that should not be
                        //saved as an actual layer output. The important property
                        //is the "discard" property. If set to true, then the layer
                        //will not be a saved layer in the release directory.
                        name: "string.discard",
                        resourceName: "string.discard",
                        discard: true,
                        //Path to the copyright file must be relative to
                        //the util/buildscripts directory, or an absolute path.
                        copyrightFile: "myCopyright.txt",
                        dependencies: [
                                "dojo.string"
                        ]
                },
                {
                        name: "../mine/layer.js",
                        resourceName: "mine.layer",
                        dependencies: [
                                "mine.layer"
                        ]
                }
        ],

        prefixes: [
                [ "dijit", "../dijit" ],
                [ "dojox", "../dojox" ],
                [ "mine",  "../mine" ]
        ]
}

//If you choose to optimize the JS files in a prefix directory (via the optimize= build parameter),
//you can choose to have a custom copyright text prepended to the optimized file. To do this, specify
//the path to a file tha contains the copyright info as the third array item in the prefixes array. For
//instance:
//      prefixes: [
//              [ "mycompany", "/path/to/mycompany", "/path/to/mycompany/copyright.txt"]
//      ]
//

But i've used the technique in client applications. The theory is simple, but could get horribly complex in practice.

I've just had a neat idea on how I could use the themeTester as an example. When time permits, I will make it available. The jist is: break each of the parts of the themeTester into bite-size pieces, and parse one piece at a time, stalling momentarily in between giving the browser time to catch up.

To increase INITIAL load time, we can manually load in the HTML segments when needed, and parse them as they come in. When you have large large pages, all you really need to load initially is the css, dojo.js + layer.