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

Components


The last main piece of our application design is related to components. In this section, we will cover how components are built and plugged into our application.

Remember that we considered components as pieces of the application that have views. By views, I am referring to the pieces that have HTML elements associated with them which are rendered in the browser and the users can interact with them directly.

Components can be as simple as a layover box. Such simple components can be rendered as part of another component or as a stand-alone component on their own.

Most of the time, our components are independent modules with their own MVC or MV* architecture, which are attached to the application and use the facilities and functionality that the rest of the application provides for them.

In our design, we have created three main components and a widget named NotificationWidget. This widget is also a component but it is loaded and viewed based on the user's interaction with another...