wxWidgets
JUCE
Our great sponsors
wxWidgets | JUCE | |
---|---|---|
51 | 104 | |
5,673 | 6,017 | |
2.1% | 2.3% | |
9.9 | 9.6 | |
6 days ago | about 8 hours ago | |
C++ | C++ | |
- | GNU General Public License v3.0 or later |
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.
wxWidgets
-
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:
-
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.
-
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.
-
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 do that in the C++ community. WxWidgets is the most famous/popular with this approach.
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.
-
GUI programming in C++
wxwidgets If you prefer to use actual native widgets If you don't like Qt Fewer users = less help, less features
-
how can i design a desktop app with dart
Using FFI, you should be able to access something like wxwindows, I guess. That's cross platform then. And more high level. And it would probably a fun exercise to write a Dart wrapper for that library.
JUCE
-
Modern C++ Programming Course
You can definitely start putting C++ into your embedded projects, and get familiar with things in an environment in which you're already operating. A lot of great C++ code can be found with motivated use of, for example, the platformio tooling, such that you can see for yourself some existing C++ In Embedded scenarios.
In general, also, I have found that it is wise to learn C++ socially - i.e. participate in Open Source projects, as you learn/study/contribute/assist other C++ developers, on a semi-regular basis.
I've learned a lot about what I would call "decent C++ code" (i.e. shipping to tens of thousands, if not hundreds of thousands of customers) from such projects. I would suggest finding an open source C++ project, aligned with your interests, and study the codebase - as well as the repo history (i.e. gource) - to get a productive, relatively effortless (if the interests align) boost into the subject.
(My particular favourite project is the JUCE Audio library: https://juce.com/ .. one of many hundreds of great projects out there from which one can also glean modern C++ practices..)
- Ardour 8.0 released
-
How have you used coding in your setup?
Here's a link to their website: https://juce.com/
-
Anyone here have experience writing VST audio plugins in C++, or 'wrapping'/converting a VST to an AU plug-in?
It seems like most audio plug-ins are built in C++ inside an audio coding program called JUCE, so maybe if I could open up the exisiting code inside that and then output it as an AU instead of a VST that could work.
-
Ask HN: What audio/sound-related OSS projects can I contribute to?
JUCE:
Tracktion:
Both very powerful audio frameworks - JUCE does plugins and audio drivers and low-level DSP, oh my - and Tracktion does all the stuff a DAW needs, on top of JUCE.
There are tons of ways to contribute, from building open source samples, to testing, or even adding functionality. Both dev teams are open to good quality PR's being submitted and both frameworks have excellent communities that will get you started: http://forum.juce.com/
These are cross-platform tools which offer Audio developers an extremely powerful toolset. By contributing to either (or both) frameworks you will be massively contributing to the audio world - so many plugins use JUCE these days!
- Recommendation for professional open source project where we can learn best practices, contribute and improve coding knowledge simply by looking at the code?
-
Leveraging Rust and the GPU to render user interfaces at 120 FPS
> Juce has a CoreGraphicsMetalLayerRenderer which I believe uses Metal to render CoreGrapghics primitives.
This class is part of a JUCE demo app, and you can read the source code to it if you want. [0] It uses CoreGraphics to render the graphics on the CPU, and then uploads it as a texture to the GPU so it can be used as a CAMetal layer. So, no, the graphics are still rendered on the CPU, with compositing being handled on the GPU.
> For example, I heard that UE4->UE5 removed the GPU tesselation support
I know it's confusing, but GPU tessellation is a completely different thing. The word "tessellation" in graphics means "turn into triangles". In a 2D graphics context, we're turning splines and curves and 2D shapes into triangles. In a 3D graphics context, GPU tessellation refers to a control cage mesh which is adaptively subdivided. These two have nothing in common except that triangles come out the other side. I am not aware of anyone who has tried to use GPU tessellation to render 2D graphics.
GPU tessellation failed for a large number of reasons, but slow performance was one of them. So, you know, doing this sort of work efficiently on the GPU is still an open research problem. Just because it's not efficient to do it on the GPU does not mean the performance overhead is negligible. For rendering big complex vector graphics, tess overhead can easily outweigh rasterization overhead.
[0] https://github.com/juce-framework/JUCE/blob/4e68af7fde8a0a64...
When we talk about 2D graphics as a research problem, we're talking about native rendering of splines and strokes. JUCE does not have GPU-accelerated splines, it flattens the path to lines and rasterizes the coverage area into a texture.
https://github.com/juce-framework/JUCE/blob/2b16c1b94c90d0db...
https://github.com/juce-framework/JUCE/blob/2b16c1b94c90d0db...
It also does stroke handling on the CPU:
https://github.com/juce-framework/JUCE/blob/2b16c1b94c90d0db...
Basically, this isn't really "GPU accelerated splines". It's a CPU coverage rasterizer with composting handled by the GPU.
You linked to the compatibility-renderer. But JUCE also has platform-specific rendering modules.
CoreGraphicsContext::createPath will convert the CPU spline segments to CG spline segments which are then rasterized by CoreGraphics using Metal on the GPU.
https://github.com/juce-framework/JUCE/blob/2b16c1b94c90d0db...
-
BlinderKitten, A free lighting software without restriction
Sure.
The device definitions come as GDTF files, see the spec and other projects that utilize GDTF here [1]
Juce framework [2]
OrganicUI [3]
What are some alternatives?
imgui - Dear ImGui: Bloat-free Graphical User interface for C++ with minimal dependencies
FLTK - FLTK - Fast Light Tool Kit - https://github.com/fltk/fltk - cross platform GUI development
Qt - Qt Base (Core, Gui, Widgets, Network, ...)
gtkmm - Read-only mirror of https://gitlab.gnome.org/GNOME/gtkmm
GTK+ - Read-only mirror of https://gitlab.gnome.org/GNOME/gtk
nana - a modern C++ GUI library
iPlug2 - C++ Audio Plug-in Framework for desktop, mobile and web
OpenFrameworks - openFrameworks is a community-developed cross platform toolkit for creative coding in C++.
audiogridder - DSP servers using general purpose computers and networks
libui - Simple and portable (but not inflexible) GUI library in C that uses the native GUI technologies of each platform it supports.
Cinder - Cinder is a community-developed, free and open source library for professional-quality creative coding in C++.