Chapter 3. Application Structure

We previously discussed how growing an application organically without any sense of architecture could result in an unmaintainable mess of spaghetti code. One of the great things about imposing structure is that it automatically gives predictability (a kind of filing system with in which we immediately know where a particular piece of code should live).

The same applies to the files that make up your application. Certainly, we could put all of our files in the root of the website, mixing CSS, JavaScript, configuration and HTML files in a long alphabetical list, but we'd be losing out on a number of opportunities to keep our application organized. In this chapter, we'll look at:

• Ideas to structure your code
• The layout of a typical Ext JS application
• Use of singletons, mixins, and inheritance
• Why global state is a bad thing

Structuring your application is like keeping your house in order. You'll know where to find your car keys, and you...