moxie VS stretch

I think https://moxie.rs/ as well

That's the idea of azul and moxie-native: they use web technologies but are way lighter than embedding a browser.

There are various ways you might do an implicit context objects. An example is the illicit crate, from moxie.

Rather than using a macro based DSL, it uses plain rust syntax with a builder pattern inspired by Moxie. It's inspired by Solidjs and Maple on the signals/reactivity side.

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.