Also:
* Move stuff around to a builtin/ folder
* Separate out classes to follow my one-class-per-file convention
* Samples are renamed to the underscore convention
I just like the word "sprue", and it's more descriptive than our original choice of "template". If I had to start Squib all over again, I would probably name it "Sprue" :P
So the idea behind this is maintain an "expected value" for the sample runs. We store the graphics calls and their arguments as a readable text file. Any change in the samples will break this, but the idea is to make sure this doesn't get broken unexpectedly.
Rearranged the data files in specs