Thunderbird/NextGeneration/MVC - Revision history

Mkmelin: schedule for deletion

2019-11-15T13:22:26Z

schedule for deletion

← Older revision		Revision as of 13:22, 15 November 2019
Line 1:		Line 1:
			{{delete\|This page contains personal plans that are no longer relevant, and could be confusing for people looking into Thunderbird plans. Should have been on a user page to start with. \|date=2019-11-15}}

	= Application tiers =		= Application tiers =

BenB: /* Access */ typo

2017-08-14T22:54:12Z

Access: typo

← Older revision		Revision as of 22:54, 14 August 2017
Line 20:		Line 20:
	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.

	Specifically, the model must never ever access the view, but the view ~~access~~ the model, and the view watches changes in the model by subscribing observers.		Specifically, the model must never ever access the view, but the view accesses the model (both read and write), and the view watches changes in the model by subscribing observers.

BenB: Access

2017-08-14T22:53:22Z

Access

@@ Line 4: / Line 4: @@
 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"]
     * [[Thunderbird/NextGeneration/Storage|Storage]]
@@ Line 12: / Line 10: @@
     * [[Thunderbird/NextGeneration/View|View]]
-[Terminology: In classic Smalltalk MVC, the JavaScript that handles user input and reacts to it is called “Controller” and the rest are part of the “View”. Here, we will lump both together and call them both the “View”. Note that the term “Controller” is sometimes mis-used for code that drives actions that were not initiated by the end user, but initiated by the application or outside input. According to “Design Patters” book, “the Controller defines the way the user interface reacts to user input”. Thus, to avoid confusion, we will instead use the term “services” for components that initiate non-user actions. This is in line with Mozilla terminology.]
+== Controller ==

BenB: Controller clarification

2017-08-14T22:49:46Z

Controller clarification

← Older revision		Revision as of 22:49, 14 August 2017
Line 11:		Line 11:
	* [[Thunderbird/NextGeneration/Services\|Services]]		* [[Thunderbird/NextGeneration/Services\|Services]]
	* [[Thunderbird/NextGeneration/View\|View]]		* [[Thunderbird/NextGeneration/View\|View]]

			[Terminology: In classic Smalltalk MVC, the JavaScript that handles user input and reacts to it is called “Controller” and the rest are part of the “View”. Here, we will lump both together and call them both the “View”. Note that the term “Controller” is sometimes mis-used for code that drives actions that were not initiated by the end user, but initiated by the application or outside input. According to “Design Patters” book, “the Controller defines the way the user interface reacts to user input”. Thus, to avoid confusion, we will instead use the term “services” for components that initiate non-user actions. This is in line with Mozilla terminology.]

BenB: /* Application tiers */ Add links to tiers

2017-08-14T22:14:14Z

Application tiers: Add links to tiers

← Older revision		Revision as of 22:14, 14 August 2017
Line 6:		Line 6:

	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.

			* [[Thunderbird/NextGeneration/Storage\|Storage]]
			* [[Thunderbird/NextGeneration/Model\|Model]]
			* [[Thunderbird/NextGeneration/Services\|Services]]
			* [[Thunderbird/NextGeneration/View\|View]]

BenB: /* Application tiers */ mod

2017-08-14T22:13:28Z

Application tiers: mod

← Older revision		Revision as of 22:13, 14 August 2017
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 ~~of classic Smalltalk MVC~~: "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"]		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.

BenB: Intro to MVC

2017-08-14T22:13:02Z

Intro to MVC

New page

= Application tiers =

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 of classic Smalltalk MVC: "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.