vgc VS qskinny

I've detailed some of the rationale here: https://github.com/vgc/vgc/issues/200

What's really cool is that VGC Illustration is fully free as in freedom (as in free speech, not price) software, and the creator is trying out the Ardour style funding model where you pay to obtain the compiled binaries, while the code is fully open source available in this GitHub repository. I like this funding model and encourage others to support it.

Oh, this is a super interesting feature request, thanks, I never thought of that! I added the request to GitHub to not forget: https://github.com/vgc/vgc/issues/565

Yes, it is open source, under the Apache 2.0 License. The source code for the prototype VPaint is here: https://github.com/dalboris/vpaint and the source code for VGC Illustration is here: https://github.com/vgc/vgc

The prototype is using Qt's QColor, which I believe is underlying a 16-bit integer per channel. The new re-implementation VGC Illustration is actually using 64-bit float per channel, I'm not kidding: https://github.com/vgc/vgc/blob/master/libs/vgc/core/color.h . It's probably a little overkill, so I may tone it down to 32-bit float per channel if I notice performance issues, but yes, basically I'll have your needs covered :-P

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.