stretch VS backroll-rs

The most common is flexbox (an attempt to a cross-platform engine at https://github.com/vislyhq/stretch).

There's a few critical subtasks here: - determine the data flow model we'd like to use for our UI. We'd like to integrate tightly into the ECS, but need to figure out how to reduce the boilerplate and improve reliability around working with hierarchies. - swap our layout library. Our current dependency stretch implements the flexbox algorithm, but is unmaintained and has critical bugs :( The three main options here are to fork flex, move to the new morphorm crate, or write a layout library from scratch - consider rearchitecting our UI to be more flexible and compositional: splitting the massive Style component into several parts and moving to a "UI is a collection of behaviors" paradigm - build out more widgets! - more docs and examples!

That would probably entail integration with bevy, or some other game engine to get the UI drawn. Our TUI crate uses https://github.com/vislyhq/stretch/ to lay out the elements, so I imagine you could use that but just draw with WGPU.

Are there any plans to make yoga fully conformant to the web implementation of flexbox? For example, migrating to use stretch instead?

https://github.com/vislyhq/stretch exists, I don’t know how well it would do at all this.

I'll share two other options, of course with numerous caveats on each: - https://github.com/HouraiTeahouse/backroll-rs Looks great for low-latency games - https://partner.steamgames.com/doc/features/multiplayer Steam can be used on non-Steam platforms too, and has official-ish rust bindings but haven't tried this route

I haven't actually got to the point of trying to implement it in my fighting game engine but Backroll rs is a rust implementation of GGPO https://github.com/HouraiTeahouse/backroll-rs

Backroll-rs is a brand new networking library based on GGPO dedicated to peer-to-peer Rollback Netcode, for use in fighting games, platform fighters, and other games with less than 8 players that require low latency. We are looking for programmers familiar with Rust to help finish this project. We are 80% of the way completed with this project, but we need more unit tests and debugging to fully finish it.