Another fix - can't believe I missed that.
parent
9f83beea3a
commit
350314f2a8
|
|
@ -1,5 +1,5 @@
|
||||||
# Squib [](https://rubygems.org/gems/squib) [](https://travis-ci.org/andymeneely/squib) [](https://gemnasium.com/andymeneely/squib) [](https://coveralls.io/r/andymeneely/squib) [](http://inch-ci.org/github/andymeneely/squib)
|
# Squib [](https://rubygems.org/gems/squib) [](https://travis-ci.org/andymeneely/squib) [](https://gemnasium.com/andymeneely/squib) [](https://coveralls.io/r/andymeneely/squib) [](http://inch-ci.org/github/andymeneely/squib)
|
||||||
Squib is a Ruby [DSL](http://en.wikipedia.org/wiki/Domain-specific_language) for prototyping card and board games. With Squib, you just write a little bit of Ruby and you can compile your game's data and images into a series of images raedy for print-and-play or even print-on-demand. Squib is very data-driven - think of it like [nanDeck](http://www.nand.it/nandeck/) done "the Ruby way". Squib supports:
|
Squib is a Ruby [DSL](http://en.wikipedia.org/wiki/Domain-specific_language) for prototyping card and board games. With Squib, you just write a little bit of Ruby and you can compile your game's data and images into a series of images ready for print-and-play or even print-on-demand. Squib is very data-driven - think of it like [nanDeck](http://www.nand.it/nandeck/) done "the Ruby way". Squib supports:
|
||||||
|
|
||||||
* A concise set of rules for laying out your cards
|
* A concise set of rules for laying out your cards
|
||||||
* Loading PNGs and SVGs using [Cairo](http://cairographics.org/)
|
* Loading PNGs and SVGs using [Cairo](http://cairographics.org/)
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue