* parts of the app - namely the Models, Views and Controllers that are bundled with the application. Let's say we have a blog management app; we* might have Models and Controllers for Posts and Comments, and Views for listing, adding and editing Posts and Comments.* Note that we didn't actually list the Views directly in the Application itself. This is because Views are managed by* Controllers, so it makes sense to keep those dependencies there. The Application will load each of the specified* Controllers using the pathing conventions laid out in the [application architecture guide](../../../application_architecture/application_architecture.html) - in this case* expecting the controllers to reside in app/controller/Posts.js and app/controller/Comments.js. In turn, each* Controller simply needs to list the Views it uses and they will be automatically loaded. Here's how our Posts* Because we told our Application about our Models and Controllers, and our Controllers about their Views, Ext JS will* automatically load all of our app files for us. This means we don't have to manually add script tags into our html* files whenever we add a new class, but more importantly it enables us to create a minimized build of our entire* For more information about writing Ext JS applications, please see the [application architecture guide](../../../application_architecture/application_architecture.html).