Home & blog  /  2012  /  Apr  /  view post  /

Non-AJAX use for jQuery's deferred objects

posted: 09 Apr '12 19:41 tags: jQuery, deferred, AJAX

I'm currently writing another article for .NET magazine on the newer features of jQuery, for developers who perhaps got comfy with jQuery 1.3 or 1.4 and didn't keep up.

One of the obvious candidates for the article is deferred objects, which landed in jQuery 1.5 as part of the overhaul to jQuery's AJAX module.

AJAX is the obvious use-case for deferred objects, and it's simple to come up with examples for that. But I was also trying to show a non-AJAX example.

I'm talking about cases where you would manually make your own deferred objects and apply subjective logic as to whether, when and how it is resolved or rejected. So other forms of asynchronous code execution.

This is quite a different beast from using deferreds with AJAX, since, at least usually, jQuery's AJAX methods automatically create, return and resolve/reject deferred objects for you. In other words, you can use deferreds in an AJAX context without ever going near methods like $.Deferred(), $.when() or deferred.resolve().

Click the vowels

I eventually came up with a slightly contrived game for children where they have to identify and click the vowels in a sequence of words. Each vowel would constitute a deferred object. When clicked, the vowel fades out and its deferred object is set to resolved. When all deferreds are resolved (i.e. all vowels have been clicked), we give feedback and move on. I think it's quite a nice pattern.

You can see a demo of the game here.

First, some simple HTML:

1<h1>Click all the vowel letters</h1>

2<div id='words'></div>

And CSS:

1#words { height: 100px; }

2#words div { display: inline-block; width: 100px; height: 100%; text-align: center; font-size: 50px; line-height: 90px; margin-right: 10px; background: #e50; color: #fff; cursor: default; }

3#words div:last-child { margin: 0; }

Now on to the JS (all inside a DRH, of course, as we're dealing with the DOM).

1//prep

2var

3words = ['square', 'hosepipe', 'canine', 'flower'],

4container = $('#words'),

5vowels = 'aeiou',

6next_word_index = 0;

All rather self-explanatory. Now for the bulk of the code:

1function build_word(word) {

2    

3     //increment the next-word index

4     next_word_index++;

5    

6     //remove the previous word, if any

7     container.empty();

8    

9     //an array to store our deferreds (one for each vowel)

10     var deferreds = [];

11    

12     //loop over the word's letters

13     for (var i=0, len=word.length; i<len; i++) {

14        

15         var

16         letter = word.substr(i, 1),

17         isVowel = vowels.indexOf(letter) != -1,

18         letter_div = $('<div />', {text: letter}).appendTo(container);

19            

20         //if this letter is a vowel...

21         if (isVowel) {

22            

23             //set up a deferred object for it and log it in the array

24             var deferred = $.Deferred();

25             deferreds.push(deferred);

26            

27             //on click, fade it out then resolve its deferred

28             letter_div.click({deferred: deferred}, function(evt) {

29                 $(this).animate({opacity: .2}, evt.data.deferred.resolve).unbind('click');

30             });

31         }

32     }

33    

34     //when all deferreds are resolved, do feedback and move on

35     $.when.apply(null, deferreds).done(function() {

36         var msg = 'Well done - you got all the vowels! ';

37         if (words[next_word_index]) {

38             alert(msg+"Let's try the next word...");

39             build_word(words[next_word_index]);

40         } else

41             alert(msg+"That's the end of the game!");

42     });

43}

44    

45//on page entry, do the first word

46build_word(words[next_word_index]);

A few points

Hopefully the comments make it possible to follow what's going on there, but here's some points of particular note.

Firstly, I invoke $.when not directly but via the native apply(). This is because $.when() does not presently allow you to pass multiple objects as an array, which is necessary for my example. apply(), as you may know, allows you to stipulate arguments to a function as an array, so problem solved.

(If you're new to $.when(), I'll be covering that in a separate post, as it has a lot to offer your patterns.)

Secondly, in a production environment it would be prudent to expose not the deferreds themselves but their inherant promise objects (via the promise() method) instead. This allows environmental code to bind callbacks to them but not interfere with their state or progress. See the jQuery API page on promise objects for more detail.

Summary

I reiterate that this is a slightly contrived example, to highlight the use of deferreds independently of AJAX, but I think it's quite a nice pattern.

Of course, the same effect could be achieved several other ways without deferreds; one could continually check, in the fadeout callback, whether there were any vowels still remaining at full opacity. If no, the user has clicked all the vowels. That would require a more complex fadeout callback, but it would of course work.

post new comment

Comments (5)

Samson, at 11/04/'12 14:32, said:
Nice! I had to read about this bad boy a couple times before I wrapped my head around it. Another implementation would be say:
var myVar;
function setMyVar(){
      var dfd = $.Deffered();
      setTimeout(function(){
           myVar = 10;
           dfd.resolve();
      }, 1000)
     return dfd.promise();
}

setMyVar().done(function(){  console.log('The value of myVar is:  ' + myVar )  })

The beauty of this is you can test for failure i.e dfd.reject() instead of resolve(), and chain callbacks if you want to execute different code for different outcomes. So you could chain a .fail() method to the .done() method. I think there is even a .then() method which amalgamates the the done and fail methods. 

btw I love the way you explain some of the rather difficult JavaScript concepts. But I digress!
Mitya, at 11/04/'12 14:39, said:
Thanks, Samson. Yes, deferreds are handy for any asynchronous code you have. Like everything with jQuery, you don't HAVE to use them - you can get the same things done without them - but they can be highly complementary to your coding patterns with regards to splitting out your functions and methods.
Ross Hadden, at 11/04/'12 17:40, said:
Several days ago I arrived in a situation where I had to make an arbitrary number of AJAX calls, and wait for all of them to return before executing some code.

My solution was doing what you did (though I used $.when.apply(window, deferreds), and I like your 'null' better because it is true), and I was quite proud of it.  I actually can't even think of a non-hacky way to do it without using deferreds.
Mitya, at 15/04/'12 11:30, said:
Hi Ross. The context argument you pass to apply() is academic in this case becuase jQuery.when() has no dealings with 'this'. This is why I pass null. I could have passed anything, though, with the same result.

As for achieving the same thing without deferreds, the obvious thing to do (which is presumably what jQuery does internally to power the deferreds mechanism) would be to create an array and, in it, have an entry for each 'event', each with a flag to track whether it had comleted yet.

When each event completes, its flag is set to true. On each event callback, we would check to see if all flags were set to true - i.e. all events had completed - and that's our cue to move on.
ecommerce reviews, at 12/05/'12 13:06, said:
Nice post! Really a nice discussion is done by you . I agree everything you say but i have some other opinion also. I know that the .NET technology is used to develop the both type of the application like web application, desktop application etc.  In this blog post ,it gives the many ideas and inspiration about to use the .NET application for developing the project .
Thanks for sharing the information.