Description
Hi Bruno
I am trying out v2 of the Router, and have noticed that override for controller's render() method is not no longer in your example. Now, you are using dispatch() event to automate rendering....
But I noticed that view generation is rather rigid in a sense where view is inferred from names of controllers and its action e.g.:
viewClass = Ext.ClassManager.get('SinglePage.view.' + controller + '.' + action);
My question is following:
Is there a way to pass in extra params to dispatch event from action?
This would allow me to pass in view xtype, viewmodel, weather I want it in a tab or dialog/window, should it be modal or not, closeable or not, etc, etc....I agree that rendering process should be left for each app to do, but it would be nice to be able to automate it....
My current solution is that I am still using override for controller render() method which accepts extra params, and then every controller action that maps to a route has to call it (a bit of a pain). If I could somehow send view xtype and view config to dispatch() that would be great...