• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Future Direction For SDE

scruffyduck

scruffyduck

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,981
Country
unitedkingdom
There are now two client applications using SDE - the TestApp (GUI) and Bgl2Xml (Command Line). So in all there are really three packages:

1 SDE
2 Bgl2Xml
3 TestApp

I am expecting to start work on another client application shortly. I would like to get views on how things should go in the future.

SDE is really the engine so I plan to use that only to refer to the engine in future.

I will give future Client applications developed by me their own names.

I am thinking about how best to distribute client applications. An initial release would probably have the engine components included. Otherwise new uses would need to download the client and the engine (is that the way to do it?). The alternative is to release the client and ask the user to download the latest engine (or have the client do it first time it runs)

Certainly future apps ought to be able to get the latest engine automatically from the web.

Anyway this is probably rather rambling which just shows that I am not clear how to proceed :o :o :o :)
 
Hi Jon.

Many programs are released with both the client and the engine, then have a menu entry under "Help", that allows an "update" package to be downloaded. I like that approach. The "update" menu entry could link to a webpage for further info on the latest changes for the GUI or the engine.

I don't really like automatic updates, as the enduser may be pleased with an older version, and the new version could introduce unwanted changes/bugs... with no way to revert to the earlier version.


Dick
 
Hi Dick

Thanks for the response. Here is what I am doing. I have a menu option to check for updates. This allows a check to be made. The check returns either that the components are up to date or, if not, a clickable link to download the updated component.

This should be in the next builds of SDE TestApp and Bgl2Xml GUI
 
You must log in or register to reply here.
Back
Top