No edit summary |
m (Stephanie moved page MDrivenStart DefineViews to MDrivenStart:MDrivenStart DefineViews) |
Revision as of 12:20, 13 January 2023
ViewModels (Views) are perspectives formed from part of the information available in the model. The ViewModels can be used for defining a user interface (UI) but can just as well define the information available to a REST-API or the data available in a report.
You may use the AutoForm-technique to rapidly create ViewModels to browse EVERYTHING in your current model.
All ViewModels must state what Class they are typed to, but a ViewModel must also state if it is rooted in an object of that class (it is given access to a specific instance object from your Class, this is your typical Document - Screens) - or not rooted (it must find its information on type level - grabbing things from "thin air" rather than having something to start with. This is your typical seeker; it helps users find objects they can show in rooted document screens).
Once you have views, you can verify that everything is coherent and no errors are found in the model - and then start the Prototyper to interact with your system.