How to use Ext.dispatch( ) in Touch 2.x or an action controller

I hope the controller of Touch 1.x will be realized in Touch 2.x .
But now I'm very disappointed that the controller of Touch 2.x was made like Extjs 4.x .
The controller should be like an container with many of actions in mvc.In views we can call any action in events.It's the true MVC Framework like in touch 1.x .
In Touch 2.x and Extjs 4.0 the controller is without any action and was designed to be a listeners manager of the view.I can not understand the mean of this design.It will cause the controller is limited by the view design.

My English is not so good, bear with me a lot.I want that Ext.dispatch() and action controller will be realized in Touch 2.x .

That is heartbreaking . I urge you to reconsider. We would love to test and provide feedback on the MVC implementation even if it is not set in stone. Besides, how are we supposed to put Touch 2 through real world testing if there is no way for us to build up our own architecture.

The way to MVC is pretty unclear right now. I couldn't get Ext.dispatch working. Though after study of examples, I figured out that this.getController('App.controller.Foo') loads up /App/controller/Foo.js

So the show could be called up from a main controller as this.getController('App.controller.Foo').show()

I switched from PR2 to PR3 recently. I'm doing my current development on preview releases so as to have minimum friction when ST2 comes out. But I hope architecture guesswork from examples would hold in final release too.

The way to MVC is pretty unclear right now. I couldn't get Ext.dispatch working. Though after study of examples, I figured out that this.getController('App.controller.Foo') loads up /App/controller/Foo.js

So the show could be called up from a main controller as this.getController('App.controller.Foo').show()

I switched from PR2 to PR3 recently. I'm doing my current development on preview releases so as to have minimum friction when ST2 comes out. But I hope architecture guesswork from examples would hold in final release too.

That is good stuff! But how do you get your actions to render your views and pass the values to it?

My Main view is loading up every other view via requires: [ ... ], and has every view used in the app inside its items.

For passing values, lets say while I've to reveal a menu item, the show method of details view should have an id parameter. The details view would do appropriate data store calls, place in loading spinner, and remove when data comes in. The controls like list that are bound to data store would get rendered automatically, while if I've some other complex components, I could target them via refs and change them from controller.