Show
Destroy
An entry
Get it down. Make it good. Share it.
Title
Text
Model View Controller is a general description of a separation between common elements in a software application: * The Model - source data * View - visible representation of that data (as a list, diagram, or chart; for example) * Controller - translation of user intent between the Model and a View, and vice-versa Below are some general notes about distinctions in the term `MVC` and more descriptive descriptions of the term. Some people think this may be the most misunderstood design pattern. I disagree. But I think it helpful to understand the origins and intent of this pattern as it relates to addressing software design issues; especially regarding visually intense applications. --- > The Model-View-Controller pattern as an obvious solution to the general problem of giving users control over their information as seen from multiple perspectives. MVC has created a surprising amount of interest. Some texts even use perverted variants for the opposite purpose of making the computer control the user.   > To any given Model there is attached one or more Views, each View being capable of showing one or more pictorial representations of the Model on the screen and on hardcopy. A View is also able to perform such operations upon the Model that is reasonably associated with that View. > It should always be possible to write a method in a controller that sends messages to views which exactly reproduce any sequence of user commands. # References * http://beza1e1.tuxen.de/model_view_controller.html * http://heim.ifi.uio.no/~trygver/1979/mvc-1/1979-05-MVC.pdf * http://heim.ifi.uio.no/~trygver/1979/mvc-2/1979-12-MVC.pdf * https://dl.acm.org/citation.cfm?id=50757.50759 * https://en.wikipedia.org/wiki/Naked_objects
Status
idea
draft
release
personal
Series
Part of a Series?
Bitcoin
On Work
Phoenix Trello Tutorial
Civics
Re Email Address
Tags
MVC
×
design patterns
×
+
Slug
Url
Image 1
Image 2
Image 3
Visible
Date