Beginning work on Game Builder module

For now, game builder can just create the
proper subdirectory and content.json file.
Going to iterate on this throughout the
week and hopefully make the 8/15 deadline.
Renamed builder.py to player.py

Just sounds better.
Gotta link these API docs...
Updated documentation

Should consider investing in some documentation
consistency tool or framework...
Fixed the formatting in the API doc
Update Otrera-API.md

Github asciidocs, lol
Fixed broken test.

Also made some 'for' loops a bit more Pythonic
Added engine_builder stub

Not ready to actually code this, just leaving
a placeholder.
Shuffling things around for packaging

This commit does a few small things that push
Otrera toward proper Python packaging.

1. Adds a placeholder yaml. That will be used for
configuring things like where engine and game
data will be saved on the user's box.

2. Moves all the Python code to the top level
'otrera' directory.

3. Makes content.py a bit smarter. It will still
default to the default engine and content.json, but
it can take in paths for specific engines and games.

4. Deleted template.py. Pretty sure that's no longer
used.

It's so nice having an integration test to make sure
things work!
Creating otrera executable

First pass. Don't have much experience. Will
need to add flags and support both multiple
content adding paradigms (interactive vs.
single commands). This commit puts a foot
in the door.
Updating engine_builder stub

Just don't want to forget a good idea about
world and scenario constructs
Completed first iteration of Game Builder

This includes an update to the otrera
executable. Pretty happy with this commit
overall. You can create a new game and then
add content to it.

I need to update the editContent module and
then add some kind of test. Going to need a
few commits to really polish the CLI.
Updated editContent to work with executable

Otrera can now add and edit content comfortably.
We're making progress
TODO update
Added template for engine_builder

Engine Builder can now create a placeholder
file for new engines. It also creates needed
subdirectories and works with the otrera
executable.
New version of engine.json based on new schema

This isn't ready for primetime, but it is a start.
The new_engine.json is a concrete example of the
Construct --> Scheme --> Content approach I worked
out in the API Google Doc. It is a messy cut/paste
job that needs cleanup and testing but it's a start.
Updated engine.py and tests

Everything now works with the new engine.json.
This is a proof of concept commit. If I stick
with this structure for engine files, I will
need to make a number of improvements to
engine.py. More precisely, engine.py will
have to be smart enough to know how to make
a character without knowing which Schemes
to expect in the engine.json file.
Merge branch 'structure' of github.com:AgathaTheWitch/Otrera into structure