Elements C++ GUI library VS JUCE

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

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

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.

I ended up with elements gui https://github.com/cycfi/elements

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.

github link

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.

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-...

Check out https://juce.com in the meantime

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..)

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.

Here's a link to their website: https://juce.com/

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.

C++ has https://juce.com/, I think.

Open source rule https://juce.com/