6 ms·
I think there's an easy answer to the question of what the controller is - it's the business logic. My main problem with the MVC pattern is actually related to
by smoyer 13y ago
I think there's an easy answer to the question of what the controller is - it's the business logic. My main problem with the MVC pattern is actually related to the model and view communicating directly. I started using the MVP pattern and then switched to passive view (http://martinfowler.com/eaaDev/PassiveScreen.html http://martinfowler.com/eaaDev/PassiveScreen.html) to eliminate as much code (and therefore testing) as possible from the view.
- tieTYT 13y agoNo that's what the model is for. The controller is just for handling framework specific input. It takes the framework specific part, puts it in a form that the business logic can understand (eg: business logic shouldn't even know what a mouseEvent is), and hands it off to the model's business logic to handle.