I agree, we should either use JSON or XML there. Both is no problem in any language, especially in Java, which I want to use for the Editor.
My early idea was to leave the cfg-style mission file, but use it to refer to additional files in XML or JSON, so we can reuse common files and simply refer to them in our "mission file system".
---------- Post added at 06:16 PM ---------- Previous post was at 06:14 PM ----------
Can I use that MECOCalc even if I'm already post-launch?
Yes, but it does then not include your current state vector. Generally, you accept some minor differences there and only get corrections or apply corrections from checklist, if the differences are huge.