3 ms·
people... two things: * MVC is not only about user interaction/UI. User interaction/UI is just most used area. i have used MVC inside a compiler, and inside da
by svilen_dobrev 8y ago
people... two things:
* MVC is not only about user interaction/UI. User interaction/UI is just most used area. i have used MVC inside a compiler, and inside data-crunching-pipeline. Fits perfect, as long one abstracts oneself from what user/business means.
* MVC is not single thing, it's a fractal idea. The View (may) has its own internal MVC (e.g. in UI: a widget, i.e. scrollbar), Model has its own (e.g. somewhat around ORM), ... and this may go further down - or up.
* it's a general concept saying that 3 islands/aspects talking to each other are needed for complete system; 2 are too few, 4 might be too many.
have fun