![\"Folder](\"guides/application_architecture/folderStructure.png\")
Large client side applications have always been hard to write, hard to organize and hard to maintain. They tend to quickly grow out of control as you add more functionality and developers to a project. Ext JS 4 comes with a new application architecture that not only organizes your code but reduces the amount you have to write.
\n\nOur application architecture follows an MVC-like pattern with Models and Controllers being introduced for the first time. There are many MVC architectures, most of which are slightly different from one another. Here's how we define ours:
\n\nModel is a collection of fields and their data (e.g. a User model with username and password fields). Models know how to persist themselves through the data package, and can be linked to other models through associations. Models work a lot like the Ext JS 3 Record class, and are normally used with Stores to present data into grids and other components
View is any type of component - grids, trees and panels are all views.
Controllers are special places to put all of the code that makes your app work - whether that's rendering views, instantiating Models, or any other app logic.
In this guide we'll be creating a very simple application that manages User data. By the end you will know how to put simple applications together using the new Ext JS 4 application architecture.
\n\nThe application architecture is as much about providing structure and consistency as it is about actual classes and framework code. Following the conventions unlocks a number of important benefits:
\n\nExt JS 4 applications follow a unified directory structure that is the same for every app. Please check out the Getting Started guide for details explanation on the basic file structure of an application. In MVC layout, all classes are placed into the app folder, which in turn contains sub-folders to namespace your models, views, controllers and stores. Here is how the folder structure for the simple example app will look when we're done:
In this example, we are encapsulating the whole application inside one folder called 'account_manager'. Essential files from the Ext JS 4 SDK are wrapped inside ext-4.0 folder. Hence the content of our index.html looks like this:
<html>\n<head>\n <title>Account Manager</title>\n\n <link rel=\"stylesheet\" type=\"text/css\" href=\"ext-4.0/resources/css/ext-all.css\">\n\n <script type=\"text/javascript\" src=\"ext-4.0/ext-debug.js\"></script>\n\n <script type=\"text/javascript\" src=\"app.js\"></script>\n</head>\n<body></body>\n</html>\napp.jsEvery Ext JS 4 application starts with an instance of Application class. The Application contains global settings for your application (such as the app's name), as well as maintains references to all of the models, views and controllers used by the app. An Application also contains a launch function, which is run automatically when everything is loaded.
\n\nLet's create a simple Account Manager app that will help us manage User accounts. First we need to pick a global namespace for this application. All Ext JS 4 applications should only use a single global variable, with all of the application's classes nested inside it. Usually we want a short global variable so in this case we're going to use \"AM\":
\n\nExt.application({\n name: 'AM',\n\n appFolder: 'app',\n\n controllers: [\n 'Users'\n ],\n\n launch: function() {\n Ext.create('Ext.container.Viewport', {\n layout: 'fit',\n items: [\n {\n xtype: 'panel',\n title: 'Users',\n html : 'List of users will go here'\n }\n ]\n });\n }\n});\nThere are a few things going on here. First we invoked Ext.application to create a new instance of Application class, to which we passed the name \"AM\". This automatically sets up a global variable AM for us, and registers the namespace to Ext.Loader, with the corresponding path of 'app' set via the appFolder config option. We also told our Application about the Users controller, which we'll come back to in a moment. Finally, we provided a simple launch function that just creates a Viewport which contains a single Panel that will fill the screen.
![\"Initial](\"guides/application_architecture/panelView.png\")
Most applications will have several controllers - usually one for each Model. By specifying an array of controllers your application is using, the corresponding classes of these controllers will automatically be loaded and initialized before the application is launched. This can be handy when setting up listeners to the Viewport, for example. In this example, our Users controller will be mapped to the AM.controller.Users class, the file of which is located in app/controller/User.js
Controllers are the glue that binds an application together. All they really do is listen for events (usually from views) and take some actions. Continuing our Account Manager application, here's how we might start off our Users controller:
Ext.define('AM.controller.Users', {\n extend: 'Ext.app.Controller',\n\n init: function() {\n console.log('Initialized Users! This happens before the Application launch function is called');\n }\n});\nWhen we load our application by visiting index.html inside a browser, the Users controller is automatically loaded (because we specified it in the Application definition above), and its init function is called just before the Application's launch function.
The init function is a great place to set up how your controller interacts with the view, and is usually used in conjunction with another Controller function - control. The control function makes it easy to listen to events on your view classes and take some action with a handler function. Let's update our Users controller to tell us when the panel is rendered:
Ext.define('AM.controller.Users', {\n extend: 'Ext.app.Controller',\n\n init: function() {\n this.control({\n 'viewport > panel': {\n render: this.onPanelRendered\n }\n });\n },\n\n onPanelRendered: function() {\n console.log('The panel was rendered');\n }\n});\nWe've updated the init function to use this.control to set up listeners on views in our application. The control function uses the new ComponentQuery engine to quickly and easily get references to components on the page. If you are not familiar with ComponentQuery yet, be sure to check out this guide for a full explanation. In brief though, it allows us to pass a CSS-like selector that will find every matching component on the page.
In our init function above we supplied 'viewport > panel', which translates to \"find me every Panel that is a direct child of a Viewport\". We then supplied an object that maps event names (just render in this case) to handler functions. The overall effect is that whenever any component that matches our selector fires a render event, our onPanelRendered function is called.
When we run our application now we see the following:
\n\n![\"Controller](\"guides/application_architecture/firstControllerListener.png\")
Not exactly the most exciting application ever, but it shows how easy it is to get started with organized code. Let's flesh the app out a little now by adding a grid.
\n\nUntil now our application has only been a few lines long and only inhabits two files - app.js and app/controller/Users.js. Now that we want to add a grid showing all of the users in our system, it's time to organize our logic a little better and start using views.
A View is nothing more than a Component, usually defined as a subclass of an Ext JS component. We're going to create our Users grid now by creating a new file called app/view/user/List.js and putting the following into it:
Ext.define('AM.view.user.List' ,{\n extend: 'Ext.grid.Panel',\n alias : 'widget.userlist',\n\n title : 'All Users',\n\n initComponent: function() {\n this.store = {\n fields: ['name', 'email'],\n data : [\n {name: 'Ed', email: 'ed@sencha.com'},\n {name: 'Tommy', email: 'tommy@sencha.com'}\n ]\n };\n\n this.columns = [\n {header: 'Name', dataIndex: 'name', flex: 1},\n {header: 'Email', dataIndex: 'email', flex: 1}\n ];\n\n this.callParent(arguments);\n }\n});\nOur View class is nothing more than a normal class. In this case we happen to extend the Grid Component and set up an alias so that we can use it as an xtype (more on that in a moment). We also passed in the store configuration and the columns columns that the grid should render.
\n\nThe only other change we need to make now is to update app.js to use our new view. Because we set an alias using the special 'widget.' format, we can use 'userlist' as an xtype now, just like we had used 'panel' previously. Let's add this view in our Users controller
Ext.define('AM.controller.Users', {\n extend: 'Ext.app.Controller',\n\n views: [\n 'user.List'\n ],\n\n init: ...\n\n onPanelRendered: ...\n});\nAnd then render it inside the main viewport by changing app.js to:
Ext.application({\n name: 'AM',\n\n controllers: [\n 'Users'\n ],\n\n launch: function() {\n Ext.create('Ext.container.Viewport', {\n layout: 'fit',\n items: {\n xtype: 'userlist'\n }\n });\n }\n});\nThe only other thing to note here is that we specified 'user.List' inside the views array. This tells the application to load that file automatically so that we can use it when we launch. The application uses Ext JS 4's new dynamic loading system to automatically pull this file from the server. Here's what we see when we refresh the page now:
![\"Our](\"guides/application_architecture/firstView.png\")
Note that our onPanelRendered function is still being called. This is because our grid class still matches the 'viewport > panel' selector. The reason for this is that our class extends Grid, which in turn extends Panel.
At the moment, the listeners we add to this selector will actually be called for every Panel or Panel subclass that is a direct child of the viewport, so let's tighten that up a bit using our new xtype. While we're at it, let's instead listen for double clicks on rows in the grid so that we can later edit that User:
\n\nExt.define('AM.controller.Users', {\n extend: 'Ext.app.Controller',\n\n views: [\n 'user.List'\n ],\n\n init: function() {\n this.control({\n 'userlist': {\n itemdblclick: this.editUser\n }\n });\n },\n\n editUser: function(grid, record) {\n console.log('Double clicked on ' + record.get('name'));\n }\n});\nNote that we changed the ComponentQuery selector (to simply 'userlist'), the event name (to 'itemdblclick') and the handler function name (to 'editUser'). For now we're just logging out the name of the User we double clicked:
![\"Double](\"guides/application_architecture/doubleClickHandler.png\")
Logging to the console is all well and good but we really want to edit our Users. Let's do that now, starting with a new view in app/view/user/Edit.js:
Ext.define('AM.view.user.Edit', {\n extend: 'Ext.window.Window',\n alias : 'widget.useredit',\n\n title : 'Edit User',\n layout: 'fit',\n autoShow: true,\n\n initComponent: function() {\n this.items = [\n {\n xtype: 'form',\n items: [\n {\n xtype: 'textfield',\n name : 'name',\n fieldLabel: 'Name'\n },\n {\n xtype: 'textfield',\n name : 'email',\n fieldLabel: 'Email'\n }\n ]\n }\n ];\n\n this.buttons = [\n {\n text: 'Save',\n action: 'save'\n },\n {\n text: 'Cancel',\n scope: this,\n handler: this.close\n }\n ];\n\n this.callParent(arguments);\n }\n});\nAgain we're just defining a subclass of an existing component - this time Ext.window.Window. Once more we used initComponent to specify the complex objects items and buttons. We used a 'fit' layout and a form as the single item, which contains fields to edit the name and the email address. Finally we created two buttons, one which just closes the window, and the other that will be used to save our changes.
All we have to do now is add the view to the controller, render it and load the User into it:
\n\nExt.define('AM.controller.Users', {\n extend: 'Ext.app.Controller',\n\n views: [\n 'user.List',\n 'user.Edit'\n ],\n\n init: ...\n\n editUser: function(grid, record) {\n var view = Ext.widget('useredit');\n\n view.down('form').loadRecord(record);\n }\n});\nFirst we created the view using the convenient method Ext.widget, which is equivalent to Ext.create('widget.useredit'). Then we leveraged ComponentQuery once more to quickly get a reference to the edit window's form. Every component in Ext JS 4 has a down function, which accepts a ComponentQuery selector to quickly find any child component.
Double clicking a row in our grid now yields something like this:
\n\n![\"Loading](\"guides/application_architecture/loadedForm.png\")
Now that we have our edit form it's almost time to start editing our users and saving those changes. Before we do that though, we should refactor our code a little.
\n\nAt the moment the AM.view.user.List component creates a Store inline. This works well but we'd like to be able to reference that Store elsewhere in the application so that we can update the data in it. We'll start by breaking the Store out into its own file - app/store/Users.js:
Ext.define('AM.store.Users', {\n extend: 'Ext.data.Store',\n fields: ['name', 'email'],\n data: [\n {name: 'Ed', email: 'ed@sencha.com'},\n {name: 'Tommy', email: 'tommy@sencha.com'}\n ]\n});\nNow we'll just make 2 small changes - first we'll ask our Users controller to include this Store when it loads:
Ext.define('AM.controller.Users', {\n extend: 'Ext.app.Controller',\n stores: [\n 'Users'\n ],\n ...\n});\nthen we'll update app/view/user/List.js to simply reference the Store by id:
Ext.define('AM.view.user.List' ,{\n extend: 'Ext.grid.Panel',\n alias : 'widget.userlist',\n\n //we no longer define the Users store inline\n store: 'Users',\n\n ...\n});\nBy including the stores that our Users controller cares about in its definition they are automatically loaded onto the page and given a storeId, which makes them really easy to reference in our views (by simply configuring store: 'Users' in this case).
At the moment we've just defined our fields ('name' and 'email') inline on the store. This works well enough but in Ext JS 4 we have a powerful Ext.data.Model class that we'd like to take advantage of when it comes to editing our Users. We'll finish this section by refactoring our Store to use a Model, which we'll put in app/model/User.js:
Ext.define('AM.model.User', {\n extend: 'Ext.data.Model',\n fields: ['name', 'email']\n});\nThat's all we need to do to define our Model, now we'll just update our Store to reference the Model name instead of providing fields inline, and ask the Users controller to get a reference to the model too:
//the Users controller will make sure that the User model is included on the page and available to our app\nExt.define('AM.controller.Users', {\n extend: 'Ext.app.Controller',\n stores: ['Users'],\n models: ['User'],\n ...\n});\n\n// we now reference the Model instead of defining fields inline\nExt.define('AM.store.Users', {\n extend: 'Ext.data.Store',\n model: 'AM.model.User',\n\n data: [\n {name: 'Ed', email: 'ed@sencha.com'},\n {name: 'Tommy', email: 'tommy@sencha.com'}\n ]\n});\nOur refactoring will make the next section easier but should not have affected the application's current behavior. If we reload the page now and double click on a row we see that the edit User window still appears as expected. Now it's time to finish the editing functionality:
\n\n
Now that we have our users grid loading data and opening an edit window when we double click each row, we'd like to save the changes that the user makes. The Edit User window that the defined above contains a form (with fields for name and email), and a save button. First let's update our controller's init function to listen for clicks to that save button:
\n\nExt.define('AM.controller.Users', {\n init: function() {\n this.control({\n 'viewport > userlist': {\n itemdblclick: this.editUser\n },\n 'useredit button[action=save]': {\n click: this.updateUser\n }\n });\n },\n\n updateUser: function(button) {\n console.log('clicked the Save button');\n }\n});\nWe added a second ComponentQuery selector to our this.control call - this time 'useredit button[action=save]'. This works the same way as the first selector - it uses the 'useredit' xtype that we defined above to focus in on our edit user window, and then looks for any buttons with the 'save' action inside that window. When we defined our edit user window we passed {action: 'save'} to the save button, which gives us an easy way to target that button.
We can satisfy ourselves that the updateUser function is called when we click the Save button:
![\"Seeing](\"guides/application_architecture/saveHandler.png\")
Now that we've seen our handler is correctly attached to the Save button's click event, let's fill in the real logic for the updateUser function. In this function we need to get the data out of the form, update our User with it and then save that back to the Users store we created above. Let's see how we might do that:
updateUser: function(button) {\n var win = button.up('window'),\n form = win.down('form'),\n record = form.getRecord(),\n values = form.getValues();\n\n record.set(values);\n win.close();\n}\nLet's break down what's going on here. Our click event gave us a reference to the button that the user clicked on, but what we really want is access to the form that contains the data and the window itself. To get things working quickly we'll just use ComponentQuery again here, first using button.up('window') to get a reference to the Edit User window, then win.down('form') to get the form.
After that we simply fetch the record that's currently loaded into the form and update it with whatever the user has typed into the form. Finally we close the window to bring attention back to the grid. Here's what we see when we run our app again, change the name field to 'Ed Spencer' and click save:
![\"The](\"guides/application_architecture/updatedGridRecord.png\")
Easy enough. Let's finish this up now by making it interact with our server side. At the moment we are hard coding the two User records into the Users Store, so let's start by reading those over AJAX instead:
\n\nExt.define('AM.store.Users', {\n extend: 'Ext.data.Store',\n model: 'AM.model.User',\n autoLoad: true,\n\n proxy: {\n type: 'ajax',\n url: 'data/users.json',\n reader: {\n type: 'json',\n root: 'users',\n successProperty: 'success'\n }\n }\n});\nHere we removed the 'data' property and replaced it with a Proxy. Proxies are the way to load and save data from a Store or a Model in Ext JS 4. There are proxies for AJAX, JSON-P and HTML5 localStorage among others. Here we've used a simple AJAX proxy, which we've told to load data from the url 'data/users.json'.
We also attached a reader to the Proxy. The reader is responsible for decoding the server response into a format the Store can understand. This time we used a JSON reader, and specified the root and successProperty configurations (see the Json Reader docs for more on those configurations). Finally we'll create our data/users.json file and paste our previous data into it:
{\n success: true,\n users: [\n {id: 1, name: 'Ed', email: 'ed@sencha.com'},\n {id: 2, name: 'Tommy', email: 'tommy@sencha.com'}\n ]\n}\nThe only other change we made to the Store was to set autoLoad to true, which means the Store will ask its Proxy to load that data immediately. If we refresh the page now we'll see the same outcome as before, except that we're now no longer hard coding the data into our application.
The last thing we want to do here is send our changes back to the server. For this example we're just using static JSON files on the server side so we won't see any database changes but we can at least verify that everything is plugged together correctly. First we'll make a small change to our new proxy to tell it to send updates back to a different url:
\n\nproxy: {\n type: 'ajax',\n api: {\n read: 'data/users.json',\n update: 'data/updateUsers.json'\n },\n reader: {\n type: 'json',\n root: 'users',\n successProperty: 'success'\n }\n}\nWe're still reading the data from users.json, but any updates will be sent to updateUsers.json. This is just so that we can return a dummy response so we know things are working. The updateUsers.json file just contains {success: true}. The only other change we need to make is to tell our Store to synchronize itself after editing, which we do by adding one more line inside the updateUser function, which now looks like this:
updateUser: function(button) {\n var win = button.up('window'),\n form = win.down('form'),\n record = form.getRecord(),\n values = form.getValues();\n\n record.set(values);\n win.close();\n this.getUsersStore().sync();\n}\nNow we can run through our full example and make sure that everything works. We'll edit a row, hit the Save button and see that the request is correctly sent to updateUser.json
![\"The](\"guides/application_architecture/postUpdatesToServer.png\")
The newly introduced Sencha SDK Tools (download here ) makes deployment of any Ext JS 4 application easier than ever. The tools allows you to generate a manifest of all dependencies in the form of a JSB3 (JSBuilder file format) file, and create a minimal custom build of just what your application needs within minutes.
\n\nPlease refer to the Getting Started for detailed instructions.
\n\nWe've created a very simple application that manages User data and sends any updates back to the server. We started out simple and gradually refactored our code to make it cleaner and more organized. At this point it's easy to add more functionality to our application without creating spaghetti code. The full source code for this application can be found in the Ext JS 4 SDK download, inside the examples/app/simple folder.
\n\nIn the next guide, we'll look at advanced Controller usage and patterns that can make your application code smaller and easier to maintain.
\n" +}); \ No newline at end of file