Opened 12 years ago

Closed 12 years ago

#3772 closed defect (fixed)

xdomain loading: when loading local modules, have to do some weird things with dojo.baseUrl and module paths?

Reported by: James Burke Owned by: James Burke
Priority: high Milestone: 0.9
Component: Loader Version: 0.9
Keywords: Cc:
Blocked By: Blocking:

Description

To load a combination of local and xd modules, I ended up with this djConfig:

		djConfig = {
			isDebug: true,
			baseUrl: "./",
			modulePaths: {
				tyby: "tyby",
				dijit: "http://o.aolcdn.com/dojo/0.9.0beta/dijit"
			},
			debugContainerId: "debugArea",
			xdWaitSeconds: 5
		};

It would be nice not to have to specify the CDN paths since they should be implied. Ideally, the dojo.baseUrl would not be needed either.

Change History (1)

comment:1 Changed 12 years ago by James Burke

Resolution: fixed
Status: newclosed

(In [10085]) Fixes #3772. The behavior in the bug is actual the correct behavior but this commit allows a way to auto-register the dojox, dijit and dojo prefixes for xdomain builds inside of dojo.xd.js, cutting down on the need for the pages to have to specify the paths.

Note: See TracTickets for help on using tickets.