Editing Model–view–controller (section)

== Motivation ==
As [[Alan Kay]] wrote in 2003, the original motivation behind the MVC was to allow creation of a graphical interface for any object.<ref name=":0">{{Cite web |title= is squeak really object oriented ? |url= http://lists.squeakfoundation.org/pipermail/squeak-dev/2003-May/058824.html |author= Alan Kay |work= Squeak Foundation mailing list |date= 23 May 2003 |access-date= 26 October 2021 }}</ref> That was outlined in detail in Richard Pawson's book ''[[Naked objects|Naked Objects]]''.<ref name=":0" />

Trygve Reenskaug, originator of MVC at PARC, has written that "MVC was conceived as a general solution to the problem of users controlling a large and complex data set."<ref name="page_trygver" />

In their 1991 guide ''Inside Smalltalk'', [[Carleton University]] computer science professors Wilf LaLonde and John Pugh described the advantages of Smalltalk-80-style MVC as:
* independence of presentation and data, e.g. multiple views on one model simultaneously,
* composable presentation widgets, e.g. one view used as a subview of another,
* switchable input modes, by swapping one controller out for another during [[Software execution|runtime]], and
* independence of input and output processing, via the [[Separation of concerns|separate responsibilities]] of controllers and views.<ref>{{cite book |last1=LaLonde |first1=Wilf R. |last2=Pugh |first2=John R. |date=1991 |title=Inside Smalltalk |url=https://books.google.com/books?id=RRkiAQAAIAAJ |volume=2 |location=U.S.A. |publisher=Prentice-Hall Inc. |isbn=0-13-467309-3 |pages=8–9}}</ref>