Question

With ASP.NET MVC controllers, the controller itself responds with requests from the client to rebuild the view and/or supply data.

However, I’m trying to understand how a view relates to a Sencha Touch controller. I’ve not seen anywhere how a controller actually creates the views. Am I missing something?

How does this compare with ASP.NET MVC controllers?

Update
An update to my original query since some investigation. It seems that all controllers are loaded in by the app, and the controller itself has no knowledge of any particular view it refers to. It seems to listen to an event from any control on any view. So a controller could in effect respond to events from 2 completely different views.

Answer 1

You define what controls the Controller listens too in the “config>control” section, you uses a css like selector language to select the control, eg:

Ext.define('App.controller.MyController', {
    extend: 'Ext.app.Controller',

    config: {
        control: {
            'button': { tap: 'onButtonTap' },
            '#superButton': { tap: 'onSuperTap' }, //select by ID
            '#SpecificView textarea': {change: 'onChange'} // all textareas in the id:View
        }
    }
    ...
}