Thought to start this post with a small image, take a look.
Ok, some background.
As you might know, during 2014 Scumari created this wonderful application called: G-MissionX. It was his first attempt in developing on ".Net" and the result was a nifty application that allow you to design basic missions for Mission-X plugin.
The problem was, ".NET" ran only on Windows and Linux/Mac users could not use it. Another issue was: How could I update the application with new features if the code was not available ?
It took me more than a few years to finally decide to try my hand in programming under QT Creator IDE. I must admit that my first impression with this tool was: "Nice tool", and after few weeks of codding I can say it is "F*$%ing" great tool, especially in the cross platform section (haven’t tested the application under OSX, but I'm pretty sure it will work).
Design and road map
Currently, I must admit, there is no real design or layout road map. No real thought on how to approach such application, which make programming and maintaining the code pretty hard, but not that hard.
Since this is an IDE driven application, there are many events that stack to the main code pipe line and clutter the editor (in the good way).
What I'm trying to figure out so far is:
1. How to correctly load the XML file.
2. How to keep all elements intact.
3. How to save and when.
4. How to manage node information and modification.
5. Lots of other hows....
Currently the progress is quite good, but not enough testing where done.
I believe that when I'll finish first full implementation, I'll probably publish it under "GitHub", though I have no idea when it will be.
What is planned for first implementation
I hope to implement the basic features that makes Mission-X so simple to work with (from my point of view).
I hope to implement the following features:
- Step Management.
- Goal Definition (these are the step goals/targets).
- Trigger definition.
- Global Settings.
- Load/Save mission data.
- Mission Validation (test if current mission has all necessary configurations to properly work).
What the application won't do [for now]:
- It will not enforce proper naming or linking between elements.
So validation might come in handy before testing under X-Plane, but this will be implemented later on, now I'll continue to crash some more bugs.
Some more "eye candy" images
Here are some more screen shots. The coloring is for testing, so do not get too exited.
I'll keep you updated, until next time