Why use Model-view-controller?

Question

Why should a developer pay attention to the Model-view-controller for designing a graphical interface? And are there any other elements that a developer should turn to developing a graphical interface?

Answer 1

MVC will help you separate the responsibility of the GUI from the business rules that you want, you may want to reuse some code later or change it if MVC helps you.

Here is another architecture for the GUI by Martin Fowler.

http://martinfowler.com/eaaDev/uiArchs.html

Model-View-Presenter (MVP)

Modest appearance

And further.

Answer 2

, , , -.

Answer 3

, , , , , MVC.

Answer 4

MVC , - .

http://en.wikipedia.org/wiki/Model -view-controller

Answer 5

Model View Controller :

    1. Data (Model) 
    2. User interface (View)
    3. Logic of the application (Controller)

. , , MVC .

, , - Object Relational Mapper. , - .

Answer 6

MVC - . Model-View-Controller.

:

- , ?

-View-Controller (MVC) , , [Burbeck92]:

• Model. , ( ), ( ).
• . .
• . , / .

Answer 7

, java, JavaFX -.

WPF Model-View-ViewModel,

• -, -,
• - , XAML
• ViewModel: , . . , , .

Answer 8

Model-view-controller - , ; . , GUI- + , + . , . + ( + ). ( , , MVC - , ).

MVC is very common because it is usually easy to understand and support, and widely applicable. My advice is to learn this well and use it often. But I also warn that it becomes your "hammer" (when you have a hammer, everything starts to look like a nail). Familiarize yourself with other options and use them when necessary.