Elements C++ GUI library
wxWidgets
Our great sponsors
Elements C++ GUI library | wxWidgets | |
---|---|---|
13 | 52 | |
2,903 | 5,721 | |
- | 1.9% | |
9.5 | 9.9 | |
6 days ago | 4 days ago | |
C++ | C++ | |
The MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Elements C++ GUI library
- declarative GUI libraries
-
Digital Audio Workstation Front End Development Struggles
There's a relatively new C++ GUI library literally called "Elements". Not sure how it works though, but the way it looks, and the music background of its creator makes it appear designed for DAWs.
https://github.com/cycfi/elements
-
Introducing Slint 1.0 - The Next-Generation GUI Toolkit with C++20 APIs
Further, if you we want a "modern" C++ GUI framework what actually would be modern would be to use mechanisms in the language itself as a quasi-DSL from within the language. This is something like what Joel de Guzman is doing with Elements
- Can I include cycfi/elements with CMake in any project or must I build up on example projects?
-
Boost.URL ACCEPTED, get the beta now!
It's a complex domain. The closest we have at the moment is Elements which hasn't been proposed for Boost (yet?) but is by Joel de Guzman, the primary author of Boost.Spirit.
-
Is there any MIT/BSD licensed UI framework for C++ ?
I ended up with elements gui https://github.com/cycfi/elements
-
GUI for software, not games, but lighter than Qt ?
If you don't want to use Qt I honestly think your best bet may be to become an early adopter of cycfi elements depending on your project. Elements is still rough but is useable for small applications. I think when it is finished it will be the best choice for a retained mode GUI library, but right now it is missing a lot of things (e.g. the standard common dialogs, "open", "Save as", etc.) , and has basically zero documentation.
-
What are you using for GUIs?
github link
-
Why I choose Electron even when I wanted to use QT
For the past year we were evaluating EFL, QML and Flutter for our embedded TV devices after having used the first two for last 5+ years and choice was made to go with Flutter. Performance is great, license is great, and development experience, judged by the whole development team, is the best. Hence my remark on being sad as QML could have had a great future, even transitioned to modern C++ without need for separate language, if there was a huge adoption and proper choices made by the company, e.g. see https://github.com/cycfi/elements.
wxWidgets
- Solitaire: Authentic remake of the Windows 95 original
-
Building Apps with Tauri and Elixir
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.
-
WxWidgets – open-source C++ cross platform GUI
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
-
Need for GUIs for bioinformatic tools?
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.
-
Create desktop application
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.
-
IUP – Cross platform C GUI library
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/
-
Creating C++ windowed applications
- 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.
-
What does this icon belong to? I've seen it used in many pieces of software, but I never found out what it actually is from.
It is the icon for WXWidgets, a programming toolkit for making user interfaces that work on Windows, Mac OS and Linux.
-
Inkscape is hiring: Accelerating the GTK4 migration
In general, people will use a cross-platform library to port such applications. While QT will likely never really stabilize (I'd flag it unsustainable), the https://www.wxwidgets.org/ is able to be statically linked into commercial and opensource projects at no cost without tripping GPL.
"Hiring a senior C++ developer with GTK experience is costlier"
I think you are confusing skill valuation, and operational productivity. Some have an erroneous notion talent is interchangeable. Likewise, applicants with identical base skill-sets on their CV often mistakenly believe they even have long-term employment options (outsourced, youth tax credit churn, and or senior wage suppression).
Most FOSS people are easier to train, as most already can mitigate utter chaos already. =)
-
Is it possible to build a gui which is both cross compatible and native?
There are a few like that in the C++ community. WxWidgets is the most famous/popular with this approach. But it is a library almost impossible to use in other languages because their api is heavily templated.
What are some alternatives?
imgui - Dear ImGui: Bloat-free Graphical User interface for C++ with minimal dependencies
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.
FLTK - FLTK - Fast Light Tool Kit - https://github.com/fltk/fltk - cross platform GUI development
lvgl - Embedded graphics library to create beautiful UIs for any MCU, MPU and display type.
gtkmm - Read-only mirror of https://gitlab.gnome.org/GNOME/gtkmm
Turbo Vision - A modern port of Turbo Vision 2.0, the classical framework for text-based user interfaces. Now cross-platform and with Unicode support.
GTK+ - Read-only mirror of https://gitlab.gnome.org/GNOME/gtk
nana - a modern C++ GUI library
RmlUi - RmlUi - The HTML/CSS User Interface library evolved
libui - Simple and portable (but not inflexible) GUI library in C that uses the native GUI technologies of each platform it supports.