nuklear VS raygui

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.

About the UI interface, I created raygui a simple immediate-mode UI library, you can also take a look: https://github.com/raysan5/raygui

git submodule add https://github.com/raysan5/raygui.git vendor/raygui

Added splicit type casting in commit: https://github.com/raysan5/raygui/commit/78ad65365ebae6433f60cf03a09e76b43c46cfa2

Yes you can use raygui as a standalone library without raylib. Read for more info: https://github.com/raysan5/raygui/blob/master/src/raygui.h.

Possibly with https://github.com/raysan5/raygui.

For your example of raygui, you can just look. It's a single header file (but does require raylib) to work.

I'm under the impression that Unity builds have a good deal of overhead. Plus, in many cases, something like raygui (C# bindings) will actually be quicker to develop with. Nothing wrong with Unity, though. The best tool is the one you know how to use, in my opinion.

raylib extra libraries cleanup: raylib has been on diet and all the extra libraries included on previous releases have been removed from raylib. Now raylib only includes the original 7 raylib modules: rcore, rlgl, rshapes, rtextures, rtext, rmodels and raudio. But no worries, extra libraries have not been deleted, they have been moved to their own repos for better maintainability and more focus on its functionality. The libraries moved out from raylib repo are: raygui, physac, rmem, reasings and raudio (standalone mode). On that same line, a new amazing GitHub group: raylib-extras has been created by @JeffM2501 to contain raylib extra libraries as well as other raylib add-ons provided by the community. Jeff has done an amazing work on that line, providing multiple libraries and examples for raylib, like custom first-person and third person camera systems, Dear ImGui raylib integration, multiple specific examples and even a complete RPG Game Example! Great work Jeff! :D

You might also want to take a look at raygui