code walkthrough and cleanup

[payload]

• learn where is what and how is stuff connected
• clean stuff which hurts eyes
• make things clear and short. the flow of code and data should be easy to understand

[payload]

• Naubino.coffee and related files ( :D ) contains initialization code
• Naubino is also the global namespace
• depends on html and all other files depend on Naubino

[payload]

• dependancy analysis: coffee$ grep -o 'Naubino\.[^. ]\+' *

[payload]

• main configures Naubino: wires events and states, defines callbacks and mostly sets active games (dependency on *Game)
• Naubino does never depend on a concrete Game :-)
• Games may depend on Naubino, cause they need access to canvases, signals and stuff like that (we could start here an globals vs singletons vs dependency injections debate... but i did now a singleton and trust in grep and sed)