github-migration/jasmine-headless-webkit
1
0
Fork 0
Code Issues 39 Pull Requests 16 Packages Projects Releases Wiki Activity

Updated Using dojo and dojo class loading in jasmine headless webkit (markdown)

kidlingo 2011-07-26 07:42:26 -07:00
parent 1596fd4748
commit 2cfb605338
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Using-dojo-and-dojo-class-loading-in-jasmine-headless-webkit.md

@ -39,9 +39,9 @@ dojo knows where to look for mystuff/SomethingCool.js in the load path.
You do this by creating a global djConfig object before loading dojo.js, providing two key pieces of information. One is modulePaths, which is how you tell dojo where to find things. The other is baseScriptUri, which tells dojo where its home is. You do this by creating a global djConfig object before loading dojo.js, providing two key pieces of information. One is modulePaths, which is how you tell dojo where to find things. The other is baseScriptUri, which tells dojo where its home is.
Unlike djConfig.baseUrl, djConfig.baseScriptUri lets you specify the URL as a file URL, and dojo will load class files using file URLs instead of requiring a server. Unlike djConfig.baseUrl, djConfig.baseScriptUri lets you specify the URL as a file URL, and dojo will load modules using file URLs instead of requiring a server.
To create this global djConfig object, I include the test_bootstrap.js in the src_files list before dojo.js, which seems to ensure that test_bootstrap.js is run before dojo.js, thereby configuring dojo correctly when it loads. To create this global djConfig object before dojo initializes itself, I include the test_bootstrap.js in the src_files list before dojo.js, which seems to ensure that test_bootstrap.js is run before dojo.js, thereby configuring dojo correctly when it loads.
### Stop trying to load firebug.js ### Stop trying to load firebug.js