$.extend( defaults, $.fn.pluginName.defaults, options )


           return this.each(function(){
                //do something more
                $.myClassName.calcSomething(param){

           }
        }
    }
    $.fn.myMethod = $.myClassName.main;
})(jQuery);

I’d like to know your opinion about that OO pattern in jQuery plugins.
Thanks for your article!

All javascript in the project I would like to transform in a jQuery
plugin. But to achieve this I need to separate in categories in
libraries for this site Im working

So, I wanna to make this:

$(”seletor”).project.ajax.remote();

$(”seletor”).helpers.options();

But when Im creating a plugin like this:

$.fn.project.ajax.remote = function() {
//code

}

Its not working…

Using extend I reach it, but extending methods of jQuery objects I
cant do that. I need this because I create a ajax library just for the
site and a lot of thing, so we need this pattern…

How I can accomplish this????

Could you update it to explain how to implement callbacks? Some concise background info about callbacks would be great as well.

Thank you so so much for all you do for the jquery community!

Alexandre

I’m most definitely not suggesting anyone using namespacing to do this:

$('selector').namespace.method().namespace.method().namespace.method()

As was mentioned, this article focuses on a single-plugin script and the suggestion is to use a single namespace for a single plugin. If your script has multiple plugins then you certainly need multiple $.fn extension points (for example, $.fn.doSomething() and $.fn.undoSomething()).

I believe that using the plugin function for default settings and for exposing public functions is a better implementation than extending the jQuery object itself. I suppose it’s a matter of taste, but I prefer to have the entire plugin implementation packaged in the same namespace.


// Private Variables and Methods
var namespace = {
};
// Public Variables and Methods
$.namespace {
}


Sorry for the confusion. Argh! I hate not thinking straight.


(function($) {

})(jQuery);


One final note. Although this isn’t standard practice, you can greatly clarify your code by using a private object as opposed to using free-floating private functions and variable. The the private section would therefore look like this:


  // Private Variables and Functions
  var private = {
    privateVariable: {},
    function privateFunction() {
      // Do Something Privately
    }
  };


This way when you access private variables and methods it will be apparent in your code:


private.privateVariable = 'foo';
private.privateMethod('bar');