@chebrock said:
@chillenious said:
That would be the controller.Yes, I would say that too but it's a blurry issue. The controller is acting like a view in that it responds to external changes in the model. I feel like this is a flaw in the concept of the pattern.
Well, the original definition says: "The controller interprets the mouse and keyboard inputs from the user, commanding the model and/or the view to change as appropriate."
So it is the responsibility of the controller to update the view when the model changes. In practice though, certainly when it comes to web frameworks, I think the controller is often bypassed and the view 'pulls' it's recent values (and thus any updates) without needing the controller directly. And yeah, it does get blurry pretty fast :-) Personally, I prefer to use patterns as rough ideas of how certain problems can be solved rather than exact descriptions.