Geek Answers Handbook

Using MVC, how should the relationship between views be handled? Between models?

Question number three in my search in order to understand MVC correctly before I implement it:

I have two cases:

  • The main window application needs to run the settings window. (One species causing another species.)
  • The main application model is to access the property in the preference model. (One model access to another model.)

These questions are related to the fact that they are both related to the connection between the Model-View-Controller triplets, a topic that I did not discuss much in my Googling.

The obvious way to fix this is to wrap everything in a top-level “application” object that processes transactions between models and allows controllers to reference other methods. I have seen how this is implemented, but I'm not sure if this is a good idea. I also see opportunities involving controllers observing more than one model and responding to more than one view, but it seems like it will become very cluttered and difficult to follow.

Suggestions on how best to implement such a cross talk? I feel this is a very obvious question, but I could not find a well-documented solution.

, , MVC, . , . Python , -.

1:

, , , , . FrontController, . , , , , , - . , . , . ?

+5
3

(1) . , . (, ), .

(3), , , . , . , . Customer.

MVC wikipedia .

+3

, .

Front Controller , . , , , . , , : .

, FrontController, , () . , .

, . . , .

. .

+2

A model does not mean a single model object. A model is a subset of the entire model of your domain that is directly related to the actions of the controller and the views in question.

0
source

More articles:


All Articles