john.c.cartwright

3.0 issues with custom modules

Discussion created by john.c.cartwright on Jun 17, 2012
Latest reply on Jun 17, 2012 by john.c.cartwright
Hello All,

I'm using both local and remote custom modules.  In 2.x, my dojoConfig was like:


  
var dojoConfig = {
   parseOnLoad: true,
   baseUrl: './',
   modulePaths: {
      'help_panel': 'http://maps.ngdc.noaa.gov/viewers/dijits/help_panel/1.1',
      'nos_hydro': './src/dijits/nos_hydro'
   }
};


Attempting to convert to 3.0, I changed to:

var dojoConfig = {
   parseOnLoad: true,
   modulePaths: {
      'help_panel': 'http://maps.ngdc.noaa.gov/viewers/dijits/help_panel/1.1'
   },
   packages: [{
      "name": "nos_hydro",
      "location": location.pathname.replace(/\/[^/]+$/, "") + "/src/dijits/nos_hydro"
   }]
};


which works for the local module but not the remote.  I also tried

var dojoConfig = {
   parseOnLoad: true,
   packages: [{
      "name": "nos_hydro",
      "location": location.pathname.replace(/\/[^/]+$/, "") + "/src/dijits/nos_hydro"
   },
   {
      "name": "help_panel",
      "location": "http://maps.ngdc.noaa.gov/viewers/dijits/help_panel/1.1"
   }]
};


but that didn't work either.  I've tried both the remote module as a Dojo 1.6 CDN build and as plain JS.

Can someone please provide me some guidance here?

Thanks!

--john

Outcomes