Quick Installation
There are three main ways to install Dojo:
- Install nothing! Use Dojo from AOL's Content Distribution Network (CDN).
- Install the latest release on your server
- Install directly from source control
Use Dojo from CDN
This method is quick and painless! You simply load Dojo through <script> tags pointing to the AOL CDN. You don't need to invest any of your own server disk space or resources nor will you need to install Dojo locally in many cases. Instructions are available on using Dojo from the CDN.
All of the Dijit examples in this book load Dojo through this method. You can literally copy and paste any example in Parts 1 and 2 onto your own web server and it will work as-is! In Part 3, where examples are most often code fragments, we'll tell you any modifications needed to run the example on CDN.
Use Dojo from your Own Server
For you traditionalists out there, you can download, install and use Dojo the old fashioned way.
- Download the latest build from http://dojotoolkit.org/downloads.
- Uncompress the file onto your web server. Assuming you install it under the directory /js, when you're done, the file system should look something like this:
- With your browser, open http://yoursite.com/js/dojo-0.9.0/dijit/themes/themeTester.html You should see a page like this:
You've got a working Dojo!
Getting the Nightly Build
Finally, for those of you who live on the edge ... you can get the latest, greatest code directly from the Subversion code repository.
- Printer-friendly version
- Login or register to post comments
- Unsubscribe post
AOL CDN Link
To use 0.9.0 from AOL's CDN, just include this script tag in your page:
<script type="text/javascript" src="http://o.aolcdn.com/dojo/0.9.0/dojo/dojo.xd.js"></script>
See http://build.dojotoolkit.org/0.9.0/ for more details.
Dojo works locally, as well
Because it's a client-side framework, most of Dojo will work when installed on your filesystem, accessed with file: URLs. This can be a convenient way to experiment with Dojo. Once you start to interact with server data, browser security requires that you deploy your page on a web server.
[Edit: seems like this no longer works in FF3]
CDN Link
So the "instructions are available" link goes back to this webpage, and there are no instructions for the CDN link at all. There is a comment with the 0.9 version, so I will include a link to the info for the 1.0.0 version as well.
http://dojotoolkit.org/2007/11/06/dojo-1-0-0-available-aol-cdn
Bug on the page
please fix the link: Instructions are available.
it's redirecting onto the same page
problem in the markup
sorry about that. fixed.
Trouble getting this to work
I can't seem to get this to work. I used svn to download the Dojo toolkit (0.90, 1.0 and 1.02) and followed the tutorial at http://code.djangoproject.com/wiki/AddDojoEditor to use the Dojo editor for my textareas. I only get javascript errors in IE7: either "could not load 'dojo._base.lang';last tried './_base/lang.js'" or "dojo not an object". Firefox says nothing and does nothing. I get the same when referencing CDN.
What am I doing wrong?
that example is very old
apparently, that example is based on Dojo 0.4, which had a very different naming structure. It's hard to say exactly what's going on without seeing the example in its entirety running, but if it's based on what's on that page, it's not going to work with the new versions of Dojo. If you want to try the editor, I'd suggest consulting the Dojo book: http://dojotoolkit.org/book/dojo-book-0-9/part-2-dijit/advanced-editing-...
A good sanity check for the content on *this* page would be to load the themeTester.html page or some of the examples in the dojo/tests or dijit/tests directories. If that works and you have trouble with specific examples, please bring your questions to the forum.
Really a issue that the build script can not work in the release
We tried to build with some customize build profile. But failed in 1.0.2. Any plan for fixing this issue? It works in the former release.
need more information
I'm not sure we're aware of this issue. It's probably best to file a ticket on trac. Please provide steps to reproduce the problem as well as build output.