ImGui.NET VS imgui

Now I'm trying to integrate ImGui into the engine. One solution I found was using this but as far as I can tell it locks you into using OpenGL which is something I would like to avoid as one of the main selling points of SDL2 for me is it's abstraction over the rendering backend.

In additiona to imgui wrapper which works great with NativeAOT, only slight nudge and you have 10Mb executable. With all deps it's 13Mb. Also there Avalonia mentioned in sibling message which work great and in 11.0-preview5 probably would not need any additional configuraiton. In case if OP is have soft spot for web tech, he can use photino.Blazor which also with slight modifications would simply works and produce 27Mb executable.

Imgui gets rendered using ImguiRenderer provided here in the example: https://github.com/mellinoe/ImGui.NET/tree/master/src/ImGui.NET.SampleProgram.XNA

I'm converting rlImGui from C++ to C# so I can use it with ImGui.NET and Raylib-cs but I'm getting stuck at a couple places. I don't know how to convert line 331 to C# since in ImGui.NET cmd.UserCallback is an IntPtr and not something I can call. I did a quick google search and you can use the Marshal library to convert it to a callable delegate but I think you need to also have the delegate known to do that. There's also line 82 but that is specific to Raylib. The function it calls does not seem to be included in Raylib-cs. Also, rlImGui keeps using a Texture type but that is not defined in Raylib-cs or ImGui.NET. I assume I can substitute it with Texture2D from Raylib-cs but I'm not to the point in porting to see if Texture2D has the necessary fields/properties/methods.

ImGui.NET 1.87.3 (using the example implementation)

If you use this example implementation for XNA/MonoGame, you can just use ImGuiRenderer.BindTexture() which returns an IntPtr.

The only thing I could really think of is something like ImGui for C# (https://github.com/mellinoe/ImGui.NET) but I've never used it. It's going to give you some simple wrappers around ImGui (https://github.com/ocornut/imgui) but even this is going to lock you into the UI framework -- you can't just "draw a rectangle" per se and use it as a "control." Do note however this is an "immediate mode" GUI which is different from how most general desktop windowing systems work in "retained mode" (which are typically event driven, which saves on computing power to not draw the same stuff over and over).

include(cmake/CPM.cmake) function(raylib_imgui_setup_dependencies) message(STATUS "Include Dear ImGui") FetchContent_Declare( ImGui GIT_REPOSITORY https://github.com/ocornut/imgui GIT_TAG 277ae93c41314ba5f4c7444f37c4319cdf07e8cf) # v1.90.4 FetchContent_MakeAvailable(ImGui) FetchContent_GetProperties(ImGui SOURCE_DIR IMGUI_DIR) add_library( imgui STATIC ${imgui_SOURCE_DIR}/imgui.cpp ${imgui_SOURCE_DIR}/imgui_draw.cpp ${imgui_SOURCE_DIR}/imgui_widgets.cpp ${imgui_SOURCE_DIR}/imgui_tables.cpp) target_include_directories(imgui INTERFACE ${imgui_SOURCE_DIR}) include(cmake/CPM.cmake) message(STATUS "Include dbg-macro") cpmaddpackage( "gh:sharkdp/dbg-macro#fb9976f410f8b29105818b20278cd0be0e853fe8" )# v0.5.1 message(STATUS "Include fmtlib") cpmaddpackage("gh:fmtlib/fmt#e69e5f977d458f2650bb346dadf2ad30c5320281" )# 10.x message(STATUS "Include raylib") cpmaddpackage("gh:raysan5/raylib#ae50bfa2cc569c0f8d5bc4315d39db64005b1b0" )# v5.0 message(STATUS "Include spdlog") cpmaddpackage("gh:gabime/spdlog#7c02e204c92545f869e2f04edaab1f19fe8b19fd" )# v1.13.0 message(STATUS "Include rlImGui") FetchContent_Declare( rlImGui GIT_REPOSITORY https://github.com/raylib-extras/rlImGui GIT_TAG d765c1ef3d37cf939f88aaa272a59a2713d654c9) FetchContent_MakeAvailable(rlImGui) FetchContent_GetProperties(rlImGui SOURCE_DIR RLIMGUI_DIR) add_library(rlimgui STATIC ${rlimgui_SOURCE_DIR}/rlImgui.cpp) target_link_libraries(rlimgui PRIVATE imgui raylib) target_include_directories(rlimgui INTERFACE ${rlimgui_SOURCE_DIR}) endfunction()

Immediate mode is a fuzzy concept, as witnessed by this writeup: https://github.com/ocornut/imgui/wiki/About-the-IMGUI-paradi...

It's fun to see the evolution in e.g. these examples of image loading for Dear Imgui:

https://github.com/ocornut/imgui/wiki/Image-Loading-and-Disp...

DirectX9 will even load the image for you, DirectX11 okay we get a few more structures to fill out, DirectX12 is where it goes off the rails and we are filling out a bunch of UNKNOWN DONT_CARE JUST_DO_IT. Then of course Vulkan is the one that gets the big fat "this probably won't actually work for you" warning.

I understand whats happening, but you know sometimes I just want to display a fucking image.

ImGui is engine/GPU agnostic

Themeing isn't a just a retained mode thing, you can do wonders with immediate UIs, even thought (dear)ImGui doesn't provide much, you can still do wonders: https://github.com/ocornut/imgui/issues/707#issuecomment-362...

More on that topic: https://www.youtube.com/watch?v=Z1qyvQsjK5Y

Bonus: If you want to make desktop app with UI, then this is another great C++ library and it's also simple to learn as well. https://github.com/ocornut/imgui.

AFAIK the Rust equivalent to C++'s Dear ImGui is egui.

They use a Dear ImGui, a C++ GUI library.