imgui VS wxWidgets

Extensibility - Can I hook into the runtime's? Load native binaries? Inject C++ or Rust where it matters? That’s how I built imgui.js, a threaded and sparse set powered C++ GUI framework over dear imgui for Node:

Yes, "immediate" refers just to the API. Source: [1]

[1]: https://github.com/ocornut/imgui/wiki/About-the-IMGUI-paradi...

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

For more detailed insights, see the comprehensive Original Article and explore authoritative sources like Open Source Initiative and the Official wxWidgets Project.

The wxWidgets License stands as a testament to the open source community’s commitment to fairness and innovation. Its design facilitates smooth collaboration across borders and industries while offering developers the legal clarity needed to protect their contributions. The comprehensive review charted the license’s historical evolution, outlined its major strengths—including flexibility, transparency, and robust community engagement—and highlighted areas that require vigilance, such as potential exploitation in commercial contexts. For developers and project managers seeking an in-depth understanding of open source licensing, the detailed analysis presented in the original article (Unveiling wxWidgets License: A Comprehensive Summary, Exploration and Review) is a must-read. In the broader context of open source initiatives, where choices like the MIT License and other industry standards compete for attention, the wxWidgets License offers a well-rounded, community-focused alternative. In conclusion, the wxWidgets License reinforces the importance of a balanced legal framework designed to support innovation and fair compensation. As the technology landscape evolves, continual dialogue and legal revisions will be essential to maintain its relevance. For detailed explorations of licensing models and additional expert insights, check out related resources on wxWidgets and further reading on open source projects at Open Source Initiative. Happy coding, and may your projects thrive under licenses that value both freedom and fairness!

The Elixir programming language is no stranger to desktop applications as the language actually supports building them out of the box. It uses wxWidgets: a C++ library that lets developers create applications for Windows, macOS, Linux and other platforms with a single code base. But wxWidgets has a very complex API, and doesn’t solve issues that usually come with desktop applications around packaging.

Qt is also 100% open/free. In fact, both are available under the LGPL, just that wxWidgets also grants an exception to not have to distribute application sources even when statically linked:

https://github.com/wxWidgets/wxWidgets#licence

But for big programs, ones written in C++? Good luck it won’t be easy at all. You might try wxwidgets or qt. I do not predict trying to click box-ify complex cli tools yielding much success.

In theory, you should be able to use FFI to interface with something like wxWindows, but you might again have problems on macOS, I don't know. And to me eyes, Wx looks a bit outdated.

This seems to be like the classic wxWidgets [1], i.e. it's an API that wraps the underlying platform's default toolkit. So on Windows it uses Windows' native controls, in Linux it seems to use GTK, and so on.

That means that the advantage is being able to write against one API, and get cross-platform compatibility, which can be nice. It also means (typically) being limited in what you can do to the least common denominator, or you (=the toolkit author) end up having to re-implement features from one platform that you want to expose but that are missing on some supported target(s). Or, of course, have an API with non-portable parts in it.

In any case, it means the "look and feel" is not the core feature of the API since that is going to be "like the target platform" and that is the point.

Given the origin, I guess Lua support is important too, here.

[1]: https://www.wxwidgets.org/

- So, I found wxWidgets. Which looked good. However, when I followed some tutorials I was getting errors. Even when I copied and pasted the tutorial code. Furthermore, the library still doesn't seem to simplify the process much.

It is the icon for WXWidgets, a programming toolkit for making user interfaces that work on Windows, Mac OS and Linux.