I have a MVC (.NET) design, where there is no link to the model of the scene. It only knows about the controller that there is communication with each other in traditional MVC patterns. In my case, the controller is basically an arbitrator, there is no exception or argument from this view. There is zero dependency on its model. Is not it an MVC now?
What you're describing is actually a subset of Model-View-Controller.
Passive View Model-View Another variation on the controller and model-view-presenter is split between a scene with these UI which is the display and the controller that responds to user gestures. The key change with the passive view is that the scene has become completely disabled and is not responsible for updating itself from the model. As a result all visual logic is in the controller. As a result, there is no dependency in any direction between the view and the model.
discusses this and other variations about it in a nutshell.
Comments
Post a Comment