10 tips for writing a good jquery plugin

After developing a lot of jquery plug-ins, I slowly developed a set of jquery plug-ins to develop a comparative standard of the structure and mode. So I can copy & paste most of the code structure, just focus on the most important logic code on the line. Using the same design pattern and architecture also makes it easier to fix bugs or develop two of times. A validated architecture ensures that my plugins are not a big problem, whether the plugin is simple or complex. I am here to share 10 lessons I have summed up.

1. Put all your code in theinside the closures .

This is the most I have used. But sometimes the method outside the closure cannot be called.
However, your plugin code is only for your own plug-in service, so there is no problem, you can put all the code in the closure.
The method may be placed inside the prototype method.

(function ($)  {//code here}) (JQuery);

2. Provide default options for plugins

Your plugin should have some options that are available for developers to set up, so providing a restore default option is necessary. You can set these options by using the Extend feature of jquery:

var defaultsettings = {      mode            : ' Pencil ', linewidthmin    : ' 0 ', Linewidthmax    : ' Ten ', LineWidth       : ' 2 '}; Settings = $.extend ({}, DefaultSettings, Settings | | {});

3. Use to return an element

A good feature of javascript/jquery is the ability to cascade methods, so we should not break this feature and always return an element in the method. I follow this rule in every jquery plugin I have.

$.fn.wpaint = function (settings)  {return This.each (function ()  {var Elem = $ (this);//run some code here}}

4. One-time code outside the main loop

This one is important, but it is often overlooked. To put it simply, if you have a piece of code that is a bunch of default values, you just have to instantiate it once, instead of instantiating it every time you call your plug-in function, you should put this code outside the plug-in method. This allows your plug-in to run more efficiently and save memory.

var defaultsettings = {mode            : ' Pencil ', linewidthmin    : ' 0 ', Linewidthmax    : ' Ten ', LineWidth       : ' 2 '}; Settings = $.extend ({}, DefaultSettings, Settings | | {}); $.fn.wpaint = function (settings)  {return This.each (function ()  {var Elem = $ (this);//run some code here}}

You can notice that the "DefaultSettings" in the code above is completely outside the plugin method, since the code is inside the closure, we don't have to worry about these variables being rewritten.

5. Why to set Class prototyping

As your code of blood and Flesh, methods and functions should be placed within the prototype function. There are two reasons:

• It can save a lot of memory because you can create these methods without repeating them.
• Referencing an out-of-the-box method to create a new one is much faster.

Simply put, prototype is an extension of an object that provides methods to it without instantiating them in each object. This also makes your code more organized and efficient. Once you get used to this type of development, you'll find that it saves you a lot of time in your future projects.

6. How to set the Class prototyping

There are two parts to setting up a prototype method. First we need to create our original class definition, which in most cases means creating an object. This definition contains a different part of each object instance. In my paint jQuery Plugin plugin, I wrote this:

function Canvas (settings)  {this.settings = Settings;this.draw = False;this.canvas = Null;this.ctx = Null;return this ;  }

Here's how to add a global approach:

Canvas.prototype =  {generate:function () {//generate Code}}

The key here is to make the prototype method generic, but the data is each instance of its own and can be referenced with "this".

7. Use the "this" object

By using "$this", we can pass the correct reference to another closure. We may also need to pass $this references to other methods. It should be noted that the name of the $this can be changed, arbitrary variable names can be.

Canvas.prototype =  {generate:function ()   {//some Codevar $this = This;var Buton =//...some Codebutton.click ( function () {//using This is found since it has it ' s own this//use $this instead. $this. SomeFunc ($this);});},somefun C:function ($this)      {//won ' t know what "this" is.//use $this instead passed from the Click event}}

8. Save the settings in each of the objects

I always save my settings in each object and then manipulate its own settings. So you don't have to pass a lot of arguments in different ways. Putting these variables in the object also makes it easy for you to call these variables elsewhere.

function Canvas (settings)  {this.settings = Settings;return this;}

9. Separating your prototype method logic

This may be a basic principle. When you hesitate to provide a way, you can ask yourself, "If someone else wants to rewrite this method, will your code meet his needs?" Or "how difficult is it for someone else to write this method?" Of course, this is a matter of flexibility. Here is a list of my color picker jQuery Plugin methods, you can refer to:

Generate () appendcolors () ColorSelect () Colorhoveron () Colorhoveroff () appendtoelement () Showpalette () Hidepalette ()

10. Setter/getter Options available

This one is not necessary, but I found all my plugins are in this one. Because it only requires a little bit of code, it can provide someone with a function that he might need.

Basically, we just have to let the developer set or get the value that the element already exists:

var linewidth = $ ("#container"). Wpaint ("LineWidth");  $ ("#container"). Wpaint ("LineWidth", "5");

Summary: The above 10 articles basically cover the core of jquery plug-in development, and can be used as a development template. A set of basic code can greatly shorten your development time, and will allow you to design the plug-in architecture more confident.

10 tips for writing a good jquery plugin