Follow Slashdot stories on Twitter

 


Forgot your password?
Close
typodupeerror
×
Image

Dojo: Using the Dojo JavaScript Library 85

Posted by samzenpus from the read-all-about-it dept.
stoolpigeon writes "The number and functionality of web based applications has exploded recently. Many of these applications rely heavily on AJAX to provide a more desktop-like experience for users. As the number of people using JavaScript grew, libraries were developed to assist with commonly encountered issues. Jim Harmon's new book Dojo: Using the Dojo JavaScript Library to Build Ajax Applications aims to introduce readers to one of those libraries, the Dojo Toolkit." Keep reading for the rest of JR's review.
Dojo: Using the Dojo JavaScript Library to Build Ajax Applications
author James E. Harmon
pages 316
publisher Addison-Wesley Professional
rating 7/10
reviewer JR Peck
ISBN 978-0-13-235804-0
summary a complete example rich developer's guide to Dojo
The Dojo Toolkit, is a JavaScript library, created to increase the speed of writing JavaScript applications. It provides developers with widgets, themes, wrappers for asynchronous communication, client side storage and more. It does all this across various browsers and platforms without requiring the user to worry about differences in browsers.

The book follows an interesting pattern. It begins with a five chapter tutorial. The tutorial launches immediately into taking a straight html form and using Dojo widgets to add functionality. All of the code used in the tutorial is available at the book's web site. This tutorial moves quickly, introducing a number of available widgets and giving the reader a nice feel for how Dojo integrates with html markup.

What does not take place in the tutorial is the normal introductory material on just what Dojo is, how it is installed, or what it can do. I'm guessing that this will be a welcome change to those used to quickly brushing past the first chapter, or more, of any programming book. Harmon takes advantage of the fact that Dojo is available via the AOL Content Delivery Network, so the examples will work any javascript capable browser connected to the internet. He does give a quick explanation of what would need to be different to use local files.

All of the introductory material that I'm use to seeing is still in the book but it does not appear until chapter ten. There Harmon covers the motivation to develop Dojo, explains the history of the project, provides a bit of information regarding the dual-licensing of Dojo. (It is available under the BSD and Academic Free Licenses.) This leads into the last seven chapters, that cover the 'deeper' material in the book.

Between the tutorial and chapter ten, there are four chapters of widget documentation with examples and some explanation. Of the three sections this is the longest, though this is in part due to sometimes large sections of white space, as each widget begins on it's own page. The documentation covers each widget and provides a visual representation where applicable. There is some repetition as this section covers widgets that were used in the first section's tutorial.

The third section is entitled "Dojo in Detail." It's the level of detail that marks this book as more of an overview, rather than an in-depth treatment of Dojo. Harmon is true to the title, this book is an extremely pragmatic guide to getting started with Dojo as a means of adding Ajax to applications. It is not however going to take the reader to any great depth into the toolkit. There is plenty here to get started, and enough to hit the ground running, but anyone to get really in-depth coverage of the library will be disappointed.

The person who will get the most out of this book is someone with some knowledge of mark-up and programming but not to an advanced level. The developer with a lot of experience will probably be frustrated with the amount of explanation and repetition of simple material combined with the lack of depth. The reader with no programming experience may struggle, though they could keep up if they are willing to look outside the book for a few resources to get a good grasp of web technologies. They may become extremely frustrated with some of the later chapters where the code examples skip steps and leave the reader to assume what has happened in between what is shown and the output.

That said, this book allows the reader to dive in quickly, get a quick overview and move immediately to making use of the Dojo Toolkit. If one is not concerned with gaining insight on every aspect of the library but would rather just get into it immediately with a little guidance, this may be just right.

With this in mind, it would have been nice if the book had provided less time on documentation and more on examples and ideas for how to best use the capabilities of Dojo. It is nice to have a book that isn't so huge that it is overwhelming and difficult to find anything. But if something had to be given up to keep things compact, I'd have much rather lost things that are easy to find in the on-line documentation and subject to change as the toolkit develops. This keeps the book from being excellent, but it is still a solid introduction and primer.

You can purchase Dojo: Using the Dojo JavaScript Library to Build Ajax Applications from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

*

This discussion has been archived. No new comments can be posted.

Dojo: Using the Dojo JavaScript Library More

Dojo: Using the Dojo JavaScript Library

Comments Filter:

  • book reviews? (Score:1, Offtopic)

    by mattwarden ( 699984 )

    Why isnt this under book reviews?

  • Of course, the real problem comes when dojo destroyers come to challenge your entire office.

    Seriously. We paid good money for that damned sign.

  • How bout something relevant... (Score:3, Informative)

    by RemoWilliams84 ( 1348761 ) on Wednesday October 22, 2008 @12:15PM (#25470779)
    I'll be the first with something relevant here. We use the Dojo tooltips and toaster widgets at work. They come in handy. Easy to use and very customizable. The tooltips have a few flaws but nothing that you can't easily work around.

    • Re: (Score:3, Interesting)

      by Chatterton ( 228704 )

      I use dojo to do a quick prototype of an application. You can start pretty quickly and do some pretty things. But I am blocked by the absence of an official widget to upload files and the fact that the standard input for file upload doesn't work with dojo. None of the sample code I found on the internet to do this seems to work well :(

      But except that big problem and some other minor ones, Dojo look very good.

      • Re: (Score:3, Interesting)

        by kevin_conaway ( 585204 )

        We use ExtJS and were able to do file uploads quite easily using a combination of their Ajax form submit and Commons FileUpload.

        If Dojo has a control to submit a form asynchronously, you should be able to pull this off. Feel free to contact me for more details

        • ExtJS uses a clever hack to allow async file upload... a hidden iFrame. So it's not really an async upload, but looks like one.

          I guess one could implement the same trick using Dojo with a little effort.

    • Re:How bout something relevant... (Score:4, Interesting)

      by eddy_crim ( 216272 ) on Wednesday October 22, 2008 @12:45PM (#25471209) Homepage

      here here! i agree, as a coder ive not tried the other javascript front end frameworks like prototype and jquery but i have tried the server-side ajax frameworks like GWT and i don't like the way that i am detached from the JS that is actuall being generated.

      Dojo makes writing JS very easy but the extensibility of it make it very powerful.

      The other thing worth noting that may or may not be a good thing is the way Dojo is backed by IBM and used extensively in their products. Hopefully this means dojo is here to stay.

      Finally if you use dojo on the client with a JSON-RPC-Adapter on the server you can move your MVC view and controller onto the client and just keep a model and service layer back on the server. This opens up some interesting possibilities.

      • Re:How bout something relevant... (Score:5, Interesting)

        by rufus t firefly ( 35399 ) on Wednesday October 22, 2008 @01:02PM (#25471531) Homepage

        I also had written a UI in dojo, starting with 0.3.x and porting forward to 0.4.x. However, their API jump to 0.9.x and then 1.x made any further porting nearly impossible.

        It was riddled with issues that had to be worked around by messing with undocumented properties and all sorts of other nonsense. (Check out the 0.4.x Wizard code for some examples.) Patches to fix problems weren't accepted, and the developers weren't very responsive to any criticism, saying that it would be fixed in the API incompatible next releases.

        I moved to GWT, and haven't regretted the move at all. Performance wise, the precompilation has made it much faster, and the code is much more maintainable in java than in javascript. There's something nice about programmatically creating a reusable UI in a sane typed programming language instead of hacking together something in Javscript.

        • Re:How bout something relevant... (Score:5, Interesting)

          by djbckr ( 673156 ) on Wednesday October 22, 2008 @01:33PM (#25472029)
          I have to say a word of agreement here; GWT blows the pants off of anything else I can find (I was trying to come up with a better picture, but I guess that'll do).
          Nicely documented, pretty easy to use, high performance, relatively small code footprint (for what it does).
          Newer versions have properly deprecated methods that makes it easy to move from version-to-version. I shudder to think about using *anything* else for this purpose. Dojo is nice and all (probably the nicest of its kind), but it's nothing compared to GWT.

          • Re: (Score:3, Interesting)

            by rufus t firefly ( 35399 )

            Plus, if you're really stuck on the way Dojo looks and feels, you can just use Tatami [google.com], which allows you to use the Dojo toolkit from inside GWT. You get the extra Dojo library bloat, but it may help someone.

            • Tje dojo library bloat is not that big. Dojo core is compressed around 50kbyte (compressed means just junk stripped, you get more if you go for real compression but that would cost initialization time)
              The full dijit widget set is 200 kbyte, not that much considering it covers around 30-40 components!
              And if you need just a subset you can roll your own custom builds and uses dynamic code loading if you miss something.
              Also have in mind that if you roll your own custom build the browser cache can trigger so all

              • Tje dojo library bloat is not that big. Dojo core is compressed around 50kbyte (compressed means just junk stripped, you get more if you go for real compression but that would cost initialization time) The full dijit widget set is 200 kbyte, not that much considering it covers around 30-40 components! And if you need just a subset you can roll your own custom builds and uses dynamic code loading if you miss something. Also have in mind that if you roll your own custom build the browser cache can trigger so all this is loaded only once!

                The point is that a lot of it is duplication, since a great deal of that functionality is already covered by GWT, and all of the dojo "boilerplate" is reproduced. For example, none of the RPC stuff is used, since GWT favors its own implementation over dojo.io.bind() or its descendants. Pure GWT is faster than GWT + Dojo, but I'm not sure by exactly how much.

                • Problem starts if you do not want to use java or GWT... ;-)

                  • Problem starts if you do not want to use java or GWT... ;-)

                    It's definitely a different approach to creating web-based applications. Far more programmatic and structured than straight up Javascript toolkits. Looking at it purely with regard to maintainability and forward porting, GWT leaves just about everything else in the dust. The downside is you have to like to code everything in Java. In the end, it's all about personal preference.

          • I have to say a word of agreement here; GWT blows the pants off of anything else I can find

            Forgive my ignorance here, but why is Google using jQuery in their Google Code site if they could have used GWT?

            • Re: (Score:3, Informative)

              by Nathanbp ( 599369 )

              I have to say a word of agreement here; GWT blows the pants off of anything else I can find

              Forgive my ignorance here, but why is Google using jQuery in their Google Code site if they could have used GWT?

              Google has said that many of their older websites use JavaScript of some sort instead of GWT because GWT had not yet been created when they started work on them, and they feel it would be too much work to move them to GWT. There are some examples of newer Google sites that use GWT that you can look up.

          • Well GWT is bound to java and generates the code on the fly, for many this is a big reason not to touch it. I never used it adittably since my work is in another domain. But talking to a guy who extensively used it basically just resulted in a confirmation of what I suspected. He said, GWT is excellent as long as you use just what GWT provides the problems begin once you have to dig into the core of the generated javascript code and if you try to alter that one. This is machine generated code and not very

        • I had a similar problem. For about a year you had to choose between Dojo 0.4 - 0.6 which had some very poor documentation but which were obsoleted by massive breaking API changes coming in 1.0. But 1.0 had no documentation and was nearly impossible to decipher and use. So there was simply no good version of dojo to use at all. Add to that the fact that the default dojo theme just looked amateur and ugly - it was a non-starter for us.

          We moved to YUI which is like entering a different universe to dojo -

  • Not sure I wanna use something called Dojo with the threat of Shodan still around... ;)
  • Anyone else read that as "DOJ: Using the DOJ JavaScript Library"?

    • Yeah the DOJ JavaScript Library continually sends AJAX requests to the FBI and the NSA in the background while your page is open.

  • since, if you got any mojo, you can get some girls (ask Austin Powers if you don't believe me). if you got some dojo, you cannot get anything?!
  • I'd like to take this opportunity to start a holy war between Dojo and Scriptaculous/Prototype. Aw hell, why not throw in Ext too.
    Wait, I'll get some popcorn.. OK - Go!
    • Perhaps I'm wrong, but it seems to me there isn't much of a holy war going on in the JavaScript framework world. At least not nearly to the same extent as Linux vs. Win vs. Mac, Emacs vs. Vi, Python vs. Perl. If I were to hazard a guess, I'd say these other holy wars exist where tools in the same domain space are are developed with radically different philosophies, whereas most/all JavaScript frameworks have more or less the same philosophy - it's just how far they take it and exactly what methodology the

  • Relevance? (Score:1, Insightful)

    by Anonymous Coward
    Is Dojo even relevant anymore now that Microsoft has embraced jQuery?

  • I recently bought 2 other related books (Score:4, Interesting)

    by MarkWatson ( 189759 ) on Wednesday October 22, 2008 @12:51PM (#25471315) Homepage

    I bought "Mastering Dojo" and although I have not finished it yet, I like it. I got into using Dojo a few years ago when I was experimenting with Common Lisp back end code with a REST architectural style - and a rich client Dojo web interface. Dojo is very cool. I have also used Dojo in a Rails web app and tried it with a JSP based web app (just a test, not a real project).

    The other related book I bought recently is "Javascript, The Good Parts" that has made me appreciate the language more.

  • I was recently looking for a javascript library to help solve cross browser issues with accessing ASP.NET based web services. The main interest was DOM traversal, simple GET/POST/SOAP requests, and XML parsing. I looked at a bunch of different frameworks, but finally settled on jQuery [jquery.com]. It had everything that I needed in a small package with excellent support for plugins and add-ons. We ended up using an XML to JSON converter plugin since parsing arbitrary XML can be a pain to do in a cross browser world. Ke

    • Re: (Score:2)

      by Sancho ( 17056 ) *

      That's a ditto moment. It sounds exactly like where I was about 2 months ago.

      I consider a framework essential for DOM traversal these days. If you want to run in multiple browsers, you'll either be writing one yourself or using one that's pre-written. There are a lot of really good frameworks out there, but I picked jQuery for the exact same reasons you did--it's no-nonsense, low-cruft, and highly extensible. Highly recommended.

  • Being a practical type, I must confess that the learning curve with Dojo has been rather steep; having said that, once you get over the first major hump - it's literally all downhill from there. But, I'm not defending Dojo. Instead, I'm complimenting the book.

    This book appears to solve the learning curve problem by starting with a practical tutorial and then going into guts.

    IMO, the biggest problem with Dojo's userbase growth has been that Dojo seems to be both large and small at the same exact time, maki

    • I've completely embraced Dojo as a reliable way to quickly produce backend systems with it - and - more recently - front ends.

      Producing a 'backend' system with a JS library must be a neat trick, since JS is client side. However, I totally agree with you about the learning curve. I couldn't make heads-or-tails of the code.

      • Apparently you can't make heads-or-tails of terminology either. You're thinking strict code execution, while I'm thinking conceptual division. In this case, I thought it was pretty obvious that I was referring to a CMS; I'll be sure to spell things out clearly next time.

        And- just for the record, neat trick indeed. JavaScript can be and is executed server-side as well as client-side. The Dojo release build system works like that. See http://www.mozilla.org/rhino/ [mozilla.org]

      • Re: (Score:2)

        by Sancho ( 17056 ) *

        JS is client side

        http://en.wikipedia.org/wiki/Server-side_JavaScript [wikipedia.org]

        Just 'cause it's fun pointing out the mistakes of others, you know?

    • I fully agree here, the learning curve is really steep because dojo is so extensive. It is basically to javascript what the java runtime is to java. It is a complete coverage of the entire domain of what you need in third party libs.

      Also I think the learning curve used to be much steeper in the past, thanks to three excellent books (I prefer the one from pragmatic programmers though) and to the improved manuals online, which unfortunately really have a load of black holes in there!

      As for the build size, I d

  • Dojo is complex for complexity's sake (Score:3, Interesting)

    by HighOrbit ( 631451 ) on Wednesday October 22, 2008 @02:09PM (#25472529)
    Dojo has some cool and impressive examples (the fish eye menu is kinda neat). However,everytime I've looked at Dojo and tried to figure out how to use it, I've had to walk away shaking my head. It is usually easier to implement something myself instead of trying to figure out the all the undocumented spaghetti code and "helper" files and abstractions in Dojo. Dojo seems to have taken all the complexity jokes about java and ported them to javascript. Maybe they have gotten better in the last year or so, but the last time I looked, most of it was undocumented and the code as non-trivial to decypher.

    For people who want to use some simple, yet powerful JS/Ajax/CSS, I'v been recommending that they check out BrainJar [brainjar.com]. Brainjar has some pretty neat stuff that is much easier to figure out, although its random stuff and not a comprehensive toolkit. But brainjar will give you some neat ideas of the things you can to with JS and CSS. Check out the windowing demo [brainjar.com] and as a plus it won't screw with your mind like Dojo.

    • Re: (Score:2)

      by LDoggg_ ( 659725 )
      Couldn't disagree more.

      Don't think of dojo as just a collection of scripts for widgets or animations like in scriptaculous.

      Dojo is a HUGE library that gives you the ability to pick bits and pieces where they might be helpful and in a way that hides some of the uglier browser-specific things that you don't want to deal with.

      For example, using connect() to add an onclick to a DOM element will put some sanity to attributes of the mousevent object that gets passed.
      Sure I could write a bunch of code to get

  • How does Dojo compare to Yahoo UI (YUI)?

    • Re: (Score:2, Interesting)

      by zuperduperman ( 1206922 )

      YUI is extremely well documented, has a great active forum and has (quite literally) hundreds of examples - dozens for each control / feature offered. They also offer a very nice, consistent theme that goes right across the whole library and integrates with every component.

      I haven't looked at dojo in a while but when I did, the documentation was *horrible*. You really had to go through a lot of pain to "grok" how it worked under the hood before you would be productive (this may have gotten better). My i

      • Btw. if you need examples and documentation on dojo there probably is no better site than

        dojocampus.org

        I am way happier with this site than with the original dojo documentation!

    • YUI has mainly the objective to cover widgets, it is comparable to the Dojo dijit widget set!
      The code itself and how the class files are done how the widgets are initialized are pretty similar. YUI however has the better documentation.

      While dojos has improved it is necessary to get one of the tree dojo books to really grasp everything correctly.

      In the end I still would choose dojo over YUI due to the fact that dojo is so much more. Around 90% of my work in javascript definitely I just use the dojo core 10%

  • Ok something that must be said here that seems to have been overlooked. Dojo is actually unusable - and yes I mean that perfectly seriously - unless you have somebody around who already has experience with it. It is completely undocumented - the documentation that exists is sketchy and often wrong. No just listing the class method parameters automagically is not sufficient. My workplace has just ditched Dojo and is investigating JQuery - with some success thus far - purely on this basis: Dojo is unmaint

    • For a better documentation look here

      http://dojocampus.org/ [dojocampus.org]

      Also buy one of the books. The documentation has becomed better however on the original site.
      I really can recommend the pragmatic programmers book however to get a full grasp!

  • If JSONP isn't an option for you, and you need to make use of a REST endpoint on another domain (or even subdomain), see if you can get the service provider to add Dojo's XIP [dojotoolkit.org] server files to their server.

  • 50% ? (Score:2, Interesting)

    by Tablizer ( 95088 )

    I browsed around the web for Dojo examples, and only about half worked. Not a good sign. Some outright crashed, others half-worked with things like text in the wrong place or only deletion working but not insertion. Reminds me of Java applets a decade ago.

Slashdot Top Deals

A committee takes root and grows, it flowers, wilts and dies, scattering the seed from which other committees will bloom. -- Parkinson

Close