Timeline for How should the model notify changes to the controller in the MVC paradigm?
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 13, 2017 at 18:45 | vote | accept | mtber75 | ||
| Oct 12, 2017 at 15:07 | answer | added | Robert Harvey | timeline score: 2 | |
| Oct 12, 2017 at 15:01 | comment | added | Robert Harvey | Note that you can raise an event on a Model (and have any controller subscribe to that event) without the model having any knowledge of the controller. | |
| Oct 12, 2017 at 9:04 | answer | added | Ewan | timeline score: 2 | |
| Oct 12, 2017 at 8:20 | comment | added | Ewan | MVVP? what does it stand for? | |
| Oct 12, 2017 at 7:30 | comment | added | Bart van Ingen Schenau | @mtber75: The observer pattern is not just for communicating changes from the Model to the View, but for any case where one component must send updates to an unspecified number of other components and/or without a direct dependency between the components. | |
| Oct 12, 2017 at 3:20 | comment | added | mtber75 | Good question. The model should not know the implementation details of the view since the model should be respected with high-level policy and should not know about low-level policies, such as the view. Therefore, in this case, let's not consider the observer pattern for the model to communicate the view. | |
| Oct 12, 2017 at 3:19 | history | edited | mtber75 | CC BY-SA 3.0 |
added 270 characters in body
|
| Oct 12, 2017 at 2:49 | comment | added | Robert Harvey | Why are you eliminating the observer pattern from consideration? | |
| Oct 12, 2017 at 0:37 | history | edited | mtber75 | CC BY-SA 3.0 |
edited title
|
| Oct 12, 2017 at 0:27 | history | edited | mtber75 | CC BY-SA 3.0 |
added 166 characters in body
|
| Oct 12, 2017 at 0:23 | review | First posts | |||
| Oct 12, 2017 at 8:26 | |||||
| Oct 12, 2017 at 0:19 | history | asked | mtber75 | CC BY-SA 3.0 |