As the title says, this thread is for the discussion associated with the SSU Workbench development.
Currently the mission file IO is pretty much established, but the scenario file IO is still to be done in detail: read the file, load to memory all the information contained in it and then output a file equal to the original, should be an initial goal before we start massaging the data.
Another thing to be decided is the "default" location of the exe and how it finds its way in the Orbiter installation. Currently the location of the orbiter.exe is required at the start, so later when saving the program knows where the Missions folder is (the user can choose where the scenario file goes, but as default the save dialog opens in the "Scenarios/Space Shuttle Ultra" folder).
We're also missing the "new" and "open" icons for the menu.
One more thing: could/should we add this project to the "main" SSU solution file? It would only be for the 2013 solution, but it would allow to have all the code under one umbrella.
Currently the mission file IO is pretty much established, but the scenario file IO is still to be done in detail: read the file, load to memory all the information contained in it and then output a file equal to the original, should be an initial goal before we start massaging the data.
Another thing to be decided is the "default" location of the exe and how it finds its way in the Orbiter installation. Currently the location of the orbiter.exe is required at the start, so later when saving the program knows where the Missions folder is (the user can choose where the scenario file goes, but as default the save dialog opens in the "Scenarios/Space Shuttle Ultra" folder).
We're also missing the "new" and "open" icons for the menu.
One more thing: could/should we add this project to the "main" SSU solution file? It would only be for the 2013 solution, but it would allow to have all the code under one umbrella.