3 ms·
Actually that's what MVC is supposed to be. Whether you use events, callbacks, delegates, or dirty checking really doesn't matter. Views inform the controller
by akrymski 13y ago
Actually that's what MVC is supposed to be. Whether you use events, callbacks, delegates, or dirty checking really doesn't matter. Views inform the controller, controller updates the model. Events and Operations are the Controller, but lets not shove MVC into some specific implementation based on events, it's an abstract pattern for software architecture, not a framework.
- asdasf 13y ago>Views inform the controller, controller updates the model No, that's not how it is supposed to work. The idea that everything has to pass through a controller for no reason, and that we need a controller per view, is the rails bastardization, not actual MVC.