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 benefits of this pattern

Most of the time, the Facade Pattern is adopted for implementation parts that have a relatively high degree of complexity and are used in several places of an application, wherein large pieces of code can be replaced with a simple call to the created Facade, leading not only to less code repetition, but also helping us to increase the readability of the implementation. Since the Facade methods are usually named by the higher-level application concepts that they encapsulate, the resulting code is also easier to understand. The simplified API that a Facade provides through its convenient methods, leads to an implementation that is easier to use, understand, and also write unit tests for.

Moreover, having Facades to abstract complex implementations proves its usefulness in cases where there is a need to introduce a change to the business logic of the implementation. In case a Facade has a well-designed API with a prediction for future requirements, such changes can...