Comments on: Jammastergoat – dojo.hitch

By: Learning Dojo | SitePen Blog

Learning Dojo | SitePen Blog — Fri, 05 Mar 2010 11:46:39 +0000

[...] (article) Jammastergoat: dojo.hitch [...]

By: DojoCampus » Blog Archive » Dojo and Air, a fancy file uploader

DojoCampus » Blog Archive » Dojo and Air, a fancy file uploader — Wed, 02 Apr 2008 09:02:49 +0000

[...] dojo.hitch method which takes all the heavy load of your shoulders. I recommend reading the cookie by Peter Higgins about dojo.hitch Note the third parameter passed to the dojo.hitch method. All parameters after the second one just [...]

By: DojoCampus » Blog Archive » Demystifying dojo.data

DojoCampus » Blog Archive » Demystifying dojo.data — Tue, 25 Mar 2008 18:14:54 +0000

[...] absolutely love the way that it simplifies my life. While it’s not quite as “magic” as dojo.hitch(), things “just work” when I use it. Many of the dijit widgets support being tied to data stores. The [...]

By: occident.us » Blog Archive » Dojo Cookies Make Curry

occident.us » Blog Archive » Dojo Cookies Make Curry — Fri, 21 Mar 2008 16:46:00 +0000

[...] set of tutorials over at dojocampus.org cutely dubbed “cookies.” Reading through the article Alex highlights on dojo.hitch I even learned something new. Turns out dojo.hitch isn’t just a nice tool for [...]

By: Continuing Intermittent Incoherency

Continuing Intermittent Incoherency — Thu, 20 Mar 2008 08:20:46 +0000

[...] Higgins has an excellent article up that covers dojo.hitch(), and in general the Dojo Cookies series over at dojocampus.org is rocking [...]

By: rcoup

rcoup — Sun, 16 Mar 2008 03:10:36 +0000

dojo.hitch() is also fantastic for interacting with third party APIs. Since nobody wants nasty global-namespaced functions, we can use hitch to tidy it up. Here’s a simple Google Maps example, since the GEvent functions don’t support any scoping.

dojo.provide(”my.maps”);

dojo.mixin(my.maps, {
savedPoint: null,

onMapClick: function(overlay, point) {
// since we used dojo.hitch() this is called with this==my.maps, which is what we want
this.updateSavedPoint(point);
},
updateSavedPoint: function(point) {
this.savedPoint = point;
}
});

// connect our GMaps event listener, and use the my.maps scope for our handler
var eh = GEvent.addListener(gmap, “click”, dojo.hitch(my.maps, “onMapClick”));

By: pottedmeat

pottedmeat — Sat, 15 Mar 2008 21:45:07 +0000

Correct!

By: toonetown

toonetown — Sat, 15 Mar 2008 19:04:17 +0000

Ok – so (as a reference for me in the future), the following code:

var foo = {attr:”an attribute”, debug: function(v, v2){console.log(this.attr + ” – ” + v + ” – ” + v2);}};
var val = “Me”;

dojo.hitch(foo, “debug”, val)(”Him”);

Will produce “an attribute – Me – Him”

Great!

By: pottedmeat

pottedmeat — Sat, 15 Mar 2008 18:57:46 +0000

@toonetown, Hitch puts the hitched parameters at the beginning, and the new arguments at the end.

In the example above, since you’re only using the first argument, it would log “Me”. But in the second argument, you’d have your passed value of “Him”.

By: toonetown

toonetown — Sat, 15 Mar 2008 18:23:15 +0000

One question I’ve always had about hitch is a bit more explaination on the “positional” arguments…for example:

var foo = {attr:”an attribute”, debug: function(v){console.log(this.attr + ” – ” + v);}};
var val = “Me”;

dojo.hitch(foo, “debug”, val)(”Him”);

What will be produced? “an attribute – Me” or “an attribute – Him” ?

Does that make sense? Does positional apply to when it’s called or when it’s defined?