Release new version to crates.io

[milibopp]

The current 0.0.3 does not work with Rust 1.0. Could you release a 0.0.4?

[mitchmindtree]

Sure @aepsil0n , the problem has been that for a long time many of the gfx and piston crates would remain far behind their up-to-date git counterparts and it became far too time consuming trying to keep everything up to date in order to publish (as you probably know you can't publish new versions with git dependencies). It seems that a greater effort is going in upstream to stay up to date on crates.io lately, so I'm fine with having another go at it :)

Also, I'll make more of an effort to branch and merge via PRs for elmesque rather than pushing straight to master now that a few people seem to be using it.

I've given you merge access to the repo and I've added aepsil0n as an owner for the elmesque crate on crates.io in case you need something like this again when I'm not around :+1:

btw, the github version is 0.1.0 at the moment (quite far ahead). I'll have a go at getting the new crates.io version up within the next few hours.

[mitchmindtree]

So the biggest issue I'm running into is that many of the piston dependencies use almost exclusively git dependencies. Fortunately though, this is only the case for the dev-dependencies (for the graphics example). Perhaps we can either:

• Change the example to not use any piston deps (perhaps exclusively glutin and gfx?). This might be tricky as elmesque currently depends on piston2d-graphics for rendering Elements and Forms.
• Remove the example (maybe move it into some other repo).

[mitchmindtree]

Another issue I'm running into is changing the piston2d-graphics dependency from git to crates.io. The change causes compatibility issues with each of the piston2d-graphics backends (i.e. gfx_graphics, opengl_graphics, etc) which all depend on the git version. This problem isn't immediately obvious in the elmesque crate, but shows itself quickly in crates like conrod that depend on elmesque.

[milibopp]

Thanks for the quick feedback. Yeah, piston has been bugging me in this regard as well. I presume the reason behind Piston's usage of git deps was the rapid pace of breaking changes in the compiler a while ago. The issues you are running into should be reported upstream, I think.

[milibopp]

btw, at least the Glium backend is available on crates.io.