egui

They go into a good amount of detail[1] as to what they mean by "immediate mode" (this is linked from one of the windows when you open the page). [1] https://github.com/emilk/egui#why-immediate-mode

How is this "immediate mode"? I see widgets that are added to a UI using .add() "You should put this widget in a ui with `ui.add(widget);" https://github.com/emilk/egui/blob/master/crates/egui/src/wi... There appears to be a fluent builder API for these widgets. Is that what makes it "immediate mode"?

It's being worked on. Merry Christmas! https://github.com/emilk/egui/issues/3378

Thank you for linking your project—that looks really cool! I saw you also implemented a pan-and-zoom area. We are currently working on moving Rerun's implementation to egui [0], so maybe keep an eye on that. It would be super cool to have layered graph drawing in (Sugiyama-style) in Rerun too. The tricky–but super interesting–challenge that we face is that our layout implementations need to be consistent across timestamps if the underlying structure of the graph changes, which is why we initially chose a force-based layout approach. There, the time-varying aspect is handled naturally by the simulation. The very interactive nature of Rerun also poses more restrictions on the implementation of our algorithms: re-layouts ideally need to be fast, to produce visualizations quickly, especially when scrubbing the timeline. I still hope we can ri

Have been playing with rerun since the early days, and the team has built a ton of amazing features for visualizing your robotics datasets. I used it on a bicyclist safety system to ingest raw data for playback and analysis later. I especially like that they're also building an (amazing) Rust version of imgui called egui, and open sourcing all the work for the ecosystem: https://github.com/emilk/egui

Thanks for the feedback! It is definitely fixable. Take a look at https://github.com/emilk/egui/issues/996 for some examples of how others have styled egui, or try out https://app.rerun.io/ Styling is done with `ctx.set_style`, but creating a nice style isn't very easy at the moment (basically you'll have to tweak constants in code, and then recompile). I'm working on making it easier as we speak though!

The http example at egui.rs uses the `poll_promise` crate to wait for a HTTP request: https://github.com/emilk/egui/blob/master/crates/egui_demo_a...

You can have real separate windows in egui. Either running on the same thread or another. See here: https://github.com/emilk/egui/blob/master/examples/multiple_...

Nothing is wrong with that, it’s rather a workaround, ultimately I am trying to have one language only including the UI too (been playing with egui),so I don’t have to use JavaScript. https://github.com/emilk/egui

FWIW, I opened an issue: https://github.com/emilk/egui/issues/4046

That's fair. I don't have experience with other immediate mode libraries. It's good to hear that it's not an intrinsic limitation https://github.com/emilk/egui?tab=readme-ov-file#layout Here the author discusses the issue directly. They note that there are solutions to the issue, but that they all come with (in their opinion) significant drawbacks. For my use case, if I have to do a lot of manual work to achieve what I consider behavior that should be handled by the framework, then I don't find that compelling and am inclined to use a retained mode implementation.

https://github.com/emilk/egui#cpu-usage Fantastic - “only” 1 to 2 ms (and that’s for simple stuff). Depending on what you’re doing that’s a big chunk. Also time you could be sleeping. Also something you don’t usually have to worry about.

Here's an IMGUI library that's also accessible (via AccessKit): https://github.com/emilk/egui