MDrivenStart DefineViews
No edit summary
No edit summary
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
ViewModels (Views) are perspectives on 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.
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.


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 that having something to start with - this is your typical seeker - that helps user find objects they can show in rooted document screens).
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, '''[[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.


{{Template:MDrivenStart_Template}}
{{Template:MDrivenStart_Template}}
[[Category:MDrivenStart]]

Revision as of 05:52, 24 July 2023

This page was created by Hans.karlsen@mdriven.net on 2020-07-08. Last edited by Stephanie@mdriven.net on 2025-01-31.

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.

Back One Back to Start Chat Updated!

MDriven Chat

How would you like to chat today?

Setting up your conversation…

This may take a few moments