Timeline for Is it fair to call a database or a document a "Model", as in Model/View/Controller?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 5, 2013 at 0:01 | comment | added | Loki Astari | @DougM: Its a pattern not an implementation. It shows you how the data flows. But if we are talking about an implementation then usually you register views with the model so that when the model changes the views are notified. It is up to the view to decide what to change in the user interface (if anything). | |
| Aug 4, 2013 at 23:44 | comment | added | DougM | Does a view ALWAYS have to be updated when the model changes, or only when there is a substantial revision? (i.e., if I tack-on a "lastEditBy" tracking internally bound to the current user account, just in the model, does the View need to be adjusted even if the app itself will never see the information?) | |
| Aug 4, 2013 at 18:08 | vote | accept | DougM | ||
| Aug 4, 2013 at 18:01 | history | answered | Loki Astari | CC BY-SA 3.0 |