copperspice VS Elements C++ GUI library

Tangentially, I just listened to an old cppcast about https://www.copperspice.com/, a QT fork with ambitions of being more c++-ey.

There was already a fork of Qt 4. It is tootling along fine: https://www.copperspice.com/

BTW, CopperSpice sounds pretty close to what you're mentioning: https://www.copperspice.com

If you already have a lot of use of Qt your might find CopperSpice to be a reasonable compromisehttps://www.copperspice.com/

exactly I'm quite happy to have my code written for me. If you don't like the moc you can use CopperSpice https://www.copperspice.com/

CopperspiceCopperspice

CopperSpice might be worth looking at too. Coming from Qt you're probably going to like it better than wxWidgets.

So I strongly dislike Qt. It's got a predatory vision for open source enforcement where they mislead their customers with spoopy language and make it harder and harder to download. In addition, they continue to insist on an architecture that's not even actually C++ (it's got a different grammar) despite it being completely possible to architect a better version of their designs in standard C++.

See copperspice project. Originally forked to work around short coming of Meta-Object Compilation.

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.