Hi everyone! I’m pleased to offer not one, not two, but THREE new Dojo releases for your consumption.
Dojo 1.4.4 is now available. This is a maintenance release that backports browser fixes to add support for Internet Explorer 9 and Firefox 4+. Information on which fixes were backported to Dojo 1.4.4 is available on the bug tracker. This is basically identical to the Dojo 1.5.2 release that happened…whenever that happened! A little while ago. Thanks to kgf for managing this release.
Dojo 1.7.3 is now available. This is a bugfix release that resolves several issues with the 1.7 branch of Dojo, including issues with the i18n subsystem, legacy modules, and the build system running on Node.js. It also fixes a significant performance regression from 1.6 when loading many legacy modules and includes bugfixes for several other components. The full list of fixes for Dojo 1.7.3 is available also on the bug tracker.
Finally, Dojo 1.8.0b1 is now available. This is the first beta of the new Dojo 1.8 release and includes several exciting new features. A blog post written by interim supreme overlord Dylan Schiemann provides an overview of many of the most significant new features and enhancements coming to Dojo 1.8. There are close to 700 new features, enhancements, and bug fixes in this release, including a brand new documentation parser (written by yours truly) that will make the API browser work correctly again. As usual, the running list of changes that have made it into Dojo 1.8 so far is at the bug tracker.
Dojo 1.8 is on track at this point for a release in mid-to-late July. Beta 2, if necessary, will be released in about three weeks. CDN releases for Dojo 1.4.4, Dojo 1.5.2, and Dojo 1.7.3 have been submitted to Google. I will post again once those are made available.
OK, that’s it from me! Have a great solstice weekend.
Colin,
Great news! While you’re speaking to the Google CDN people, can you please ask them to update their Google Loader metadata?
Load Dojo through Google Loader:
google.load(“dojo”,”1″) —– loads 1.6.1, should be latest
google.load(“dojo”,”x”)
google.load(“dojo”,”1.x”) —- fails, should load latest “test” version, so probably should point to same as stable
Thanks,
Nick
Hi Nick,
It is my understanding that at this point the Google Loader is no longer updated, so if you want the newer versions you need to inject the scripts yourself. (This is probably better from a performance perspective anyway.)
Regards,
I tried to follow the Dojo build tutorial :-
http://dojotoolkit.org/documentation/tutorials/1.7/build/
There are a few gaps in the Tutorial that make it very difficult to successfully run it (or being a newbie to Dojo I may be missing something)
1) The tutorial is referring to some sort of a project structure, but the structure itself has not been shown anywhere. For example the “Putting it all together” section says “Given a typical application that exists in the app package, a simple build script that builds everything into dojo.js would look like this: ….config snippet follows
2) Under the “Putting it all together” section – myapplication.profile.js snippet, layers section, there is a reference to main.js. But it is not clear what main.js contains.
3) The “Putting it all together” section, last para talks about a “configuration file that specifies the locations of all the packages used by the application”. However no code snippet is provided to illustrate the same.
It is my understanding that at this point the Google Loader is no longer updated, so if you want the newer versions you need to inject the scripts yourself. (This is probably better from a performance perspective anyway.)
thanks!