glium_text_rusttype
glium_text_rusttype copied to clipboard
not-fl3
Are you still maintaining this?
I am back here :)
Not going to actively work on this in the near future, but will be there for PRs and issues. I see your PR, its great, if it will help you - I could add you to crates.io owners etc, just let me know :)
I don't really need to be a maintainer if you are still ok maintaining this. I would just appreciate it if you made tags for releases and in fact made a release for my recent changes.
Also you should throw this up on travis and activate weekly autobuilds just to check whether things keep working.
Published your changes to crates.io. Will keep this issue opened until I manage to set up travis.
Nice stuff, appreciate it.
On Fri, Sep 28, 2018 at 10:34 AM Fedor Logachev [email protected] wrote:
Published your changes to crates.io. Will keep this issue opened until I manage to set up travis.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/not-fl3/glium_text_rusttype/issues/13#issuecomment-425363918, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAGgJjbHI4U3T4RHrAlbU_Z2LI5GwNRks5ufd8RgaJpZM4WbX8h .
@not-fl3 Could you please update deps, e.g. glium to 0.28? :)
Btw, the table is broken in the docs: https://docs.rs/glium_text_rusttype/0.3.3/glium_text_rusttype/
And Rust supports inclusive ranges now:
As of now, Rust doesn't provide a way to create inclusive ranges yet so thou shall add +1 to the outer bound.
Not really, I moved from glium to miniquad https://github.com/not-fl3/glium_text_rusttype/pull/17#issuecomment-622983702 and not using this anymore.
I can merge pull requests etc, but if someone wants to properly maintain - would be happy to give write access/transfer crate rights or whatever is needed :)
Sent PR #18 to bump the glium version, as it's broken past glium 0.26 at the moment. Happy to help out herding PRs/releases through if you like, since I'm making use of this crate.
