We've been blogging about what's coming in Dojo 1.1 for a while now, and today I'm happy to announce that Dojo 1.1 Beta 1 is available.
There's so much great new stuff in this release that it's hard for me to know where to begin, so I'll let the release notes do most of the talking. The team has closed nearly 500 bugs, and it'll be closer to 700 by the time 1.1 goes final. We've been busy.
Of particular note:
- major overhauls and updates to the Dijit themes thanks to Torrey Rice and Nikolai Onken
- CSS optimization and multiple versions of Dojo side-by-side, courtesy of the irrepressible James Burke
- BorderContainer and ExpandoPane layout containers
- animation support in
dojox.gfx - new easing functions in
dojox.fxand code highlighting indojox.highlight dojox.dtlis now at feature parity with Django's implementation and has extensions for handlingdojo.dataresults cleanly- major updates to
dojo.dataintegration with the grid and tree and new data stores including JsonPath for simple JSON queries and a SnapLogic store to make your lightweight data integration tasks a snap - updated accessibility support to track the latest changes in Firefox 3's WAI-ARIA implementation
- Adobe AIR support (courtesy of Adobe and SitePen)
- drop-in backwards compatibility with Dojo 1.0
...and that's keeping it short and sweet.
We'll have more updates as we do another beta and a release candidate for 1.1, but you can start playing with it now to see how much faster, smoother, and polished it is.
tickets
FYI, I've added a 1.1b1 version to trac so we can monitor bugs in the beta build. So please help us in our beta testing by filing tickets about broken functionality, and please use that version when filing bug tickets.
I'm updating the version of
I'm updating the version of dojo we have in our SVN repo for Psych Desktop to this version so we can help send you guys bug reports in a real-world application. It works out really nicely because we're due around march 20th and you guys are due at the beginning of march.
Edit: As of revision 1179 we're using 1.1 beta
Re; Psych Desktop
That's really cool... definitely do bug us about our bugs that impact you.
re-look at the library build
Hello,,,
I am a newbie to dojo.. and just gone through some intro concepts of the dojo toolkit. I understand it's a great job. Kudos to you guys...!!!
I downloaded the v1.1 and it contains all the samples, test runs and it is very necessary to understand how dojo works.
When we use the same version in any application, it's gonna take up some space for the tests and demos which came along with the toolkit, which the application may not require to be hosted.
I have a suggestion in the make of the build/toolkit. You could separate the testing elements of the toolkit and the javascript libraries which actually do the work so that anybody can use without any worry. I mean, the examples, demos and the test scripts/html can be separated out leaving the core at one place which would be easy to embed in any application.
Hope it helps everybody.
regards,
Uresh :-)
Hi Uresh, So its funny you
Hi Uresh,
So its funny you say that, I've written a script that safely removes all the cruft from a release after build, so you can still utilize the build system, then "clean" the tree and have an optimized code base. It is just an experiment at this point, but I've already been talking to the build mastermind jburke about incorporating some of the functionality into the official build process. My dojo-release-mini.tar.gz is 1.1 megs after all is said and done, a modest size when considering it's a 100% usable dojo tree.
I like all the samples contained within the codebase. It's a lot easier to find things, and maintain. Space restrictions on web hosts are nominal anymore, so my motivation for creating this optimized archive was more for deployment, in places where you'd actually ship the whole toolkit w/ your app or product. The current release archive is a great learning tool. You can read the source, see the examples, and everything wonderful. My version after compression is obfuscated it would be near impossible to debug, and provides no meaningful examples or documents (comments) of any kind. Perfect for dropping in after development, or shipping, but really really bad news during.