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 |
||
|---|---|---|
| .. | ||
| _output | ||
| autoscale_font | ||
| backend | ||
| build_groups | ||
| colors | ||
| config | ||
| data | ||
| images | ||
| intro | ||
| layouts | ||
| project | ||
| proofs | ||
| ranges | ||
| saves | ||
| shapes | ||
| sprues | ||
| text | ||
| units | ||
| README.md | ||
| basic.rb | ||
| hello_world.rb | ||
| shiny-purse.png | ||
| spanner.svg | ||
README.md
Squib Samples
In here we have a massive library of Squib samples. We try to exercise as many options as possible here as these samples also serve as Squib's regression test suite.
If you have one to contribute, file an issue!
What's with the underscores?
Normally you don't start a filename with an underscore (e.g. _text.rb), but to make it easier to find the code itself on GitHub, we've renamed the files so they sort to the top of the list.