JoelOtter on master
Update Readme.md to include Go … (compare)
Channels would work internally, and making the channel public in case someone needs it may also make sense.
In general, though, does it ever make sense for there to be more than one Game type in existence? If not, a singleton pattern might work, making Game available as a package-level variable in that NewGame() is still necessary to initialize things, but termloop.Game() gives you the singleton from anywhere, which would also allow you to easily call game.Quit() from anywhere easily as well.
Not too familiar with the internals of your package yet though, so let me know if something I'm suggesting wouldn't make sense.
Hello everybody! I'm a noobie to golang and I decided to start making a minigame with termloop using pixelmode. This engine is truly awesome. This is the link in case you want to check it.
I had some issues dealing with terminal colors in Windows, so I looked for the best colors through "trial and error", and I make the game load different assets in runtime depending in OS (it would be so great if you know a better solution). I also edit a pair of lines in
image.go in order to load images from memory rather than a files as I used go-bindata in order to embed assets. However, I think that my implementation is not very portable and that there must be a better built-in alternative.
So, that's it. Any comment is welcome. Hope you like it :)