Order of Require

[jaykapalczynski]

1.  Is there a specific order in which the below have to follow i.e. the PARSER has to come before the MAP  or the READY before the connect?  or can I place them in ANY order as long as the order is the same in the REQUIRE as it is in the FUNCTION
2.  I noticed the containers and Dom/Ready do not require anything in the Function why is that?

Thanks

    require([         "dojo/ready",         "dojo/on",         "dojo/_base/connect",         "dojo/dom",         "dojo/dom-construct",  "dojo/keys", "esri/SnappingManager", "esri/dijit/Measurement", "esri/sniff",         "dojo/parser",         "dijit/registry",   "dijit/layout/BorderContainer", "dijit/layout/ContentPane",  "dijit/layout/AccordionContainer",  "dojo/domReady!"     ], function(         ready,         on,         connect,         dom,         domConstruct,  keys, SnappingManager, Measurement, has,         parser,         registry     ) {

[TimWitt · Accepted solution]

Jay

this should clear up a lot of your questions. In addition, since all modules are loaded at the beginning, the order doesn't matter, as long as you keep the order in your require([]) the same as in your following function() and put "dojo/domReady!" last in your require([]) list.


Tim

[JeffPace]

Containers dont need aliases if you only use them in defined HTML

If you try to create them programmatically (new BorderContainer) you will need an alias.  It is my opinion, for both readability of code and preventing errors down the road, to just add aliases for everything.  It doesn't hurt anything and can prevent alot of problems

[jaykapalczynski]

Thanks for your thoughts....both of ya....appreciated.
Thats what I was figuring...I had the containers aliases in there at one time but took them out as another example didnt have them in there.
Cool...thanks....

[JohnGravois]

just to pile on...
when each individual module is loaded, its own dependencies are resolved automatically by the dojo loader, and additional requests for supporting code are made automatically, if necessary. 

the require callback isn't triggered until all the asynchronous responses have been received.  this allows us to load modules in whatever order we like.