Is it worth to make "a straight-forward version" of it? It would be work just for this release... we are still using the next version for the Mission Editor and configuration development, right?
Yeah, I think that the pain is there to have a proper tool to make this all easier.
But then, why I am not sure if it is a good idea to plan for using it:
It is right now a very specialized tool with very specialized requirements. A mission editor would have different requirements, which include the requirements of MECOTool. It might be tempting to do it all right now, but as I see it, it is also a development delay.
As little as MECOTool really does: Is it really a problem to redo it then from ground up? After all, all it does are three small calculations right now.
Which would mean, if aiming at proper reuse later: Three classes should implement the calculations, one model class is needed for describing the intermediate orbits, one model class describes MECO parameters, another model class the OMS PEG7 targets.
Add an yet unknown number of view model classes for binding the model data to the view.
And now the classic problem: Do we want to spent the needed effort now before release? Or later after release?
Considering the many open questions in my analysis, I
feel like I want to do this later, but feel free to convince me of the alternative.
Also as another factor there: Starting after release would make it easier to instantly push towards a continuous delivery development process for the mission editor, so that it should always be possible to include a version of the mission editor as soon as the Orbiter add-on is ready for release. But that's no show stopper for doing this before release, since we could at least find the time for doing the commit stage properly already.
).
