Patterns In Jquery Plugin writing

Well, there is nothing new to write about how to write a jquery plugin,  there are a lots of articles available on the web including jquery site and those are more than enough to learn about writing a jquery plugin. So I’m not going to teach anything new today but instead, I’m trying to discuss about various ways and difference of writing a jquery plugin that developers use, because everyone doesn’t use the same pattern and sometimes it creates confusions.



What is the difference ?

Ultimately nothing. Both patterns are correct. The first pattern is the simple way of adding an attribute to an object. In javascript, you can add an attribute to a custom object like this. Here the fn is an object and myplugin is a new attribute/method and the function right side of the = is an anonymous function assigned to this method. Now lets see an example how to do it in javascript.

Now, if we want to add a new attribute to our myObj then we could do that in the following way.

Here, in our first pattern we did the same thing. The fn is an object (an alias of prototype) and we’ve just added a new attribute to it and the anonymous function is it’s value, so, you can say that, we’ve extended it or added a new method to fn object and named it myPlugin. Now, if we write $(‘some_element’).myPlugin(), the anonymous function at the right side of ‘=’ in our plugin, will be executed. In the second pattern, same thing happened but using jquery’s extend method, instead.  In this case, we’ve extended the fn object and added two new items to it using javascript object literal. The benefits of using this pattern is that, we can add multiple items/plugins in the same time as we did here, x and y become now two new plugins and these belongs to fn object. That’s it. Hope I could make it clear.


 To maintain the chainability the ‘return’ keyword has to be used with ‘this’ keyword and use jquery’s ‘each’ method inside your plugin to apply some action to a collection of matched elements. Lets see.

If we call $(‘div’).myPlugin().css(‘color’,’black’), all the div will be effected by our plugin because we wrote the function inside each (plugin will loop all divs) and after the plugin’s operation .css() will change the text color of all divs because we’ve returned the object using ‘return’ keyword, if we didn’t then we had to call the .css method seperately like this

Passing arguments to the plugin

Now we can call our plugin with options/parameters like this

In the plugin above we’ve created an object(settings) and gave some default options ‘background_color’:’gray’ and ‘foreground_color’:’black’ and merged it with user’s options, using $.extend( settings, options ), so if we call the plugin without any parameter/option, by default, values of the ‘defaults’ object will be applied, that means, background-color will be gray and color will be black. If we want to change only background color then we can call it with one argument as, $(‘div’).myPlugin({‘background_color’:’white’}). That’s it.

Latest Blog


PHP – 8.0 Match Expression

In PHP 8.0 there is a new feature or I should say a new language construct (keyword) going to be introduced,  which has been implemented depending […]


New Union Type in PHP – 8

A new RFC has been finished voting and accepted for PHP – 8. That is “Union Types”, which is an extension of PHP’s type system. […]