renaming dojo namespace breaks dojo markup dijits?

Question

Hi, I have an app that primarily uses programmatic custom dijit creation in conjunction with esri's jsapi (2.0). I thought the flexibility of changing the dojo namespace as described here looked nifty, but after some testing I have found that I can no longer create dijits in markup. Yikes! (or, what the heck am I doing wrong here ) In one page for testing start by adding the scopeMap item to djConfig, then reference the api, then reference some dijits like esriDojo.require("dijit.form.DropDownButton");, and then in the body try to create the dijit, but it will not work. When I remove the namespace customizations the DropDownButton works just fine. Does renaming the dojo namespace somehow break the in-line parsing on-load? Take out the scopeMap and change the require statements back to regular dojo.require and the DDBtn works fine. TEST PAGE testing dojo Scope Thanks, Loren

LorenMueller · Answer

Hi Kelly,
Now that I have implemented the change in my real code my local resources (custom dijits) will no longer load.  I get 'could not load cross-domain resources' errors now.  All of my djConfig settings are the same still, and I have implemented all the reccommendations from the dojo folks found here.  Any thoughts on why that might be breaking due to the namespace change?
Thanks! - Loren

LorenMueller · Answer

Thanks Kelly!  Works for me as well now.  Much appreciated.
Loren

khutchins · Answer

Loren, I ran a quick test and it works if you change the attribute dojoType to esriDojoType. Here's the revised code: testing dojo Scope