3 ms·
Sounds as if you prefer the Microsoft take on MVC, where they introduced the "UI Model" as an additional component. (Real) Model -> fetch -> UI Model -> build
by PaulDavisThe1st 6y ago
Sounds as if you prefer the Microsoft take on MVC, where they introduced the "UI Model" as an additional component.
(Real) Model -> fetch -> UI Model -> build -> View
^
|
v
build/modify
^
|
v
Controller
The UI Model serves as a simplified version of the "real" model that can also use the data structures/objects used by the technology used in the View.
In "original" MVC (outside of the use of this term in webdev), the "M" in MVC absolutely did refer to a 1:1 correspondence with the data at the core of the application. This works too, but when using various UI toolkits, adding the UI Model can make things feel a bit more natural.