views:

1982

answers:

6

The Dojo toolkit looks like it is very useful, but the docs feel very incomplete and buggy. Can anyone suggest a book or other resource to help a javascript novice really learn to use Dojo?

+3  A: 
Yadyn
They're up to 1.1 now and have a printed book? I guess I'm <em>really</em> behind the times! Man... unfortunately, it's too late in our current project to re-do everything with the new version or else I would.
Yadyn
+3  A: 

I have Dojo: The Definitive Guide by Russell and Dojo: Using the Dojo JavaScript Library to Build Ajax Applications by Harmon. I needed both books but once I had gone through the Harmon book I have not referred to it much, if at all. The Russell book, however, I have kept by my side and refer to it frequently. Harmon's book gave me an overall understanding and a quick way to use the toolkit. Russell's book takes you through the toolkit from zero knowledge of the toolkit.

Russell's *Definituve Guide* is the best choice when looking for a Dojo book.
Török Gábor
+16  A: 

There are a number of useful resources for Dojo out there...

Online documentation:

  • Dojo Book: The online reference guide for Dojo is pretty comprehensive, and is generally updated. During 2008, the docs will move to a more editable site at DojoCampus.

  • API Reference: Want to know the attributes for customising a ContentPane? Or the parameter order for dojo.connect()? Hit the Dojo API Reference and look it all up. Commenting is available too so leave your experiences there.

  • Dojo Campus is the home of learning resources for Dojo. It includes a Feature Explorer, the new Documentation, podcasts, tutorials, and cookies (helpful bite-size tips for Dojo)

  • Demos & Tests are a great way to see how the different components can be used, combined, and customised. The online archive has links to test pages, and they're also available in the downloads and checkouts under <dojo/dijit/dojox>/<module>/tests/

  • Others:

    • The Dojo Toolbox is a desktop app which provides an offline version of the API reference and a number of other tools and links.
    • The Key Links page on the Dojo website links to lots of tutorials around the web.

Blogs:

Books:

rcoup
+1  A: 

This afternoon I was running into a Dojo problem that just wouldn't budge. I boiled it down to a case that was simple enough to ask for help on the #dojo channel on the FreeNode IRC network. A Dojo developer took a look at my issue very quickly, determined that it was due to a bug in a recently-created interface, and brought the developer who had written that module into the conversation. There was a bug fix in the trunk within half an hour, and everything worked fine afterward.

If you just can't get anywhere with the examples or the documentation, I'd recommend joining #dojo.

tuxedo
+1  A: 

I recently bought Mastering Dojo by Rawld Gill, Craig Riecke, and Alex Russell (Publisher: The Pragmatic Programmers). It's without a doubt the best Dojo learning and reference out there.

+2  A: 

I have Mastering Dojo by Gill, Riecke and Russell, but I'm looking for something more information dense and less erroneous. For example, here's an error I noticed:

"In good object-oriented frameworks, some built-in methods are meant for the programmer to call, and some are meant for the programmer to override. A good example of the latter is compare in Java. This method is defined at the root of the class tree (Object) and overridden in most of the built-in classes." (p. 329)

I think they meant equals, not compare. See http://java.sun.com/j2se/1.3/docs/api/java/lang/Object.html#equals(java.lang.Object)

Also, in the section explaining the widget lifecycle, Mastering Dojo does not mention the methods destroyRecursive and uninitialize. By contrast Dojo: The Definitive Guide does mention those methods, and explains all the lifecycle methods in more detail than Mastering Dojo does.

Another thing I found disappointing about Mastering Dojo is that it's very "Pro-Dojo". It takes the viewpoint of a fervent Dojo advocate, rather than that of an even handed teacher. In and of itself this is not bad, but when one of the book's authors is a major Dojo code contributor, it makes me lose confidence in the book's objectivity. I mean, opening chapter one with this sentence strikes me as a bit arrogant/pretentious/biased/blind:

There's a new king in town.

Chinnery
+1 for the critism on *Mastering Dojo*.
Török Gábor