4 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
5 <title>The source code</title>
6 <link href="../prettify/prettify.css" type="text/css" rel="stylesheet" />
7 <script type="text/javascript" src="../prettify/prettify.js"></script>
8 <style type="text/css">
9 .highlight { display: block; background-color: #ddd; }
11 <script type="text/javascript">
12 function highlight() {
13 document.getElementById(location.hash.replace(/#/, "")).className = "highlight";
17 <body onload="prettyPrint(); highlight();">
18 <pre class="prettyprint lang-js"><span id='Ext-app-Controller-method-constructor'><span id='Ext-app-Controller'>/**
19 </span></span> * @class Ext.app.Controller
21 * Controllers are the glue that binds an application together. All they really do is listen for events (usually from
22 * views) and take some action. Here's how we might create a Controller to manage Users:
24 * Ext.define('MyApp.controller.Users', {
25 * extend: 'Ext.app.Controller',
28 * console.log('Initialized Users! This happens before the Application launch function is called');
32 * The init function is a special method that is called when your application boots. It is called before the
33 * {@link Ext.app.Application Application}'s launch function is executed so gives a hook point to run any code before
34 * your Viewport is created.
36 * The init function is a great place to set up how your controller interacts with the view, and is usually used in
37 * conjunction with another Controller function - {@link Ext.app.Controller#control control}. The control function
38 * makes it easy to listen to events on your view classes and take some action with a handler function. Let's update
39 * our Users controller to tell us when the panel is rendered:
41 * Ext.define('MyApp.controller.Users', {
42 * extend: 'Ext.app.Controller',
46 * 'viewport > panel': {
47 * render: this.onPanelRendered
52 * onPanelRendered: function() {
53 * console.log('The panel was rendered');
57 * We've updated the init function to use this.control to set up listeners on views in our application. The control
58 * function uses the new ComponentQuery engine to quickly and easily get references to components on the page. If you
59 * are not familiar with ComponentQuery yet, be sure to check out THIS GUIDE for a full explanation. In brief though,
60 * it allows us to pass a CSS-like selector that will find every matching component on the page.
62 * In our init function above we supplied 'viewport > panel', which translates to "find me every Panel that is a direct
63 * child of a Viewport". We then supplied an object that maps event names (just 'render' in this case) to handler
64 * functions. The overall effect is that whenever any component that matches our selector fires a 'render' event, our
65 * onPanelRendered function is called.
67 * <u>Using refs</u>
69 * One of the most useful parts of Controllers is the new ref system. These use the new {@link Ext.ComponentQuery} to
70 * make it really easy to get references to Views on your page. Let's look at an example of this now:
72 * Ext.define('MyApp.controller.Users', {
73 * extend: 'Ext.app.Controller',
85 * click: this.refreshGrid
90 * refreshGrid: function() {
91 * this.getList().store.load();
95 * This example assumes the existence of a {@link Ext.grid.Panel Grid} on the page, which contains a single button to
96 * refresh the Grid when clicked. In our refs array, we set up a reference to the grid. There are two parts to this -
97 * the 'selector', which is a {@link Ext.ComponentQuery ComponentQuery} selector which finds any grid on the page and
98 * assigns it to the reference 'list'.
100 * By giving the reference a name, we get a number of things for free. The first is the getList function that we use in
101 * the refreshGrid method above. This is generated automatically by the Controller based on the name of our ref, which
102 * was capitalized and prepended with get to go from 'list' to 'getList'.
104 * The way this works is that the first time getList is called by your code, the ComponentQuery selector is run and the
105 * first component that matches the selector ('grid' in this case) will be returned. All future calls to getList will
106 * use a cached reference to that grid. Usually it is advised to use a specific ComponentQuery selector that will only
107 * match a single View in your application (in the case above our selector will match any grid on the page).
109 * Bringing it all together, our init function is called when the application boots, at which time we call this.control
110 * to listen to any click on a {@link Ext.button.Button button} and call our refreshGrid function (again, this will
111 * match any button on the page so we advise a more specific selector than just 'button', but have left it this way for
112 * simplicity). When the button is clicked we use out getList function to refresh the grid.
114 * You can create any number of refs and control any number of components this way, simply adding more functions to
115 * your Controller as you go. For an example of real-world usage of Controllers see the Feed Viewer example in the
116 * examples/app/feed-viewer folder in the SDK download.
118 * <u>Generated getter methods</u>
120 * Refs aren't the only thing that generate convenient getter methods. Controllers often have to deal with Models and
121 * Stores so the framework offers a couple of easy ways to get access to those too. Let's look at another example:
123 * Ext.define('MyApp.controller.Users', {
124 * extend: 'Ext.app.Controller',
127 * stores: ['AllUsers', 'AdminUsers'],
130 * var User = this.getUserModel(),
131 * allUsers = this.getAllUsersStore();
133 * var ed = new User({name: 'Ed'});
138 * By specifying Models and Stores that the Controller cares about, it again dynamically loads them from the appropriate
139 * locations (app/model/User.js, app/store/AllUsers.js and app/store/AdminUsers.js in this case) and creates getter
140 * functions for them all. The example above will create a new User model instance and add it to the AllUsers Store.
141 * Of course, you could do anything in this function but in this case we just did something simple to demonstrate the
144 * <u>Further Reading</u>
146 * For more information about writing Ext JS 4 applications, please see the <a href="../guide/application_architecture">
147 * application architecture guide</a>. Also see the {@link Ext.app.Application} documentation.
149 * @docauthor Ed Spencer
152 Ext.define('Ext.app.Controller', {
153 <span id='Ext-app-Controller-cfg-id'> /**
154 </span> * @cfg {String} id The id of this controller. You can use this id when dispatching.
158 observable: 'Ext.util.Observable'
161 onClassExtended: function(cls, data) {
162 var className = Ext.getClassName(cls),
163 match = className.match(/^(.*)\.controller\./);
165 if (match !== null) {
166 var namespace = Ext.Loader.getPrefix(className) || match[1],
167 onBeforeClassCreated = data.onBeforeClassCreated,
169 modules = ['model', 'view', 'store'],
172 data.onBeforeClassCreated = function(cls, data) {
174 items, j, subLn, item;
176 for (i = 0,ln = modules.length; i < ln; i++) {
179 items = Ext.Array.from(data[module + 's']);
181 for (j = 0,subLn = items.length; j < subLn; j++) {
184 prefix = Ext.Loader.getPrefix(item);
186 if (prefix === '' || prefix === item) {
187 requires.push(namespace + '.' + module + '.' + item);
195 Ext.require(requires, Ext.Function.pass(onBeforeClassCreated, arguments, this));
200 constructor: function(config) {
201 this.mixins.observable.constructor.call(this, config);
203 Ext.apply(this, config || {});
205 this.createGetters('model', this.models);
206 this.createGetters('store', this.stores);
207 this.createGetters('view', this.views);
215 init: function(application) {},
217 onLaunch: function(application) {},
219 createGetters: function(type, refs) {
220 type = Ext.String.capitalize(type);
221 Ext.Array.each(refs, function(ref) {
223 parts = ref.split('.');
225 // Handle namespaced class names. E.g. feed.Add becomes getFeedAddView etc.
226 Ext.Array.each(parts, function(part) {
227 fn += Ext.String.capitalize(part);
232 this[fn] = Ext.Function.pass(this['get' + type], [ref], this);
234 // Execute it right away
240 ref: function(refs) {
242 refs = Ext.Array.from(refs);
243 Ext.Array.each(refs, function(info) {
245 fn = 'get' + Ext.String.capitalize(ref);
247 me[fn] = Ext.Function.pass(me.getRef, [ref, info], me);
252 getRef: function(ref, info, config) {
253 this.refCache = this.refCache || {};
255 config = config || {};
257 Ext.apply(info, config);
259 if (info.forceCreate) {
260 return Ext.ComponentManager.create(info, 'component');
264 selector = info.selector,
265 cached = me.refCache[ref];
268 me.refCache[ref] = cached = Ext.ComponentQuery.query(info.selector)[0];
269 if (!cached && info.autoCreate) {
270 me.refCache[ref] = cached = Ext.ComponentManager.create(info, 'component');
273 cached.on('beforedestroy', function() {
274 me.refCache[ref] = null;
282 control: function(selectors, listeners) {
283 this.application.control(selectors, listeners, this);
286 getController: function(name) {
287 return this.application.getController(name);
290 getStore: function(name) {
291 return this.application.getStore(name);
294 getModel: function(model) {
295 return this.application.getModel(model);
298 getView: function(view) {
299 return this.application.getView(view);