No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
ViewModels (Views) are perspectives formed from part of the information available in the model. ViewModels can be used | ViewModels (Views) are perspectives formed from part of the information available in the model. ViewModels can be used to define a user interface (UI) as well as describe the information available to a REST-API or the data available in a report. | ||
You may use the AutoForm | 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 | All ViewModels must state what Class they are typed to. 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, '''[[MDrivenStart Verify|you can verify]]''' that everything is coherent and no errors are found in the model and then '''[[MDrivenStart Prototyper|start the Prototyper]]''' to interact with your system. | Once you have views, '''[[MDrivenStart Verify|you can verify]]''' that everything is coherent and no errors are found in the model and then '''[[MDrivenStart Prototyper|start the Prototyper]]''' to interact with your system. | ||
Revision as of 05:52, 24 July 2023
ViewModels (Views) are perspectives formed from part of the information available in the model. ViewModels can be used to define a user interface (UI) as well as describe 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. 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.