ocornut/imgui

I finally dipped into using ImHex when doing some reversing of the PS2 memory card format for https://ps2iodb.com . The program is so good, and has enough of a reputation that I knew to reach for it even though I know nothing about reversing, and that was 3-4 years ago now! Also shoutout to the awesome GUI library is uses; https://github.com/ocornut/imgui

No. As much as I would like it to be the case, that is most certainly a poor criteria to evaluate a UI library. Dear ImGui [0] is without a doubt the most prevalent immediate mode UI library. It does not have native accessibility features, but that hasn't stopped companies such as Intel, Meta, IKEA and Google from shipping products built upon it. It's also used in a ton of games. Calling Dear ImGui a toy project at this point would be like calling Unreal Engine a toy project. It's a shame accessibility support is not more widespread, and furthermore it's a shame that it is so laborious to add it. 0: https://github.com/ocornut/imgui/

I've been vibe coding some music tools and after some researching let Claude get going with imgui ( https://github.com/ocornut/imgui ) to build a tool I use for local authoring. It's pretty pixel-dense and looks alright to me. It runs on MacOS and Linux, which is enough for my needs now. Claude has been pretty decent at getting audio stuff going on MacOS and can even tap into various accelerators in MacOS libraries. It's had no problems loading and playing mp3s and m4as, which is the majority of my collection. I'll probably prototype an music manager off of that. It'd be great if it works out for Android as well.

Agreed. This is exactly what I want, ideally with components and libraries and panels and data shareable and extendable between applications. The closest in spirit is Probably something like Dear ImGui[0] and the ecosystem of components and apps built with it, but it's not quite there for me. Something is missing. [0] https://github.com/ocornut/imgui

re, iteration: Have you encountered ImGui [0]? It's basically standard when prototyping any sort of graphical application. re, GUIs in statically typed languages: As you might expect, folks typically use a library. See Unreal Engine, raylib, godot, qt, etc. Sans that, any sort of 2D graphics library can get the job done with a little work. You might also take a look at SwiftUI if you have an Apple device. [0]: https://github.com/ocornut/imgui

…se in game engine editor tooling (not very style-able, simple layout algorithms and assumption that they're running in a 60FPS loop), but they're still a good place to look at, to get a general idea. The most famous library is Dear ImGui [1] The biggest advantage of the immediate mode approach is that you get UI/state syncing for free without having to manage any callbacks/getters/setters/magic properties. It introduces new problems (widgets are now defined implicitly and you need a system for keeping track of them over time), but they're way easier to solve than the UI/state sync issue. Examples of real-non-video-game software that uses it are File Pilot [2] and RAD Debugger [3], which ar…

…text to figure out data dependencies and data formats), and that would be the "interesting" part to solve - e.g. how to tunnel richer debug information from the programming language to the debugger. Also there's a middle ground of directly adding a realtime runtime debugging UI to applications via something like Dear Imgui ( https://github.com/ocornut/imgui/ ) which is at least extremely popular in game development - and in this case it's trivial to provide the additional context since you basically develop the debugging UI alongside the application.