CodeRage 7 - Malcolm Groves - An Introduction to Model-View-View Model (MVVM) in Delphi

With the addition of cross-platform support to Delphi, and the coming Mobile Studio product, there is an increasing need to have device-specific User Interfaces. At the same time, you want to minimize the amount of code you have to rewrite for each platform. This session will look at Model-View-ViewModel, one technique that leverages LiveBindings to not only minimize the effort required to slide different UIs in front of your code, but also increases the maintainability and testability of your app as a bonus.

CodeRage 7: Tuesday, November 6, 2012 - 3pm PST
Malcolm Groves - An Introduction to Model-View-View Model (MVVM) in Delphi.

[olivogiorni]

Nothing against MVVM It has some advantages, but:Having validation in the forms were never advised.Second, who in 2018, or in 2012 will migrate its UI by hand? Those who not talented enough, or think it does not worth to write a parser, can buy the Delphi Parser or anything else.What make people stay in DElphi s probably the code that should be in the controlers, the UI(OUR DFM ) is easy to port even to another language.

[michaelrempel]

Why not use Controller instead of View-Model? At least use different words.

Controllers need to be fairly universal. If we need one for each UI this gets confusing quickly. And avoiding the issue in an intro is a waste of time because it is an instant problem for anyone using it.

Richer validation and feedback in a string list is instantly needed as well. Linking forms to controllers is bad. Controllers need to be as small as possible. One form can have several controllers in a big UI.