inox2d VS glium

I'm writing Inox2D, which is kind of a rewrite of Inochi2D in Rust. The aim is to reach more use-cases such as web with WASM and even potentially embedded development, but at the very least an implementation in a low-level non-garbage-collected language.

Inox2D, an experimental native Rust implementation of Inochi2D.

inox2d - official experimental reimplementation of Inochi2D, an open-source alternative of Live2D for animating 2D puppets in various contexts such as games or vtubing. inox2d isn't really meant to be a replacement over the current implementation, but more of a complementary one that extends it's use-cases, for example embedded devices and web integration with WASM.

Hey, I'm working on inox2d which uses glow.

For example, I wouldn't want to separate this into multiple files, would make it harder to see where all the deserialization logic is.

For example, I'm working on Inox2D, a reimplementation of Inochi2D in Rust.

I absolutely get that. It was actually very clear in a project of mine. I work on inox2d which is a native implementation of Inochi2D in Rust (Inochi2D being a FOSS puppet animation system, like Live2D which is used by vtubers and light novel engines notably).

For example, on my Inox2D project, I was using serde to deserialize some JSON payload. But that came with some hacks I had to do, like have a temporary struct that gets converted to the final one because it wasn't possible to serialize it by itself, and add extra-dependencies to make the system extensible while also supporting external structures I used like Arena from the indextree crate.

You can find it at https://github.com/Inochi2D/inox2d. If you know stuff about OpenGL and low-level rendering in general I'd really appreciate some help as I myself am very new to this stuff.

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.