imgui VS nuklear

I find the imgui UIs to be very high density (https://github.com/ocornut/imgui and the gallery issues) See for example the tracy profiler: https://github.com/wolfpld/tracy. It seems the game dev community has pretty powerful tools to understand and interrogate their work.

The user interface has been entirely developed using immediate mode gui dear-imgui library, with the ImGui.NET wrapper. This allows for a fast and bloat free experience but, at the same time, harder customization for a task of this size, since the library isn't really suited to the development of end-user applications. On the other side, it's what I'm most familiar to work with.

I've recently had a lot of fun/success with Dear ImGui (C++) -- not a game engine, but originally/partly meant for use in them. https://github.com/ocornut/imgui

You can manually transform vertices (call ImGui::ShadeVertsTransformPos) this is what angled headers are using https://github.com/ocornut/imgui/issues/6917

Cool project! Graphics programming is _hard_ and anything to make it easier is welcome.

Maybe a dumb question, but why not Imgui (https://github.com/ocornut/imgui). "It's way too big and complex" is a completely reasonable answer, but I found it fantastic for debug menus, and there are a few applications that have used it as their _main_ GUI (Ship of Harkinian as an example).

The most well known immediate mode GUI framework, which egui is also inspired by, is Dear imgui. The egui repository also has a section on the trade offs when it comes to immediate mode GUIs, which I would definitely recommend you check out.

> "Minimize state synchronization."

> void UpdateUI()

Minimize state synchronization by effectively synchronizing state on each screen refresh?

> "Minimize state storage on user side."

> Immediate mode is a style of API where important state is kept in user code

Then reduce state stored in user code by storing "important state" in user code?

> "Minimize setup and maintenance."

I don't find the example convincing. It seems like any more complexity beyond this toy example puts you right back where you started. Building components by hand is stone age ideology regardless of how you push state.

https://github.com/ocornut/imgui/blob/master/examples/exampl...

> "Easy to use to create dynamic UI which are the reflection of a dynamic data set."

Which is great for a video game.

The one big downside I see is that if you want to actually work on the library itself, it's a pain to have to re-compile the entire thing every time you change something.

Nuklear (https://github.com/Immediate-Mode-UI/Nuklear) uses separate files with a deploy script that combines them all into a single header; I think that approach is quicker for iterating on the code.

Nuklear is an alternative Immediate GUI, also written in C.

> And for the right project, especially those where a predefined engine structure does not not fit, it can still be the most productive choice.

Right on. While interning at an oil refinery, I developed an application in LÖVE that processes and displays data from spectrometers. In hindsight it may not have been the wisest choice, but hand rolling all the GUI elements I couldnt force out of the Nuklear[0] bindings for LÖVE gave me a strange sense of satisfaction.

[0]: https://github.com/Immediate-Mode-UI/Nuklear

No, Nuklear has been updated 2 days ago.

I think good option would be nuklear it is a single header lib

For GUI, there are lots, most well-known of course being Dear Imgui, for which people have made auto-generated C bindings. Another mature but a lot simpler option is Nuklear, as others have mentioned. Even more minimalistic (it's just 1KLOC) is microui. There are a lot more, just google "imgui library c".

What about https://github.com/Immediate-Mode-UI/Nuklear ?

Nuklear? They have a number of backends.