Book Image

jQuery Design Patterns

By : Thodoris Greasidis
Book Image

jQuery Design Patterns

By: Thodoris Greasidis

Overview of this book

jQuery is a feature-rich JavaScript library that makes HTML document traversal and manipulation, event handling, animation, and Ajax much simpler with an easy-to-use API that works across a variety of browsers. With a combination of versatility and extensibility, jQuery has changed the way that millions of people write JavaScript. jQuery solves the problems of DOM manipulation, event detection, AJAX calls, element selection and document queries, element attribute and data management, as well as object management utilities. This book addresses these problems and shows you how to make the best of jQuery through the various design patterns available. The book starts off with a refresher to jQuery and will then take you through the different design patterns such as facade, observer, publisher/subscriber, and so on. We will also go into client-side templating techniques and libraries, as well as some plugin development patterns. Finally, we will look into some best practices that you can use to make the best of jQuery.
Table of Contents (18 chapters)
jQuery Design Patterns
About the Author
About the Reviewer

The Revealing Module Pattern

The Revealing Module Pattern is a variant of the Module Pattern with a known and widely recognized name. What makes this pattern special is that it combines the best parts of the Object Literal Pattern and the Module Pattern. All the members of the Module are declared inside an IIFE, which at the end, returns an Object Literal containing only the public members of the Module and is assigned to the variable that acts as our Namespace:

var simpleguid = (function() { 
  var guid = 1; 

  function init() { 
    guid = 1; 

  function increaseCounter() { 

  function getNext() { 
    var nextGuid = guid; 
    return nextGuid; 

  return { 
    init: init, 
    getNext: getNext 

One of the main benefits of this pattern that differentiates it from other variants is that it allows us to write all the code of our Module inside the IIFE, just like we would if they would be declared on the Global Namespace...