So now I'm auditing and documenting. Each function, global and struct is going to get identified and tucked away. I'm trying not to suffer from "Analysis Paralysis" but I want an opportunity to look at each function and figure out what each does and where it fits. I have the maps to do so, now I's just a matter of writing a header and jotting down parameters and returns. (I have a handy code snippet that I wrote in XML to help)
As the documentation was getting a little repetitious, I spent the other half of my day drawing up a few graphical prototypes. The question I had was this: How do I maintain the graphic look of ROE, but move it away from the LCARS Star Trek-ish interface. You can argue that the garish 16 color interface isn't exactly Star Trek, but I wanted to try some prototypes anyway.
|Click to Embiggen|
Speaking if rendering. I may turn the title sequence into an 3D FMV. I may experiment with that later, as long as it doesn't detract from my coding too much.