Commenting example game, matching up workflow for connections, cloud9 stuff

fist off, i realize i am checking in a bigger chunk of stuff and i apologize, i will try and be more granular with my next commits. i did the classic "didnt check for updates before working" and ended up with a little mess in git. hopefully i am not wrecking too much...

this contains the start of commenting out the example game gode that @gever wrote, and tweaking some things so they follow a more consistent rhythm, like World. add_connection(), which matches World.add_location().

i also changed some variable names in the example game to make it slightly more noob friendly and added some redundant import statements to support the cloud9 IDE better (the editor doesnt seem to parse the '*' import and so kids will see a lot of errors when writing and no autocompletes.

finally, i added a Game() static class (for now) to deal with game-wide functions that i wanted to separate from user code, and make it more obvious that it was in the engine. i can see later needing something like:

```
my_game = Game()
my_game.do_something_game_wide()
```

kind of situation, and so this static class is not ideal.

so please, feel free to hack and slash my hackery, i know it aint pretty ;)