Monday, November 5th, 2007

Dojo 1.0 Released: The Granddaddy is Born

Category: Announcements, Dojo

Ben and I have been talking about Dojo forever. We talked about Net Windows and MochiKit before it, and when a slew of JavaScript hackers came together to create Dojo we knew it would be a good thing.

Dojo was more than an XHR wrapper, which consisted of the majority of libraries that appeared on the scene right after Ajax came to life. Dojo always felt like the standard library that JavaScript never had. It wasn’t just for the browser, it was for all JavaScript.

Recently the Dojo team decided that this was all well and good, but the pragmatic reality was that the browser was where their users were using them, so it was time for a rewrite. From scratch they rebuilt a fast lean Dojo core that only has what you need. They kept the core philosophy, and the build system is still there, as well as the great widget system.

The end result is Dojo 1.0, a huge milestone for the project as they took 1.0 so seriously.

Recent Features

  • Accessibility including keyboard navigation, low vision support, and ARIA markup for assistive technologies
  • High performance grid widget supporting 100,000+ rows of data
  • Browser-native 2-D and 3-D charting
  • A full library of easy-to-use, attractive UI controls
  • Universal data access for simple and fast data-driven widget development
  • Internationalization with localizations provided for 13 major languages
  • CSS-driven themes to make customization and extension simple
  • Dojo Offline, based on Google Gears, which makes offline applications easy to build
  • Support for the OpenAjax Alliance Hub 1.0 to guarantee interoperability with other toolkits
  • Native 2-D and 3-D vector graphics drawing
  • Access to many more widgets and extensions through the Dojo package system

Take a look at the full press release or watch our chat with Alex about the release. Alex is always great to talk too as he is very honest, and carries the torch nicely for the Open Web. Congrats to the entire Dojo team.

Comet Daily

SitePen has also released a new website dedicated to the discussion of Comet: Comet Daily. A group of the Comet experts are all signed up and ready to show you that PUSH is back!

Posted by Dion Almaer at 9:18 am
22 Comments

++++-
4.1 rating from 62 votes

22 Comments »

Comments feed TrackBack URI

Dojo source is fairly well documented, but I’d prefer id they used scriptdoc instead of their own(?) documentation format. Scriptdoc’ed code enables code assist if you use the Aptana IDE. I’m aware of at least three major APIs that use scriptdoc: Ext, Yahoo and OpenLayers, and this format is very useful.
http://www.scriptdoc.org/specification.htm
http://www.aptana.com/docs/index.php/Documenting_your_code_using_ScriptDoc

Comment by Les — November 5, 2007

Congratulations!!

I did a double take at this news… glasses of bubbly all round… great work guys!

Fantastic…

Comment by Chris — November 5, 2007

I was only thinking of this and wondering when it would happen the other day. Congratulations to everyone involved. I look forward to using it.

Comment by Rory — November 5, 2007

I just tried the fisheye (version 0.9), IE 7 don’t want it, so as Safari, Firefox renders a vertical fisheye, and Opera took 7 minutes to render the same.

It’s cool to release new version, but it’s even cooler to have something working before you do so.

Comment by Samori Gorse — November 5, 2007

Hip Hip Hooray!

Hopefully this will hit the AOL CDN soon. http://dev.aol.com/dojo

Comment by Jay — November 5, 2007

@samori – the common ‘vertical fisheye’ problem is usually a failure to include Fisheye.css – also, though most dijits do, Opera 9 is not officially supported by the widget system, and patches are gladly accepted to aid in compatibility. the Fisheye widget is also in dojox – the experimental/extras part of the toolkit – it lives on a separate release cycle than the dojo core and dijit widget system. It’s also marked “experimental” so you know it’s not production ready. the advantage of having dojox is that the code is there to make more stable and use if stable enough, and very transparent to the developers. A lot of stuff in dojox “doesn’t work in all browsers”, which is why it’s in dojox – a gestation period before it can be called “stable” … hope this helps clarify.

Comment by dante — November 5, 2007

… not to bash dojox though, btw – there are a lot of great projects in there that are very stable. another one of it’s “roles” is for projects that don’t really fall under the category of “dojo core” or “widget”, like dojox.offline or dojox.gfx … Hopefully, the README file in each dojox project folder will assist in determining the usefulness and stability of each project, should you feel you need any of the functionality found within.

Comment by dante — November 5, 2007

Bravo for a great 1.0 release…

Ludo

Comment by Ludo — November 5, 2007

Congratulations to Alex, Dylan, and the rest of the team!

Comment by Sam Stephenson — November 5, 2007

Nice congrats to the Dojo JS gurus. I personally need to take another look at Dojo on my next project… there looks like a ton of great stuff there …specifically like the idea of the Google Gears wrapper/abstraction, very cool.

Comment by Mark Holton — November 5, 2007

Nice to see the milestone reached!
but.. where’s all the bling-bling demos and examples showing of the new (and old) stuf?

Comment by Fredrik — November 5, 2007

@Fredrik – there are actually many Dojo/Dijit/Dojox examples and demos, but you will need to do some footwork… search for the demos and tests folders.

Comment by Les — November 5, 2007

As much as I like these ajaxian videos, I still have to mention that the audio in this one just like the recent java video gives me a migraine :(

Comment by Magnus — November 5, 2007

This is an important milestone in making Ajax safe for the enterprise. We don’t need another fisheye widget, we need an open source toolkit that can beat Silverlight! Dojo 1.0 may not be the ultimate winner of the Ajax wars, but it sure sets a high bar for any toolkit that wants to beat it as a viable RIA toolkit for the enterprise. I wrote more of my thoughts here:
http://www.keeneview.com/2007/11/why-dojo-10-matters-ajax-now-enterprise.html

Comment by C Keene — November 6, 2007

Documentation still needs work! Same as before (v0.9)

Comment by Mike — November 6, 2007

Tragic.
Absolutely tragic.
They are expecting developers to *develop* using this thing, and expecting users to put up with the huge ugliness of it and lack of features?
No. Dojo is a non-starter.

Comment by Animal — November 6, 2007

Is there an online example of Dojo’s virtual / lazy loading grid?

Comment by Sanjiv Jivan — November 6, 2007

Here’s hoping Dojo’s commitment to accessibility lights a fire under the rest of the Ajax frameworks.

Comment by Ryan — November 6, 2007

Sorry? Please clarify “Dojo’s commitment to accessibility”.

Comment by Olmo Maldonado — November 7, 2007

Olmo:

All Dijit widgets provide keyboard access (focus setting, etc.), high-contrast mode support and detection, and WAI ARIA role and state hinting for assistive technologies.

In short, Dojo goes far beyond the letter of the law for accessibility in order to really build a great experience for those using assistive technologies.

Regards

Comment by Alex Russell — November 7, 2007

@Sanjiv – you can find Dojo grid examples at the dojotoolkit site here:

http://archive.dojotoolkit.org/nightly/dojotoolkit/dojox/grid/tests/test_grid.html

All of the basic demos use a stock data model that (arbitrarily) has 1000 rows. Technically, these *are* virtual data sets (even 1000 rows is far too much to render all at once), but it’s not as impressive as if it were 100,000 rows.

For more information, go to the dev.wavemaker.com forums here:

http://dev.wavemaker.com/forums/?q=node/1216

Comment by C Keene — November 8, 2007

I hear good things about Dojo, however I feel the documentation just isn’t good enough. It seems like it’s all available and detailed but the organization of it is just not good enough to sway me away from other frameworks that I am comfortable working with.

Also, another downside is that it only supports, “Latest Safari (currently 3.0.x), 2.0 support was dropped upon the release of Leopard”

I don’t know who does projects that are only compatible with Safari 3. That’s bad.

Comment by Rob — November 10, 2007

Leave a comment

You must be logged in to post a comment.