Extremely-high-level bindings for gui system

[CyberVenlor]

Currently, there’s a lack of high-level Rust bindings for GUI development, and I’m working on a project to recreate a Sans fight on the Flipper Zero. Given the Flipper Zero’s limited SRAM, I’ve been exploring how concepts from the Bevy engine (especially ECS—Entity Component System) can be adapted for a lightweight GUI system on this device.

SCHEME(not sure)
1. Complete the current GUI mod.
2. Implement ECS-like features to efficiently manage GUI components within tight memory constraints.
3. Add basic physics components, which could open doors for more interactive and dynamic interfaces or games.

I wish you may share some ideas
😺

[dcoles]

Hi @CyberVenlor! That's an awesome idea. I'd love to see how that would play out on the Flipper Zero with the D-pad.

@JarvisCraft has been working on exposing some high-level bindings for the GUI in #29, though the PR has stalled a little.

I'd also suggest taking a look at the embedded-graphics and the approach they take for implementing graphics on constrained devices. I could certainly see us providing an implementation of the DrawTarget trait in the flipperzero crate so it's easy to make use of the embedded-graphics ecosystem.

I'm not aware of any embedded focused ECS systems, but there seems to be a couple with no_std support (e.g. shipyard, edict) and it looks like there's also an effort to add no_std support throughout Bevy which seems to be making excellent progress.

I've not dug deeply into any of these crates (besides bevy_ecs for some non-embedded work), but might serve as a good starting point.