Consider using piston-window

[kvark]

https://github.com/PistonDevelopers/window

It's a new window abstraction that is compatible with gfx::Canvas. Transitioning to it would unlock the path to dev_menu in #27

cc @bvssvni

[bvssvni]

There are many ways to plug into the Piston ecosystem:

• Depend directly on "window" and poll the events from the window and handle your own update/render
• Use it in combination with the "event" crate which adds .events() to get a game loop
• Use "piston" crate which reexports "window" and "event"
• Use the "piston_window" crate
• Implement event::GenericEvent for a wrapper around the input structure you are using

GenericEvent is designed in a such way that it possible to use it with any structure. The input structure in Piston is merely for convenience. Suggestions for making this even better are welcome.

[bvssvni]

I was thinking about for a moment of moving GenericEvent to its own library to make it easier to use the Piston libraries, but realized it would not be usable without the event traits and the input library.

[kvark]

@bvssvni thanks for the info! I like the composability of the libraries in Piston ecosystem. I believe piston/window fits in there quite nicely.