The model is defined first, then the controllers are fired based on the user request, and they will generate the views (the output).
So it should be M->C->V, right?
|
The model is defined first, then the controllers are fired based on the user request, and they will generate the views (the output). So it should be M->C->V, right? |
|||||||||||
|
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or specific expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, see the FAQ for guidance.
|
Because that's how the originator of the term ordered it. "MVC was first described in 1979[3] by Trygve Reenskaug, then working on Smalltalk at Xerox PARC." http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller |
|||
|
|
|
Maybe it comes down to dependancies and usage? Each item on the right knows about or uses the item on the left. Controller knows about views and models. Views know about Models. Models just know about themselves. So hence the naming convention MVC. Just my thoughts. |
|||||||
|
|
Yes this should be MCV but many acronyms are made in wrong order just because they sound better that way.
|
||||
|
|