Book Image

Modular Programming with JavaScript

Book Image

Modular Programming with JavaScript

Overview of this book

Programming in the modular manner is always encouraged for bigger systems—it is easier to achieve scalability with modular programming. Even JavaScript developers are now interested in building programs in a modular pattern. Modules help people who aren’t yet familiar with code to find what they are looking for and also makes it easier for programmers to keep things that are related close together. Designing and implementing applications in a modular manner is highly encouraged and desirable in both simple and enterprise level applications. This book covers some real-life examples of modules and how we can translate that into our world of programming and application design. After getting an overview of JavaScript object-oriented programming (OOP) concepts and their practical usage, you should be able to write your own object definitions using the module pattern. You will then learn to design and augment modules and will explore the concepts of cloning, inheritance, sub-modules, and code extensibility. You will also learn about SandBoxing, application design, and architecture based on modular design concepts. Become familiar with AMD and CommonJS utilities. By the end of the book, you will be able to build spectacular modular applications in JavaScript.
Table of Contents (17 chapters)
Modular Programming with JavaScript
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
2
Review of Important JavaScript OOP Concepts
Index

Sandbox module


When we talk about a sandbox in our daily lives, we usually have a picture of a box full of sand in our minds, where we allow the kids to play and make all the mess they like - and hopefully only in that box.

In our modular architecture, we capitalize on the same concept and create spaces for our components to play in and to be isolated from other pieces of the application.

By sandboxing our modules in such a way, we eliminate tight coupling among our application components and the core module.

The sandbox is essentially a layer of abstraction as well as a thin interface between our components and the other pieces of our application.

As the sandbox module is designed to be an interface and to provide communication among our components and the rest of the application, it is considered a contract and, as such, it should never change. This is so our components can be sure that they can always count on a consistent layer of communication with the application as well as a certain level...