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

Advantages of writing automated tests


As developers, our primary concern is to write code that can produce the expected functionality and results. While this principle holds true, the way we achieve our final implementation goal is also very important.

A properly designed application is not just about achieving the final goal of the application but it should also be about implementing an easily extensible and maintainable code-base.

Using a modular approach certainly helps us with achieving such objectives but as we make changes to our code-base, and as our application goes through its life cycle, we need to make sure all the pieces of the application still work properly.

When we make a change to one part of the application, we need to make sure that the change does not adversely affect the other parts of our code base. Of course, one way of assuring this, is to test everything manually and check every aspect of our application under all the circumstance that it was designed for. But such an...