Comments on: Rewriting My ‘Guaranteed Callbacks’ Code With jQuery Deferred

By: Andrew McCloud

Andrew McCloud — Wed, 22 Aug 2012 22:59:00 +0000

Awesome! Could you share an example using Marionette.Callbacks vs your Collection.onReset? Would you still need to override Collection.fetch to resolve the callback?

By: j@ubourg

j@ubourg — Wed, 08 Feb 2012 04:34:00 +0000

Not at all! Keep creating domain-centric objects with clear, semantic, method names: that way, application code is readable and explicit.

The whole idea behind $.Deferred and $.Callbacks methods being lexically bound is to push people into creating their own utility classes. Just like Addy Osmani demonstrates in his Demistifying $.Callbacks article by creating a pub/sub object ( http://addyosmani.com/blog/jquery-1-7s-callbacks-feature-demystified/ ).

By: Derick Bailey

Derick Bailey — Wed, 08 Feb 2012 04:02:00 +0000

nice! … kind of make the whole point of my object go away, too. i think i like that :)

By: j@ubourg

j@ubourg — Wed, 08 Feb 2012 03:28:00 +0000

You can make your Callbacks definition even shorter, knowing that Deferred methods are detachable:

Marionette.Callbacks = function() { var defer = $.Deferred(); return { add: defer.done, run: defer.resolveWith };};