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

Revisiting index.html file


If you recall, in Chapter 8, Application Implementation – Putting It All Together, I mentioned that we were using quite a few <script> tags in our index.html file to load our application's modules.

To refresh your memory, here is what we had:

While this implementation worked, it was not very scalable, since for each module file we needed to add a <script> tag to our page. Also, by looking at the list of files being loaded, we could not determine how each module or component was dependent on another piece (or pieces) of the application.

We had to create another <script> tag at the bottom of the page as well, which took care of booting-up the application, as shown here:

It would be nice if we could eliminate the need for having all the <script> tags and our boot-up sequence in index.html. Also, it would be very useful to implement a mechanism which could indicate and mange our modules' dependencies.

Well, we are going to achieve all that very soon...