When doing any largish project, you need various support infrastructure. You need to be able to track your changes, and because working with multi-thousand line files is a right pain - you need some way to combine multiple files into one, and finally, you need to be able to run tests to ensure your code is valid.
This means we need:
- A Version Control System
- A build system
- A Test system
I'm a fan of git, and so the project is already up on github. Don't bother to have a look there yet - there's not really anything to see. But it takes care of the first requirement.
For a completely different project, I wrote a small dependency resolver in python. Coupled with a small command line interface it makes a minimal (<300 line) build system. For a project that isn't "just" building code, this allows a lot more flexibility than things like Make, and because it's python it probably doesn't require people to install anything they don't already have.
There is also also have other non-project code that needs to be written. We need some way to get models and assets into our new engine, and like a complete n00b, I went and modelled all the models already. I also wrote an export script for blender! The great thing about blender is that it is python scriptable, and it is trivial to iterate through the vertices and write an export plugin. So we already have a way of getting all the vertex data that we need.
Below you can see the sprite-sheet with the face outlines in white (and the physics outline of the ship in red). You may notice the weird color-spectrum: those are baked in blur levels that are useful for making a bloom effect in the meshes fragment shader without needing screen-space post processing.