So I'm just going to use the standard model to show these things. And what has happened from before is that we have a new icon here that calls the turnkey live editor. And this is the view model editor.

So they resemble each other. And it's a combination of the run button, which we had from before, where you prototype and start the system in either BPF or in the local turnkey prototyper. So this is sort of a hybrid between the view model editor, where you actually change the definition of the views, and this way you actually run the application.

So if I push this one, I always get a corresponding view model connected to it, because they share some of the logic. So if you don't want to see it, you don't need to look at it, but it's there.

And this is basically a embedded browser, the new WebView2, Microsoft's embedded Edge browser, which is replacing the old Internet Explorer and Edge. So what happened there was they said that, well, there's no connection to the target machine. So what we want to do is to set up a server.

So this is something that looks very much as it did in the play button, that we can check if we have a current turnkey core installed, we need one of those, and that we can use. So this is new, and particularly Eulage has been asking for the ability to connect it to a M-driven server instead. So this is optional.

You can either run it towards a local XML file, or you can use the M-driven server, and that will use the settings from the cloud connection for data. Sweet. So, and if you that one, this button lights up, and you get to this one where you actually can set the server that you want to run against.

But for now, I'm going to use the XML. So what I want to do is to restart the turnkey core, and this new text highlights in red when it discovers that if there is a server running, or the settings from before doesn't match the file that we're actually working on. So I'm working on a file that's stored in the internet cache here, so sample model for association.

I'm going to restart the server, and once that is done, I can fold this tab again, and then this one is started with our application. So this is basically just the application in the browser, nothing to it so far. But when we choose to fold down this live edit tab, we get the view model tree, and also some of the few of the settings that are interesting per view model column.

So when I click something here, like this, all things, I can see that this is positioned at the position 0x and 0y, and if I were to change this to like 10 instead, this would immediately jump, and I don't have to refresh or anything, and that's the beauty of us running within a harness like this, because we can do the push and refresh for you, so to make things move smoother. And as I've shown before, we can also move things around like this, and since this is the running application, I can expect to find the actions, I can create a new thing, and I can save that, and if, well, this is small screen, so I'm gonna view one thing.

So that's pretty much all what we prior to view models did with handles and the cursor manager handlers to point out which object was currently in a hierarchy and things like that everything of that type is encapsulated in the view model implementation and of course you could just as well have done a transient class called view one thing and added these derived attributes or have them as their own properties and that that would sort of solve the same problem but this is fewer clicks and and less things to maintain.

Watch the video to learn more

(Video)