Confirmed users
596
edits
Thunderbird/NextGeneration/MVC: Difference between revisions
→Application tiers: mod
(Intro to MVC) |
(→Application tiers: mod) |
||
| Line 3: | Line 3: | ||
We will follow the mostly classic Smalltalk MVC model, with a slight adaption to the web. There are many derivations in use today, which are often conflicting, so we’ll describe what this means for a web-based application. | We will follow the mostly classic Smalltalk MVC model, with a slight adaption to the web. There are many derivations in use today, which are often conflicting, so we’ll describe what this means for a web-based application. | ||
Definition | Definition: "MVC consists of three kinds of objects. The Model is the application object, the View is its screen presentation, and the Controller defines the way the user interface reacts to user input. [Other] user interface designs tended to lump these objects together. MVC decouples them to increase flexibility and reuse." – from [https://en.wikipedia.org/wiki/Design_Patterns "Design patterns" book by the "Gang of Four"] | ||
Lower level tiers must never access higher level tiers. But rather, higher level tiers drive and call lower level tiers. | Lower level tiers must never access higher level tiers. But rather, higher level tiers drive and call lower level tiers. | ||