4 ms·
One persistent source of ambiguity is the arrow from the controller to the view. I've seen so many implementations that take this to mean that in response to a
by sivanmz 12y ago
One persistent source of ambiguity is the arrow from the controller to the view. I've seen so many implementations that take this to mean that in response to a user action the controller modifies the model and updates the view, rather than letting the view observe the model.
My understanding of that arrow is that the controller may send messages to the view.
- fnayr 12y agoI think there's different approaches. Apple, for instance, approaches MVC that way (controller updating the view, with the view having no knowledge of the model).
- givanse 12y agoRight, there are different ways of doing it. In general, an arrow/line between Controller and View is better understood as "there is some type of communication"; then, different variations of the same design will use different forms of communication (observers, data binding, the controller references the view, the view references the controller etc).