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
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

Introducing the Factory Pattern


The Factory Pattern is part of the group of Creational Patterns and overall it describes a generic way for object creation and initialization. It is commonly implemented as an object or function that is used to generate other objects. According to the majority of Computer Science resources, the reference implementation of the Factory Pattern is described as a class that provides a method that returns newly created objects. The returned objects are commonly the instances of a specific class or subclass, or they expose a set of specific characteristics.

The key concept of the Factory pattern is to abstract the way an object or a group of related objects are created and initialized for a specific purpose. The point of this abstraction is to avoid coupling an implementation with specific classes or the way that each object instance needs to be created and configured. The result is an implementation that works as an abstract way for object creation and initialization...