I read a couple of things about MVC, but I still don't understand when they should be used and when they should not be used. I am looking for clear examples that say things like “ if you are developing this, then you should use MVC, for example this “ and “ if you are developing this, you should not use MVC. ” Most of the examples I saw are rely on complex structures that have already implemented everything, and you need to study the structure and use it to understand what is actually happening. For many programmers, phrases such as " business user interface logic " sound like marketing terms - for example, the words " Instead, the view is attached directly to the view model " is used in this message.
I know about the dangers that can be hidden in the shadows, since MVC is a concept, and everyone feels that they know it best, but no one knows exactly how to use it, because there can be many variables, and each allowed another The prospect is how to analyze the project in the model, view and controller. There is a lot of theory, but very few clear examples. What I'm looking for is not the “best” ways to do this so that it is not considered subjective; I am looking for various simple implementations that let me decide for myself which ones work best.
In short: What are some good online resources that provide pro and con arguments for using MVC in various situations and provide clear examples to help the reader understand the concept?
model-view-controller
Tom Nov 20 '08 at 10:02 2008-11-20 10:02
source share