Full analysis of jQuery plug-in development

There are two types of jQuery plug-in development: one is class-level plug-in development, that is, adding new global functions to jQuery, which is equivalent to adding methods to the jQuery class itself. jQuery's global functions are functions that belong to the jQuery namespace. The other is object-level plug-in development, which is to add methods to jQuery objects. The development of the two functions is described in detail below.
1. Class-level plug-in development
The most direct understanding of class-level plug-in development is to add class methods to the jQuery class, which can be understood as adding static methods. A typical example is the $.AJAX() function, which is defined in the jQuery namespace. Plug-in development at the class level can be extended in the following forms:
1.1 Add a new global function
To add a global function, we only need to define it as follows:
Java code

Copy code The code is as follows:

 
jQuery.foo = function() { 
alert('This is a test . This is only a test.'); 
}; 

1.2 Add multiple global functions
To add multiple global functions, you can use the following definition:
Java code

Copy code The code is as follows:

 
jQuery.foo = function() { 
alert( 'This is a test. This is only a test.'); 
}; 
jQuery.bar = function(param) { 
alert('This function takes a parameter, which is "' param ' ".'); 
}; 

is called the same as a function: jQuery.foo();jQuery.bar(); or $.foo();$.bar ('bar');
1.3 Use jQuery.extend(object);
Java code

Copy code The code is as follows:

 
jQuery.extend({ 
foo: function() { 
alert('This is a test. This is only a test.'); 
}, 
bar: function(param) { 
alert('This function takes a parameter, which is "' param '".'); 
} 
}); 

1.4 Using namespaces
Although in the jQuery namespace, we prohibit the use of a large number of javaScript function names and variable names. But it is still inevitable that some function or variable names will conflict with other jQuery plug-ins, so we are used to encapsulating some methods into another custom namespace.
Java code

Copy code The code is as follows:

 
jQuery.myPlugin = { 
foo:function() { 
alert('This is a test. This is only a test.'); 
}, 
bar:function(param ) { 
alert('This function takes a parameter, which is "' param '".'); 
} 
}; 

9 .Function using namespace is still a global function, the method used when calling:
10.$.myPlugin.foo();
11.$.myPlugin.bar('baz');
Passed With this trick (using separate plugin names), we can avoid namespace function conflicts.
2. Object-level plug-in development
Object-level plug-in development requires the following two forms:,
Form 1:
Java code

Copy code The code is as follows:

 
(function($){ 
$.fn.extend({ 
pluginName:function(opt,callback){ 
// Our plugin implementation code goes here. 
} 
}) 
})(jQuery); 
 

Form 2:
Java code

Copy code The code is as follows:

 
(function($) { 
$.fn.pluginName = function() { 
// Our plugin implementation code goes here. 
}; 
.})(jQuery); 

A jQuery function is defined above, and the formal parameter is $. After the function definition is completed, pass the jQuery actual parameter in. It will be called and executed immediately. The advantage of this is that when we write a jQuery plug-in, we can also use the $ alias without causing conflict with the prototype.
2.1 Declare a name in the JQuery namespace
This is a single plug-in script. If your script contains multiple plug-ins, or reciprocal plug-ins (for example: $.fn.doSomething() and $.fn.undoSomething()), then you need to declare multiple function names. However, usually when we write a plug-in, we strive to use only one name to encompass all of its contents. Our example plugin is named "highlight"
Java code

Copy code The code is as follows:

 
$.fn.hilight = function() { 
// Our plugin implementation code goes here. 
}; 
Our plugin is called like this: 
$('#myDiv').hilight(); 

But what if we need to decompose our implementation code into multiple functions? There are many reasons: design needs; This is easier or more readable to implement; and it is more object-oriented. This is a real hassle, breaking the functionality into multiple functions without adding unnecessary namespaces. We can do this out of recognition and utilization of functions as the most basic class objects in JavaScript. Just like other objects, functions can be specified as properties. Therefore, we have declared "hilight" as a jQuery property object. Any other properties or functions we need to expose can be declared as properties in the "hilight" function. Continue later.
2.2 Accepting the options parameter to control the behavior of the plugin
Let’s add the ability to specify the foreground and background colors to our plugin. We might pass the options to the plugin function as an options object. For example:
Java code

Copy code The code is as follows:

 
// plugin definition 
$.fn.hilight = function(options) { 
var defaults = { 
foreground: 'red', 
background: 'yellow' 
}; 
// Extend our default options with those provided. 
var opts = $.extend(defaults, options); 
// Our plugin implementation code goes here. 
}; 
Our plug-in can be called like this: 
$('#myDiv').hilight({ 
foreground: 'blue' 
.}); 

2.3 Exposing the default settings of the plug-in
One improvement we should make to the above code is to expose the default settings of the plug-in. This makes it easier for users of the plugin to overwrite and modify the plugin with less code. Next we start using function objects.
Java code

Copy code The code is as follows:

 
// plugin definition 
$.fn.hilight = function(options) { 
// Extend our default options with those provided. 
// Note that the first arg to extend is an empty object - 
// this is to keep from overriding our "defaults" object. 
var opts = $.extend({}, $.fn.hilight.defaults, options); 
/ / Our plugin implementation code goes here. 
}; 
// plugin defaults - added as a property on our plugin function 
$.fn.hilight.defaults = { 
foreground: 'red', 
background: 'yellow' 
}; 
Now users can include a line like this in their scripts: 
//This only needs to be called once, and does not have to be called in the ready block 
$.fn.hilight.defaults.foreground = 'blue'; 
Next we can use the plug-in like this method, which sets the foreground color to blue: 
$('#myDiv').hilight(); 

Now users can include a line like this in their scripts Here:

Copy code The code is as follows:

 
//This only needs to be called once, and does not have to be called in the ready block 
$.fn.hilight.defaults.foreground = 'blue'; 
Next we can use it like this The plugin's method, as a result it sets the blue foreground color: 
$('#myDiv').hilight(); 
As you can see, we allow the user to write a line of code that sets the plugin's default foreground color. And users can still selectively override these new default values ​​when needed: 
// Override the default background color of the plug-in 
$.fn.hilight.defaults.foreground = 'blue'; 
// ... 
// Call the plugin with a new default setting 
$('.hilightDiv').hilight(); 
// ... 
// Pass Configuration parameters to plugin methods to override default settings 
$('#green').hilight({ 
foreground: 'green' 
}); 

2.4 Appropriate Exposing some functions
will step by step extend your plug-in in interesting ways to the previous code (and let others extend your plug-in). For example, our plug-in implementation can define a function called "format" to format highlighted text. Our plug-in now looks like this, the implementation of the default format method is under the hiligth function.
Java code

Copy code The code is as follows:

 
// plugin definition 
$.fn.hilight = function(options) { 
// iterate and reformat each matched element 
return this.each(function() { 
var $this = $(this); 
// ... 
var markup = $this.html(); 
// call our format function 
markup = $ .fn.hilight.format(markup); 
$this.html(markup); 
}); 
}; 
// define our format function 
$.fn.hilight.format = function(txt) { 
return '' txt ''; 
}; 

We easily support other properties in the options object by allowing a callback function to override the default settings. This is another great way to modify your plugins. The technique shown here is to further effectively expose the format function so that it can be redefined. With this technique, others can override your plugin by passing their own settings, in other words, so that others can write plugins for your plugin.
Considering the useless plugins we created in this article, you may be wondering when exactly these would be useful. A real example is the Cycle plug-in. This Cycle plug-in is a sliding display plug-in, which can support many internal transformation effects to scroll, slide, fade away, etc. But in practice, there is no way to define every type of effect that might be applied to a sliding change. That's where this extensibility is useful. The Cycle plugin exposes "transitions" objects to users, allowing them to add their own transformation definitions. The definition in the plug-in is like this:

Copy the code The code is as follows:

 
$.fn.cycle .transitions = { 
// ... 
}; 

This trick enables others to define and pass transformation settings to Cycle plugins.
2.5 Keep private functions private
This technique is very powerful in exposing part of your plugin to be overridden. But you need to think carefully about the exposed parts of your implementation. Once exposed, you need to keep in mind that any changes to parameters or semantics may break backward compatibility. A general rule of thumb is that if you're not sure whether to expose a particular function, then you probably don't need to do that.
So how do we define more functions without messing up the namespace or exposing the implementation? This is the function of closures. To demonstrate, we will add another "debug" function to our plugin. This debug function will output the selected element format to the firebug console. To create a closure, we will wrap the entire plugin definition in a function.
Java code

Copy code The code is as follows:

 
(function($) { 
// plugin definition 
$.fn.hilight = function(options) { 
debug(this); 
// ... 
. }; 
// private function for debugging 
function debug($obj) { 
if (window.console && window.console.log) 
window. console.log('hilight selection count: ' $obj.size()); 
}; 
// ... 
})(jQuery); 

Our "debug" method is not accessible from the outer closure and is therefore private to our implementation.
2.6 Support for Metadata plug-ins
Based on the plug-in you are writing, adding support for Metadata plug-ins can make it more powerful. Personally, I like this Metadata plugin because it lets you use a few "markup" options to override the plugin (which is very useful when creating examples). And supporting it is very simple. Update: A little optimization suggestion in the comments.
Java code

Copy code The code is as follows:

 
$.fn.hilight = function(options) { 
// ... 
// build main options before element iteration 
var opts = $.extend({}, $.fn.hilight. defaults, options); 
return this.each(function() { 
var $this = $(this); 
// build element specific options 
var o = $.meta ? $.extend({}, opts, $this.data()) : opts; 
//... 

These change lines do some Thing: It tests whether the Metadata plugin is installed. If it is installed, it can extend our options object by extracting the metadata line and adding it as the last parameter to JQuery.extend, which will now override any other options settings. We can drive behavior from "markup", if we select "markup":
When calling, we can write: jQuery.foo(); or $.foo();
Java code

Copy code The code is as follows:


. 
Have a nice day! 


< ;div class="hilight { foreground: 'orange' }"> 
Have a nice day! 


9. Have a nice day!
10.

Full analysis of jQuery plug-in development_jquery