allsorts VS glium

But again you don't need to reinvent text layout from scratch (that's my discussion, BTW) if you use the platform's native text drawing facilities, like DirectWrite on Windows, or CoreText on macOS.

All these layers of Cows create an extremely complex lifetime tree and it's actually not possible to factor out the complex parsing steps into functions because they depend on a lot of stuff. (trying to return an OutlineBuilder from a function would dangling reference about 3 different temporaries, for example. Obtaining the temporaries is part of the parsing step)

machine learning, neural networks, image processing, cryptography (though it is getting better), font shaping/rendering (though it is getting better), CPU/software rendering (though it is getting better)

It can be used for the things you suggest but our driving use case is font parsing. The goal is to use it to generate the font parsing code in Allsorts, which is ultimately used in Prince.

Use allsorts or rustbuzz for text shaping

Loader -> Allsorts

It's something I'd like to improve on in future -- are there any pure-Rust libraries you'd recommend for shaping? Allsorts looks quite promising.

I am trying to follow to this tutorial on glium and I can't even get a window to show up because of what I assume to be a lack of comprehension on my end about how dependencies work.

Which is blocked, waiting for glium to update: https://github.com/glium/glium/pull/2036

https://crates.io/crates/glium (8 months ago - 925 kB)

The book is a great place to look at https://github.com/glium/glium/tree/master/book And glium itself is a bit outdated might be good to look at alternatives like glow

Hi rustaceans! I glued this prototype together with vtkio and glium. There are more features that are unsupported than supported at this point, but the code is here if you want to check it out: https://github.com/JeffIrwin/skillet

https://github.com/glium/glium/issues/941 is the relevant Glium bug/feature request. Long story short, structs as uniforms aren't supported by Glium's current design, it looks like.

Should i learn glium (https://crates.io/crates/glium)? i have some experience in opengl (C++) and i would like to use the opengl functionality in the Rust ecosystem.

I can recommend https://github.com/glium/glium as a good, safe abstraction. There was a time when I wanted to learn shaders and write complex pipelines with several stages, this library allowed me to learn about the important objects and their responsibilities without having to program the very verbose chunks of code to initialize. I learned the following:

Glium is a Rust-y OpenGL wrapper, and its repository contains a discussion that should give you an idea whether this is what you want to use, as well as some tutorial.

With a gluim window open, I want to count the number of user clicks and retain the number after the window is closed. In order to keep the program running after the window is closed, I had to change event_loop.run to event_loop.run_return and I think that means all variables will be moved into the closure and my counter goes out of scope.