Highly abstract MVC ignores the pitfalls of the following detail descriptions

Highly abstract MVC ignores the pitfalls of the following detail descriptions

The beautiful Life of the Sun Vulcan (http://blog.csdn.net/opengl_es)

This article follows "Attribution-non-commercial use-consistent" authoring public agreement

Reprint Please keep this sentence: Sun Vulcan's Beautiful Life-this blog focuses on Agile development and mobile and IoT device research: IOS, Android, HTML5, Arduino, Pcduino , Otherwise, the article from this blog refused to reprint or re-reproduced, thank you for your cooperation.

for MVVM I want to say: self-made things, the controller is simplified! The supplement to

MVC is the final result of software iteration, it is also the backbone, ignoring the details, and it is highly abstract, ignoring the specific implementation of the difference;

As a result, these neglected parts, or with or without the reverse transformation of the application, there are many unexpected malignant consequences;

MVC itself is dynamic, adapt to different environments and complexity, need to have different trade-offs;

Because of the wide adaptability, it is difficult to abstract;

However, the need to be widely disseminated, must be highly abstract, at the same time must be a trade-offs;

The result is an abstraction of the applicable and productive part;

The detail guiding meaning part is neglected;

In general this, MVC is dynamic, is extended, is a summary of practice, and there is no way to really use the MVC three letter to express the complete, MVC is only a landmark.

Then, the real embodiment of MVC lies in the dynamic expansion, separating the data and the presentation structure!

The simple application, the box section, the View controller appears all the logic, also does not have the quantity to say;

Complex application, the box section, should not appear any actual view or data related to the content, these parts should be gathered into the sub-class, the completion of each;

Complex applications, box sections, can only see the business logic, which is also a lot of elegant Java project innate characteristics;

Do not understand the business logic, can not understand the code context, this is right;