You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating a robust and compelling user interface in Rust/Bevy is non-trivial. Bevy provides an in-house UI implementation, but it's too barebones and exceptionally verbose. There is no plug-and-play component framework natively provided by Bevy at this time.
Originally, I ignored my concerns and attempted to implement a UI using Bevy's tooling. This proved exceptionally time consuming and the cost/benefit trade-off was abysmal. It was several hundred lines of code to create the most trivially styled dialog.
In response to this, I abandoned Bevy's UI implementation and searched for alternatives. The most immediately promising solution was to use egui + bevy_egui to integrate the two frameworks. egui is currently responsible for creating the menus seen within the app.
Numerous high-level questions still linger, though:
egui does not scale with zoom in/out of the world map. Should it?
egui UI appears too small on mobile devices. How to elegantly resolve?
what does a "good" ui look like for Underground View? when will that be created?
how to create a mobile/responsive UI using egui? how high should this be prioritized?
is it worth considering alternatives such as Belly or Kayak? Why?
Additionally, there are low-level implementation questions:
How to completely reset an egui window position on game restart?
The text was updated successfully, but these errors were encountered:
Creating a robust and compelling user interface in Rust/Bevy is non-trivial. Bevy provides an in-house UI implementation, but it's too barebones and exceptionally verbose. There is no plug-and-play component framework natively provided by Bevy at this time.
Originally, I ignored my concerns and attempted to implement a UI using Bevy's tooling. This proved exceptionally time consuming and the cost/benefit trade-off was abysmal. It was several hundred lines of code to create the most trivially styled dialog.
In response to this, I abandoned Bevy's UI implementation and searched for alternatives. The most immediately promising solution was to use egui + bevy_egui to integrate the two frameworks. egui is currently responsible for creating the menus seen within the app.
Numerous high-level questions still linger, though:
Additionally, there are low-level implementation questions:
The text was updated successfully, but these errors were encountered: