Andy Meneely
0d076b1e85
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
29 lines
683 B
Ruby
Executable File
29 lines
683 B
Ruby
Executable File
#!/usr/bin/env ruby
|
|
require 'squib'
|
|
require 'mercenary'
|
|
|
|
Mercenary.program(:squib) do |p|
|
|
p.version Squib::VERSION
|
|
p.description 'A Ruby DSL for prototyping card games'
|
|
p.syntax 'squib <subcommand> [options]'
|
|
|
|
p.command(:new) do |c|
|
|
c.syntax 'new PATH'
|
|
c.description 'Creates a new Squib project scaffolding in PATH. Must be a new directory or already empty.'
|
|
|
|
c.action do |args, options|
|
|
Squib::Commands::New.new.process(args)
|
|
end
|
|
end
|
|
|
|
p.command(:make_sprue) do |c|
|
|
c.syntax 'make_sprue'
|
|
c.description 'Creates a sprue definition file.'
|
|
|
|
c.action do |args, options|
|
|
Squib::Commands::MakeSprue.new.process(args)
|
|
end
|
|
end
|
|
|
|
end
|