Follow me Stepbystep Flex tutorial

According to the consistent style, the purpose of writing this article and AMF that the same, and also hope that the reader if the concept of MVC if not understand, after reading the content, the best (necessary) in-depth understanding of learning.

People who have used the web framework struts, webwork, or other frameworks should be familiar with MVC.

The so-called MVC, is model, view and controller.

Model is the data models.

View is the user interface.

Controller is the controller.

MVC is a design pattern invented by Xerox PARC in the 80 's for programming languages Smalltalk-80, and is widely used. It was later recommended as the design model for Sun (already acquired by Oracle) Java platform.

MVC has basically become the accepted design pattern of the web framework, and the existing popular web framework basically follows this design pattern.

What are the benefits of the MVC design pattern?

1, low coupling.

This means that the view and business layers are separate.

2, High reusability.

Multiple views (that is, the user interface, the popular saying, hehe) can share a data model. For example, whether users want to use a traditional Web page, Flash page or WAP page, you can use a model for processing.

3, maintainability.

The business layer and view layer are separate, which is more advantageous to the maintenance of the code.

4, rapid development.

The MVC pattern makes development time shorter. Makes Java program personnel more focused on the business layer, Web pages can be more focused on the page.

Oh, say this, a lot of people will say, now the company wants a person all dry, what points?

This may be the case in most cases, but the benefits of this development have been experienced by the authors.

When China Mobile network management development, the business layer and the page is separate development, so cooperate, progress quickly, because the page developers do not need to focus on complex business, the latter developers only use the Java language and do not care about complex JSP pages and cumbersome JavaScript.

Useful is useful.

5, Software Management.

Layered clear, structured, not conducive to code management is strange, hehe.

There are good and bad, but to understand this bad will be to the MVC design pattern in-depth understanding, the author here to briefly mention that interested readers can be in-depth study.

Obviously, the layering, the code file will increase, this is inevitable. Oh, this is also a disadvantage, of course, forget it. But this shortcoming is not worth the benefit of MVC.

I have to mention it. But the shortcoming is the shortcoming, again small also is the shortcoming. Do not be good at small but not for, do not use evil small and for it (why do you say this sentence?) Just make it a little bit humorous in the boring technical theory.

As for the diagram of MVC, the author does not draw, there are many online.

Writing this content is to make readers pay attention to it and attach great importance to this concept. If this does not understand, for the Flex development Framework Caringorm understanding will be greatly discounted even do not understand very much, this to the reader caused by confusion than understanding, the technology of this road has a suspicion.

Therefore, all technology, to understand the principle. Just like the author, the use of struts,webwork, caringorm and so on are extremely easy (blowing cattle, forgive Ah, the literati are light, do technology, I think it is heavier, so I forgive this big boast bar, haha).

The next lecture will talk about the theoretical knowledge of the Cairngorm framework, but before that, if you do not understand the MVC, then you must make full use of time and network or books to study well.

Article Source: http://wangyisong.javaeye.com/blog/434282