Month: June 2011

Disclaimers:

1. I’m still learning my way with jQuery.
2. Code here is pseudocode carved from functioning code (and even then only partly so), so it’s untested in real world.

I was curious as to how jQuery does parameter expansion in event handlers with callbacks. Googling I could only come up with resources that would call their custom functions with parameters given as object literals, like so:

myFunc({
  parameter1 : 12345,
  parameter2 : "foo"
});

, which, when using a callback parameter, would go something like:

myFunc({
  parameter1 : 12345,
  callback : function() {
    return true;
  }
});

Now, there’s nothing wrong with that as such. What I wanted however, was to be able to call my custom functions in the elegant way jQuery does it, without the object literal brackets surrounding the parameters, like so:

myFunc(12345, function() {
    return true;
});

Here’s how I could achieve this:

jQuery.fn.myFunc = function() {
	var options = {
		parameter1 : (arguments[0] || 0),
		callback : (arguments[1] || function() { return false; })
	}

	do_stuff_with_param1(options.parameter1);
        return options.callback();
}

The 403 issue is fixed in a new release of Bitlbee, but those of us relying on third-party servers running older versions need to use a workaround. Comment #3 by wilmer on the tracker ticket says the workaround is to issue:

ac tw2 set base_url http://api.twitter.com/1

However, applying this to settings on my server running Debian Lenny took some effort, so I’m making a note of the working format here:

account set 2/base_url 'http://api.twitter.com/1'

(where ‘2’ is the number of my bitlbee account connected to twitter)

php -r 'echo strip_tags(file_get_contents($argv[1]));' file_to_strip

And as an alias:

alias strip_tags="php -r 'echo strip_tags(file_get_contents(\$argv[1]));'"