Should MVC be called MCV?

Question

Data Flow Direction in MVC Template

Model -> Controller -> View 

therefore why is it not called the "MCV template"?

Is there anything significant about letter order in "MVC" or is it just softer?

Answer 1

MVC slips faster from the language.

In addition, the MCV is a mobile vehicle, would not want to confuse it.

Jokes aside read this

Answer 2

MVC was conceived as a general solution to the problem of users managing large and complex data set. The hardest part is to hit good names for different architectural components. Model-View-Editor was the first set:

Thing-model-view-editor

After much discussion, particularly with Adele Goldberg, we ended up with the terms Model-View-Controller:

Controller Models

(from http://heim.ifi.uio.no/~trygver/themes/mvc/mvc-index.html )

Answer 3

Here is my very scientific, commented, footnoted [1] guess:

 +-------+ +------+ | Model | | View | +-------+ +------+ | | +------------+ | +------------+ | Controller | +------------+ 

If you read it from left to right, this is Model-View-Controller.

[1] I really didn’t mention it [2]
[2] Wait. What kind?: -)

Answer 4

The question suggests some kind of flow, but it is not.

The model does not call the controller. The controller invokes the model and view, and there is nothing to stop viewing when checking the model. MVC simply lists the various problems in a specific order.

Answer 5

Why not CMV? You start by calling the controller method, the method on this controller decides which view will return to you (even if this is the default view), and it may or may not consult the model for data and functions to create this page view. Ergo CMV. Then, when the view comes back, it's VCMV.

Anyway, I am very pleased with MVC. The symbol has been recognized and understood.

Answer 6

I think this is more historical. MVC has been in software jargon for quite some time and is an outdated template from earlier versions of SmallTalk. There is no real reason to change it.

Answer 7

"I think" because the flow is bi-directional from the controller to both, model and views. Therefore, they call it Model / View Controller (controller "model" and "view") : /

Answer 8

what about VMVCV - indicate how you can use multiple views

Answer 9

It follows the same logic as dates, in order of importance.

Compare with dates: Month-Day-Year:

First comes the month, the most important number. This is the most direct participation in the season. You immediately snap the location to what we know about it.

Secondly, Day is coming - this is what everyone wants to know. Then a year follows.

In MVC, the model is most important. The model is king, baby. What follows is what most people experience, kind. Finally, we have a bad old controller.

This is according to American logic.

If your thought process follows a large and small order of priority (Year-month-day), as I believe, most OO programmers - then you will find MCV a more natural name.

Answer 10

I think that basically sounds, but you can also think about it in terms of importance. Obviously, data is the most important component, followed by how the user interacts with it. The least important part is how the system processes the input and prepares the output for display.

Answer 11

The MVC user interface paradigm or Model-View-Controller was first described by Trygve Reenskaug from Xerox PARC. First appeared in print in the magazine "Byut" volume 6, number 8, in August 1981.

He included the user and named him MVCU. Now it really is not going crazy, at least in English. Interestingly, it sounds like the Norwegian, Trygve native language.

Answer 12

From the end user action: the order specified only by MVC also matters

Answer 13

This is called MVC, not MCV or any other, because Model and Controller can be combined together, because both of them contain java.class files, where the view contains all the other .jsp, .html or any other resource files. So that M and C are not broken, it is divided by V and, therefore, is MVC.

Hope that is clear :)

Answer 14

In my opinion, the name MVC comes from 1979, a concept developed by Trygve Reenskaug to solve the problem of GUI software design. He had a Model that was called when the application started, then he had a browse page that displays the data, and on the destination controller when the user clicked on ex. for the flag, it uses the controller to update / change the model.

In this sense, the term MVC is correct. But I think that this has nothing to do with the modern "MVC architecture", I think the name should be RCMV, or at least CMV, of course. In modern applications, we first turn to the Route layer, and then at the Controller Model Control View level , so it should be called CMCV / RCMCV .

Can someone resume the discussion on this? These are really interesting things, am I wrong?