Well, if you didn't know, it's been already there for 29 minutes
:
https://bitbucket.org/face/genericvessel/
Yikes! I have a stalker! :lol:
I'm already writing a lot of specifications in a text file. When Face is ready with setting up the project, I will publish them
The Wiki is up and running. Go ahead and add pages with your specifications as you see fit. You need a user account there, but it is free, anyway.
If you don't want to do that, I guess a posting here is sufficient also.
So, to get it straight, the goal is to provide an alternative ground-up interpreter for SC3 initialisation files, which correctly parses files in the existing structure, while fixing bugs/limitations of SC3 and providing additional functionality, or to provide a new, but similar environment for non-programmer developers to create spacecraft?
In other words, is this a spiritual Spacecraft 4 or an entirely new system with a similar purpose?
I think it should be both. A standard SC3 INI set should work without changes IMHO. And of course nothing stops it from adding more features or even different description formats.
---------- Post added at 15:53 ---------- Previous post was at 15:22 ----------
I've made a few commits to the project's repository with vinka's packages extracted to a standard Orbiter directory (without the Orbiter files, of course). I think it is safe to upload them to the public repository, as he explicitly states in SC3 documentation:
All add-ons based on spacecraft3.dll may be distributed freely with this base package include.
For developers
The source code can be obtained upon request.
Such a setup will make it much easier for folks to test their work against various versions of the generic frameworks (SC1,2,3 and whatever the new is called then).
Of course I've taken care to keep the credits where they are due in the commits, so it is clear where the files are coming from in the history, even if we use them later on in the project as e.g. test scenarios.
If there are no objections, I'm going to push them to the repository and link the documentation PDFs for reference.