Difference between revisions of "JQuery"

From Klenwell Wiki
Jump to navigation Jump to search
(Overview)
(Plugin Pattern)
 
Line 19: Line 19:
 
To build your own classic jQuery plugin that can be used like so:
 
To build your own classic jQuery plugin that can be used like so:
  
<pre>$('.div').foo()</pre>
+
<pre>$('.div').myPlugin()</pre>
  
 
Boilerplate template to get you started here:
 
Boilerplate template to get you started here:
  
 
* https://github.com/jquery-boilerplate/jquery-boilerplate/blob/master/src/jquery.boilerplate.js
 
* https://github.com/jquery-boilerplate/jquery-boilerplate/blob/master/src/jquery.boilerplate.js

Latest revision as of 16:46, 9 October 2020

Overview

In deference to the KISS principle, I generally prefer to use jQuery over some of the newer more complex frontend frameworks if at all possible. For most CRUD applications, jQuery usually fits the bill.

When writing jQuery code, I usually adopt one of the following patterns:

Another more specialized pattern is the web widget pattern. This would be used to build a centralized widget pushed out to multiple sites (e.g. Disqus comment forms).

Module Pattern

The module is best used for modules where the abstraction is centralized and does not require multiple instantiations (as with a class object).

For an example of the modular pattern, see the following :

Plugin Pattern

To build your own classic jQuery plugin that can be used like so:

$('.div').myPlugin()

Boilerplate template to get you started here: