Can anyone explain the connections between MVC elements using this picture as an example?

Or correct me:

  1. Controller → Model is a direct change by the controller of the model data.
  2. Model → Viev - this model notifies viev of the changes that have occurred in it.
  3. Viev → Model - this viev takes data from the model.
  4. Viev → Controller - this viev notifies the controller of the user's actions (the button, for example, pressed).
  5. Controller → Viev - and this connection, in my opinion, is superfluous and contradicts the MVC principle: "the controller is developed independently of viev, and interacts with it only through the model."
  • 2
    Less bother with the principles that are trying to impose "Big Scientists". Act "according to the situation" in accordance with "common sense." - avp

1 answer 1

In an ideal situation, yes, the controller should not know anything about the presentation, but in practice this is not always the case. Therefore, I agree with the first comment.