Librum VS qskinny

>Why should they have to justify providing free software?

They don't, but they have to be honest about what they're presenting. There's this shitty motte-and-bailey situation in open source where their website ( https://librumreader.com/ ) looks like marketing for a serious application - but the moment you treat it like a serious application, people are like "it's free, why are you treating it like a serious application?".

Look:

>Simplicity

>Focus on what actually matters, using a simple and straight forward interface.

>Your time is too valuable to be wasted on complex applications.

What does the tone here convey? Is it "this is just a cool project I wrote"?

Thank you for reading, here are links to the project if you want to take a look: Our current website: https://librumreader.com The client application: https://github.com/Librum-Reader/Librum

Hey, I want to add CI to a project that depends on a big framework and some smaller linux libraries (https://github.com/Librum-Reader/Librum). I have a command that installs all dependencies on ubuntu, but it takes some minutes to install all of these libraries.

Thank you in advance for any advice on this topic (For some context, here is my project's github repository: (https://github.com/Librum-Reader/Librum)

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.