Talk:Model–view–controller: Difference between revisions
m Archiving 1 discussion(s) to Talk:Model–view–controller/Archive 2) (bot |
|||
Line 22: | Line 22: | ||
I also concur. The diagram is incorrect. There's no direct interaction between the Model or View. [[User:WanderingFido|WanderingFido]] ([[User talk:WanderingFido|talk]]) 10:05, 17 January 2022 (UTC) <ref>https://www.freecodecamp.org/news/the-model-view-controller-pattern-mvc-architecture-and-frameworks-explained/</ref> |
I also concur. The diagram is incorrect. There's no direct interaction between the Model or View. [[User:WanderingFido|WanderingFido]] ([[User talk:WanderingFido|talk]]) 10:05, 17 January 2022 (UTC) <ref>https://www.freecodecamp.org/news/the-model-view-controller-pattern-mvc-architecture-and-frameworks-explained/</ref> |
||
: According to Krasner and Pope 1988: "The model carries out the prescribed operations, possibly changing its state, and broadcasts to its dependents (views and controllers) that it has changed, possibly telling them the nature of the change. Views can then inquire of the model about its new state, and update their display if necessary." so Model-View interaction is part of MVC as described in the original literature. But I do think there is room for improvement. The original literature includes the input and display devices as part of the diagram and also differentiates between state "change messages" and "access/editing messages". It may be useful to portray that distinction here. [[User:Elplatt|Elplatt]] ([[User talk:Elplatt|talk]]) 19:32, 26 January 2022 (UTC) |
Revision as of 19:33, 26 January 2022
This is the talk page for discussing improvements to the Model–view–controller article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
Archives: 1, 2Auto-archiving period: 30 days |
Computer science Start‑class Mid‑importance | |||||||||||||||||
|
|
On 26 May 2010, Model–view–controller was linked from Slashdot, a high-traffic website. (Traffic) All prior and subsequent edits to the article are noted in its revision history. |
Wiki Education Foundation-supported course assignment
This article is or was the subject of a Wiki Education Foundation-supported course assignment. Further details are available on the course page. Student editor(s): Mohammedhhassan.
Above undated message substituted from Template:Dashboard.wikiedu.org assignment by PrimeBOT (talk) 04:21, 17 January 2022 (UTC)
Picture issue
I share sentiment with comment above , that picture is disturbing . users (clients) should only interact with view objects while controllers 'goes' between views and model(data). 41.77.91.206 (talk) 07:17, 17 December 2021 (UTC)
I also concur. The diagram is incorrect. There's no direct interaction between the Model or View. WanderingFido (talk) 10:05, 17 January 2022 (UTC) [1]
- According to Krasner and Pope 1988: "The model carries out the prescribed operations, possibly changing its state, and broadcasts to its dependents (views and controllers) that it has changed, possibly telling them the nature of the change. Views can then inquire of the model about its new state, and update their display if necessary." so Model-View interaction is part of MVC as described in the original literature. But I do think there is room for improvement. The original literature includes the input and display devices as part of the diagram and also differentiates between state "change messages" and "access/editing messages". It may be useful to portray that distinction here. Elplatt (talk) 19:32, 26 January 2022 (UTC)