Friday, March 28th, 2008

Dojo 1.1 Released

Category: Announcements, Dojo

The Dojo team has released version 1.1 which includes from over 800 improvements:

  • An easy to use and significantly improved Dojo API Viewer with some seriously great features, including the ability to easily find the original definition of a method that is “mixed-in”
  • A growing collection of demos, tutorials, and articles
  • A new BorderContainer Dijit, which is a much better way to handle layout-based widgets than SplitContainer and LayoutContainer
  • Significant performance improvements to dojo.query and dojo.fx
  • Support for Adobe AIR and Jaxer, and updated dojox.flash and dojox.offline APIs
  • Major improvements to Dijit infrastructure and widgets
  • All around Dijit theme improvements including the CSS structure for themes, refinements to the Tundra theme, re-introduction of the Soria theme, and the newly added Nihilo theme
  • DTL, the Django Template Language, is now available for use in widgets with dojox.dtl
  • Vector graphics animations
  • Additions to DojoX including an analytics package
  • Improvements to Dojo Data and RPC, and support for JSONPath
  • Many improvements to the build system including CSS optimization, multiple-versions of the Dojo Toolkit co-existing in the same document, and other great tools for optimizing performance

What is next for Dojo 1.2?

On to 1.2, where the focus will be on continuing to refine Dijit, the Dojo Grid, Dojo Charting, a better approach to DojoX, and much much more.

Posted by Dion Almaer at 9:33 am

4.4 rating from 72 votes


Comments feed TrackBack URI

Is there any UI Framework (like ExtJS or Dojo) but built ontop of prototype and scriptaculous?

Comment by ob — March 28, 2008

Dojo is getting some traction and it’s good to see it. There are three new Dojo-specific books being published. Check Amazon for the titles.

Comment by Les — March 28, 2008

I haven’t used dojo since 0.9. Can someone comment on how it performs in 1.0/1.1 now? I remember using it for a project and it was a dog as far as performance goes, but did provide some neat functionality.

Comment by tj111 — March 28, 2008


There are several strategies for optimizing Dojo, and unlike other toolkits we make the tools we use for solving problems like that available for you to use as well. If you can provide specifics, odds are that there’s a well-defined way to address any performance issue you may be seeing.


Comment by slightlyoff — March 28, 2008 looks all garbled to me in MSIE 6. Any reason?

Comment by Dov Katz — March 28, 2008

Great job, Dojo folks!
Dojo 1.0 is a HUGE imprevement from previous verisons. I haven’t checked out Dojo 1.1 yet. Not sure whether it has addressed one of the major concerns I have: Opera support?

I know Dojo core itself supports Opera, but Dijit doesn’t. This is a major problem preventing us from using Dojo on consumer facing applications. Does anybody know whether Dojo 1.1 release addresses Opera support? If not, does anyone know whether Opera will be supported going forward?

Again, great job, Dojo team.

Comment by Mark Arrington — March 28, 2008

@ob – ExtJs has adaptors for Prototype and many other frameworks.
@slightlyoff (alex I dig the name) congrats on the release :)

Comment by jdalton — March 28, 2008

@Dov Katz: Just filed Thanks.

@Mark Arrington: Something we’d love to have, but it just hasn’t been a priority given market share, and there’s currently nothing on our schedule for this. We’ve seen some of Dijit run on the latest Opera, but there’s clearly work (and much testing) to be done. Patches to fix Opera (without adding significant bloat) are welcome.

Comment by peller — March 28, 2008

Yes, though Opera has small market share, but its existence in the market is just a fact that web developers have to deal with (sometimes don’t just want to wish Opera goes away so that we have one less browser to test?).

The challenge is that lack of Opera support makes it diffcult to convince project teams to adopt dojo against other great Ajax toolkits such as EXT, which has Opera support.

From a competitive stand point, though Opera has tiny market share, Dijit really needs to figure something out related to Opera in order to stand up against other Ajax toolkits, in particular, for consumer facing web applications.

Comment by Mark Arrington — March 28, 2008


We spent time making sure that our most complicated widget test cases work on Opera. What we mean by “not supporting” is “we can’t guarantee that it’ll work for every use case (particularly a11y), but it’s not known to be broken”, not “it doesn’t work”. Obviously, we take bug reports against Opera, but until it’s a11y story, developer tools, and market share improve we’re probably going to continue to be in “it works, but we’re not making promises” mode.


Comment by slightlyoff — March 28, 2008

Thanks for the clarification. I just tried some dijit demos on Opera 9.26, and they actually work fine, though there are little problems here and there. It seems that dijit team has made great progress already (I was not able to run demos on earlier versions of dijit on Opera). Congrats.

I’d highly recommend this to the Dojo team:
1. Clarify “Opera support” issue along the lines that you described. Giving the users some better understanding of what works and what doesn’t work on Opera. Adding this info to Dojo 1.2 release will be a significant step in enabling customers to check off the “broad browser support” checkbox when evaluating an Ajax toolkit;

2. “ally” doesn’t work on Opera is not a problem – Dijit team can spend their time better by doing something else. Plus, most other Ajax toolkits don’t even bother with “a11y” at all. So don’t let the “a11y” issue become the issue from stopping Dojo to support Opera;

Further, here is a shout to Opera folks: if a popular toolkit like Dojo is having challenges to support you – Dojo supports almost every other browser out there already, maybe Opera should devote some resources to work with Dojo folks to resolve whatever issues in the way? Anybody from Opera might respond here?

Comment by Mark Arrington — March 29, 2008

1.1 is not fully backward compatible with 1.0.0. We developed a framework on top of 1.0.0 and it is mostly broken in 1.1. This has been the biggest pain with Dojo, but we hoped that 1.x is at least backward compatible with 1.0.

– Kidiyoor.

Comment by Rags — March 31, 2008


Did you file a bug on the issue? We’re absolutely serious about the 1.x backwards-compatibility guarantee for Core and Dijit APIs. There was some CSS drift (as documented by the release notes), but APIs in Dijit and Core should not change. If they did, please file a bug (and don’t hesitate to ping us in IRC or send me mail).


Comment by slightlyoff — March 31, 2008

Leave a comment

You must be logged in to post a comment.