qskinny VS score

That's exactly what we are doing with QSkinny: https://github.com/uwerat/qskinny, we have been using it for a customer project for years now...

Not really, or at least, not fully. The roadmap for Qt 6 somewhat vaguely intends to have a C++ API for Qt Quick Controls (now there is, but very limited and private with no compatibility, and ugly to use). I think they are seeing that QSkinny can take some market from them.

C++ qt quick: https://github.com/uwerat/qskinny

Do you think that an approach like QSkinny would work for you? I've not used it myself in practice (just running the examples, and looking at the code), but the idea of it is that it uses Qt Quick as a backend (so I guess in Qt 6 it would use OpenGL/Vulkan/Metal/etc as needed without you having to do the abstraction), and IIRC it uses some of the private APIs that Qt Quick Controls use as well for the C++ side. QSkinny doesn't require to use QML though (should be optional, but I think C++ is preferred/more tested). It has been said also that during the Qt 6 timeline, there might be a C++ public API for Qt Quick Controls.

It kind of is (with a 3rd party library). Or you can use the private API (which I would not recommend). A public C++ API for Qt Quick Controls is planned as well, but I'm not very optimistic on the time frame.

https://ossia.io uses widgets and qgraphicsscene for the main UI rendering and Qt rhi for the GPU pipeline, and it's performing well enough for our use-cases - I was working on it on a 1080p screen on a Pi4 recently and it certainly felt much much faster and responsive than chrome on the same hardware.

I use it for live c++ recompilation in https://ossia.io - all the code is in there. https://github.com/ossia/score/tree/master/src/plugins/score-plugin-jit/JitCpp

> I feel like visual programming gets a bad rap because of things like this. As an electronic engineer that used to love LabView and life long user of NI Reaktor and Max/MSP, those tools are fantastic if you don’t approach them with an imperative programming mindset.

aha, in the long run I ended up making https://ossia.io which is as VPL as it can get. Yet it still embeds a LOT of textual languages.

For me both VSCode and CLion lag heavily.. whenver I tried CLion it was completely unuseable on my project https://ossia.io which is only 500kloc (and I try to try it pretty much once a year since it was in beta)

https://ossia.io does some of it, I've been working on a new release that also supports the whole QtQuick stack in the node graph items but you can already combine videos & shader effects

In https://ossia.io with PCH, using clang, ninja, mold, and some artificial split in shared libraries for development builds, I get a compile-edit-run cycle of a couple seconds in general... I wouldn't say it's too much of a problem if you use the tools already available

If you're interested in multimedia https://ossia.io is always looking for new contributors!

Tools like Ossia Score, Chataigne and PureData (pd) can also help a ton in building interactive art and triggering other A/V software.

here's a simple example of how to do it in https://ossia.io score : https://streamable.com/wkklek