bevy_dioxus
bevy_dioxus copied to clipboard
JMS55
Open questions: * Should we rename the dioxus #[component] macro to #[widget] or something? * What parts of dioxus do we want to re-export?
UI components should be able to listen for ECS events, and re-render the component when an event is received.
Take inspiration from https://www.framer.com/motion and https://motion.dev
Users should be able to change the cursor styles on hover, click, etc. Both custom images, and platform-specific cursor states.
Composing UI, especially reactive UI, as code is good. But for some types of games, it would be nice to generate static UI visually in the editor. Open questions: 1....
Wrapper over bevy_ui::Style so that we can use strong types and implement dioxus's IntoAttributeValue (do we also want to support stringly typed as well?)
Widgets
Widgets should be "headless", meaning they should handle state and accessibility, but not styling. See also https://headlessui.com. ### Basics - [x] Node - [x] Text - [ ] Button -...
Components must implement Reflect and Clone
Rather than re-rendering every single frame, it would be nice to use something like checking for changes at the archetype level https://github.com/bevyengine/bevy/issues/5097