Documentation:MDriven Designer Overview part 3

Review on the WECPOF prototyper application and continue on prototyping with actions and viewmodels.

To make your experience more comfortable, we set the main tags mentioned in the video to the right bar menu of this mini player. Choose the interesting subtitle on the list and immediately get to the exact theme timeplace in the video. Now you can pick any topic to be instructed without watching the whole video.

Running prototyper application More on WECPOF Action Definitions editor • Global actions Bring Up a View Model • ViewModel root object • Menu groups • Create/Init standart actions • Framework actions Nested ViewModel class • Grid options • Expressions • Global Action for Create/Global Action for show ViewModel action Class action Navigating Actions 3d rendering

To outset the guidance, we need to google for “MDriven”. As it takes us to the Capable Object site, on the “Downloads” tag head to “BuildServers”. By reaching the Build Servers, where we update all the builds daily, you will be able to find also the MDriven designer. Here we can find that required “MDriven Designer use the ClickOnce” tool. So, Click Once is the distribution technology from Microsoft. It updates every time there's a need, otherwise the application stays in your internet cache, so that's a good way to execute the application. For the Chrome or Firefox users you may need a “Click Once” plugin. ( In order to make the browser know what to do with the “Click once” extension). Once you’ve downloaded all the needed extensions and the browser is able to recognise them, you can safely launch the “MDriven Designer use the ClickOnce” link, as you already signed in. Then it started with the “Default” or starting model. You may prefer to work on a “Default model”, but we start from the beginning, to bring you the full exercise by choosing the new one. Following up on the benefits of the MDriven designer, here you can define your model and lots of things, regarding your application. We argue that you could create complete software systems using nothing, but modelling with the help of MDriven designer. Inasmuch as you might not believe, so will have to follow this guidance to get to that conclusion yourself. Back onto the next step, what we see first - is the overview screen and it shows, what diagrams there are. In our case as an example, we use only one diagram - "Diagram one". There is also a repository tree, where you also can create and see diagram structure. So, if we were to set up another diagram, by choosing '’Add Class diagram",' it would pop up on both overview screen and repository tree as "Diagram2".