Qt does. They just don’t actually work with Kirigami.Theme, so you can’t write portable Kirigami code, you either need to commit your QML to Kirigami.Theme and breeze, or Material.theme et al. on all platforms.
And that’s just if you want to respect the user’s choice of light or dark, let alone any richer UI experience than that.
I don’t know how good they are because I don’t use them,
Which makes all the high level documentation that promises all this sort of stuff works on all the platforms that all the cool kids are using and is “guaranteed to be cross platform” - part of the problem as well.
But I didn’t wake this thread up just to grumble, or to point out that we’re nearly a year on and this:
Kirigami itself can use whatever QtQuick Controls (QQC) style you want, and Qt comes with a Material QQC style
is still an incredibly misleading half-truth, in that you can pick any one style per application that it will use on every platform - but you can’t write portable QML that can be externally styled to look appropriate for the environment its running in.
Or to bang on about how much time I just wasted figuring that out The Hard Way. Or how that’s just the tip of a very big iceberg.
But this thread spun off from the question, We need your thoughts on Kirigami, and it does kind of highlight what I think is a problem that will bite you if it isn’t doing so already.
If you’re open and honest and clear about the current limitations this code has, people wanting or trying to use it will have realistic expectations about what does and doesn’t work, and what they might contribute to if it’s a personal itch of theirs. But if you make grandiose, and untested, promises about how easy it is to write code that looks and works beautifully and seamlessly on all platforms, when people’s lived experience is horrifically different to that, then you will lose people, not just as users, but as contributors. When a problem is clearly indicated, people can efficiently choose to route around it or chip in to help fix it. When it’s not, a lot of everyone’s time becomes wasted, and a very different set of questions comes into play.
It’s great to have aspirational goals - and not all the problems here are directly with Kirigami, it sits at the tip of a large, also work-in-progress, house of cards - but being at the pointiest end of user-facing does mean accepting that the buck stops with you for being the face of user friendly.
When one page of docs “guarantees” everything is cross platform and “perfect for mobile”, and the next page shows isolated partial examples of fundamental features like colour and theming that isn’t actually cross platform and doesn’t actually work on mobile, and doesn’t have a little asterisk explaining that - and doesn’t even fail in obvious and easily diagnosable ways, it just silently Doesn’t Work… Then the job of winning hearts and minds just dug itself a really big hole, and filled it with pointy sticks.
If I’d have been assessing this for a new project instead of trying to bring an existing one up to speed with current versions of its deps … then yeah, I’d probably be busy testing something else instead of writing this with the hopes of a Better Future right now… and you asked, so it’s some honest debrief feedback, which I hope is taken positively even if this time it’s not a pat on the head for Doing Good Things.