I am proud to announce what is now officially the coolest-numbered-dot-release in Dojo history: The Dojo Toolkit 1.2.3
Both 1.2.1 and 1.2.2 were released silently and were relatively short-lived. 1.2.3 is expected to be the last release of the 1.2 branch, and is very stable. This release includes several critical fixes to ContentPane, and many low-risk changes to the 1.2 release. It should be a 100% safe migration for 1.2 users, and offers better support for 1.1 users wishing to migrate.
Both CDN's have been updated to point to this new release:
Google: http://ajax.googleapis.com/ajax/libs/dojo/1.2/dojo/dojo.xd.js
AOL: http://o.aolcdn.com/dojo/1.2/dojo/dojo.xd.js
It is worth pointing out: the above URL's use a fixed minor version "1.2", as opposed to including the revision number as "1.2.3".
While the URL: http://ajax.googleapis.com/ajax/libs/dojo/1.2.3/dojo/dojo.xd.js works, it is always recommended you exclude the revision: http://ajax.googleapis.com/ajax/libs/dojo/1.2/dojo/dojo.xd.js -- when a new version is released, you will automatically be updated to the latest dot-version ...
Thanks be to Google and America On-Line for their continued CDN hosting and support of the Dojo Toolkit, to all the developers working and testing in the branches, and to all the Dojo users for all the testing and feedback provided during this last cycle --
Happy Dojo'ing.
Release Notes
Hi. Where do I go to read what's different between 1.2.3 and prior releases?
In particular, I'm getting this warning:
Use of getBoxObjectFor() is deprecated. Try to use element.getBoundingClientRect() if possible.
However, I'm not calling this method at all. I'm thinking that maybe it's part of the DND package, b/c my DND function is throwing this error: "this.dndObj.insertNodes is not a function" where as it was working fine prior.
Love some pointers in the right direction.
thanks.
Peep This
http://trac.dojotoolkit.org/roadmap?show=all
I troll the above link as I stay up on the goings ons... enjoy.
Unit Tests?
I had been using Dojo 1.1.1 before I upgraded to 1.2.3
Before, in 1.1.1 there was a tests directory under the dojo folder. This is where the unit tests were.
In 1.2.3 the tests directory no longer exists.
Has it been moved?
they are still available in
they are still available in the -src release, the normal release includes no tests of unit tests. 1.3 will include the re-introduction of the uncompressed.js files, though they are easy to build yourself.
thanks
I'm a little new to the whole -src release and building stuff myself.
Is there a link that you could post that explains both?
Thanks!
1.2 vs 1.2.3
One thing to keep in mind, the 1.2 revisioned url from Google has cache expiration set to 1 hour from the request, while the 1.2.3 url from Google has expiration set to one year from the initial request. If your site has a good number of repeat visitors, they can get a much better cached load experience if you use the 1.2.3 urls.
True story. This only
True story.
This only applies to the directly called resources (css file, the base js file, etc). Once dojo figures out what version it is, it calls it's resources directly from the dot-release URL that has a 1 year expiration, but there will always be a few resources that get the 1 hour expiration.
Bummer. I understand why they have to do that, but...
Dojo
I saw Dojo at a customer project and I must say: a very good libary!
Dojo leaks in frames in IE
Hey. It seem Dojo leaks in frames. When a page with Dojo is shown in a frame it seems dojo doesn't unload at all(?) or leaks for whatever other reason.
Simple case of just loading dojo.js with an empty page (with no other script) in a frame shows the memory leak. The leak is small (but still present) for referencing dojo in repository (not sale, when dojo.js is small), but is really a problem for built dojo (baked, dojo.js.uncompressed.js).
For release I get about 0.8MB leak for each frame on refresh. I suspect any widgets present on the page add to the leak. Perhaps unload procedure isn't run properly in the frame?
To reproduce - unpack attachment to the root of the dojo source repository (together with dojo.js file). Load test_frames.html. The problem isn't as noticeable with fresh (not built dojo) as it is with baked dojo.
bugs.dojotoolkit.org
It's best to report these problems at bugs.dojotoolkit.org (using your dojotoolkit username/pw) if you haven't already. Thanks!