Random questions about the library

[kvark]

1. Why is the package named piston-gfx_texture, while the widely popular image is just named image? Do you have any guidelines on these names? I don't mind either way, just prefer consistency.
2. What's the point of having a single source file named texture.rs if the project is gfx_texture? Why not just put the logic into lib.rs if it's so small?
3. Why returning a struct (Texture) that has only gfx::TextureHandle instead of just returning the handle directly?
4. Why is the error (for from_path) returned as String? I believe you should have proper enums for errors, no unwrap() calls in the body, and Display with Debug implemented for the errors.

[bvssvni]

1. I think my line of reasoning was that 2D libraries were prefixed piston2d and 3D libraries piston3d, and since gfx_texture was used for both I used just piston. See Reserve names on crates.io piston#768
2. gfx_texture partly comes from Hematite, which had a source texture.rs. Historical accident.
3. To work with piston-graphics, the Texture object needs to implement the ImageSize trait.
4. This should be fixed.

[kvark]

Thanks! One more thing:

(5). Why aren't texture loaded with mipmaps? This is probably the most common use case, so while a configurable option is preferred, doing mipmaps by default is most desired.

[bvssvni]

@kvark That might be a good idea. Will open an issue.