Oh, you maintain that? Ok that’s handy to know. That’s not the only example, it was just a clear and easy to confirm on any platform one. And really it started right from the very beginning of the examples there.
The cmake boilerplate needed for this is a kind of complicated mess of everyone re-implementing what someone else has done, but slightly differently and variously incompatibly. What’s shown there didn’t work for me - though part of that is partly down to the requirements of the full application stack I ultimately need, and the mess that occurs when mixing “the google way” with “the qt way” with “the ecm way” of building for android. That one’s a separate discussion to open and problem to work on once I get my example code posted and reviewed.
Then the very first minimal example didn’t work as advertised either. Even the very basic code shown in Explaining pages | Developer didn’t work as shown in the screenshots.
title didn’t display at all on Android, and Kirigami.ApplicationHeaderStyle.Auto did not work at all - the only thing that did is what the few android-supporting applications seemed to be doing which was always using Kirigami.ApplicationHeaderStyle.ToolBar and setting the page header with a titleDelegate … but they in turn also weren’t using what seemed to be the documented current best practice (in the source code) for many things either.
But it seems the header problem may now be (at least partly, I’ve only initially tested if it really was as we speak) fixed in the last few days with a fix for the Breadcrumb header style – though this has been exactly my quandary - for every problem figuring out whether it’s My Mistake, a change to How It’s Supposed To Be Done, or A Real Bug - and by the time I get halfway to being halfway certain about which of those categories I’m looking for a solution in, I’ve run into 6 other problems, all with the same uncertainty attached.
It’s been an extra-ordinarily slow process of digging through source code and trying to guess intent from sometimes very terse commit messages. It’s been a little reassuring to see that at least someone seems be front running me by a couple of days and fixing some of them in something close to real time as I’m stumbling over them - but these aren’t the sort of problems I would have initially expected to make it into release versions, so that’s been a learning experience all of its own.
And then there are things like:
https://bugreports.qt.io/browse/QTBUG-124926
and
qrc:/qt/qml/org/kde/kirigami/private/globaltoolbar/NavigationButtons.qml:89:13: QML ToolTip: Binding loop detected for property "contentWidth"
qrc:/qt/qml/org/kde/kirigami/private/PrivateActionToolButton.qml:101:5: QML ToolTip: Binding loop detected for property "contentWidth"
Which clearly aren’t caused by my code - but still need investigating before I can know what if any part they are playing in the problems that seem like they shouldn’t be happening.
I understand you’re frustrated
That people are (and some of the concrete reasons why they are) - is mostly just linking this back to the original “What are your reasons for not adopting Kirigami” question that this thread forked from - just ranting about being frustrated is not why I’m posting all this.
It’s the concrete problems and if and how they might be fixed that I’m most interested in.
the actionable thing to do is to report those issues in the repo
I’m very comfortable with code, it’s not a new thing to me - but I am still wrapping my head around both QML’s quirks, and the somewhat byzantine structure of KDE and who is responsible for what, where they like to triage and discuss things, and how responsive they are likely to be.
So I’m happy to report (and even send patches for) bugs - but right now probably what would be most helpful is knowing the right place to bounce the initial problems off to get some guidance on whether it’s Already Known, Something I’m doing wrong or should investigate more, definitely a bug that should be reported, or Only Going To Get Fixed If I Send A Patch.
It’s not like I think I’ve found A Bug. It’s more like I’ve lifted the mozzie net and they are everywhere I look - so it’s a problem that needs a more nuanced plan to solve than ‘hit it with a rolled up newspaper’. Swamping y’all with untriaged reports just creates its own People Are Already Too Busy To Solve problem.
I was sort of hoping the matrix room might be good for that, but so far not so much - so mostly I’ve just been collecting them as examples and notes in my testbed code to share once I’ve done my best to make what’s in it work as well as is currently possible. Then if nobody else responds, I can move on to the other things I need to get done with a clear conscience and without it hanging as a half-finished job over my head too …