I'm having trouble picking between two approaches to controllers vs views in ExtJS4... my projects are in various states of adhering to one or the other:
Views contain no procedural code at all outside maybe an initComponent override that applies default configs. The view is mostly only lazy components specs and config options. This approach seems to lend itself well to using a tool like Designer to generate view classes that can be dropped in with your controller with no changes or letting human designers manage views without tripping over code.
Controllers know nothing of CSS classes and DOM structure and only handle application-level logic and coordination between views. Views contain as little procedural code as possible, doing just enough to turn DOM events into higher-level component events and to encapsulate reading/updating their state.
I'm wondering if anyone has committed to one for awhile and has anything feelings to share on where it got them?
DOMless controllers seems like a cleaner separation of concerns, but dumb views might offer a more convenient workflow. I've also seen another pattern from I think the old version of designer where components are split into two classes: a UI layer and then a logic layer that extends it. Has anyone tried mixing that approach with ExtJS4s MVC structure?