Yes, ready is an event handler (a great one, since it fires when the DOM is ready, rather than waiting for images to load).

However, when using it, you want to pass a reference to the function, not execute the function itself.

Rather than:

jQuery(document).ready(MyFunction());

Do:

jQuery(document).ready(MyFunction);

Also, one of the nicest things jQuery does, is if you pass it a function straight away, that is a shortcut to the document ready event.

jQuery(document).ready(MyFunction);

Is exactly the same as:

jQuery(MyFunction);

Call a function on page load:
function MyFunction()
{
// do lots of my stuff here
}
jQuery(document).ready(MyFunction());

OR
jQuery(document).ready(function(){// do little stuff here});

jQuery.fn.myPlugin = function() {
 
    // Clean up after yourself!
 
    jQuery.myPlugin = {
        cleanUp: function() {
 
            // Remove all click handlers binded
            // as a result of the plugin:
            jQuery('*').unbind('click.myPlugin');
 
            // ALternatively, remove ALL events:
            jQuery('*').unbind('.myPlugin');
 
        }
    };
 
    return this.bind('click.myPlugin', function() {
        // Do something...
    });
};
 
// Note, you can also namespace data:
// E.g. $(elem).data('whatever.myPlugin',value);

1. Why put the cleanUp function inside jQuery.myPlugin = {…}, couldn’t you just use var cleanUp = function() {…} ?

2. If you needed to declare some variables for you plugin’s state, where would you put them: in the jQuery.fn.myPlugin = function() {…} block; or the jQuery.myPlugin = {…} block?

My apologies if these are stupid questions. 🙂

I think there is a little type here, the second ‘i’ should be replaced by a ‘j’

// List bound events:
console.dir( jQuery('#elem').data('events') );
 
// Log ALL handlers for ALL events:
jQuery.each($('#elem').data('events'), function(i, event){
    jQuery.each(event, function(i, handler){
        console.log( handler.toString() );
    });
});
 
// You can see the actual functions which will occur
// on certain events; great for debugging!

One minor remark: you say the the event object is normalized across all browsers. This is true, but I do like to point out that the event triggers are not normalized. For example, listening to keypresses works differently in different browsers, the same goes for the submit event, which is different in Opera.

Keep ‘hem coming and Congrats !