wxWidgets
JUCE
Our great sponsors
wxWidgets | JUCE | |
---|---|---|
52 | 105 | |
5,732 | 6,096 | |
2.1% | 2.3% | |
9.9 | 9.5 | |
1 day ago | 4 days 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
- 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.
JUCE
-
3rd Edition of Programming: Principles and Practice Using C++ by Stroustrup
Personally, I started by writing externals for Pure Data, then started to contribute to the care. Later I took the same path for SuperCollider.
The more typical path, I guess, would be to start with simple audio plugins. Have a look at JUCE (https://juce.com/)!
Realtime audio programming has some rather strict requirements that you don't have in most other software. Check out this classic article: http://www.rossbencina.com/code/real-time-audio-programming-...
-
Anyone know anyone that creates plugins?
Check out https://juce.com in the meantime
-
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
-
What programming languages do you recommend starting with regarding audio visual programming/audio software development?
Respect for the others here who recommend C but I think they’re possibly masochists. If anything JUCE, which uses C++ is in my opinion far more approachable.
-
How have you used coding in your setup?
Here's a link to their website: https://juce.com/
- xcode or visual studio?
-
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.
-
Common Audio Production
C++ has https://juce.com/, I think.
-
Apple Logic Pro Ruleface
Open source rule https://juce.com/
What are some alternatives?
imgui - Dear ImGui: Bloat-free Graphical User interface for C++ with minimal dependencies
Qt - Qt Base (Core, Gui, Widgets, Network, ...)
FLTK - FLTK - Fast Light Tool Kit - https://github.com/fltk/fltk - cross platform GUI development
iPlug2 - C++ Audio Plug-in Framework for desktop, mobile and web
gtkmm - Read-only mirror of https://gitlab.gnome.org/GNOME/gtkmm
OpenFrameworks - openFrameworks is a community-developed cross platform toolkit for creative coding in C++.
GTK+ - Read-only mirror of https://gitlab.gnome.org/GNOME/gtk
nana - a modern C++ GUI library
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++.