We need to port everything from QQC1 before release.
I just saw this in a review
"Everything is ported to QQC2 except for the TableView since there is no direct analogue
in QQC2."
That could mean some code in Kirigami or we need it in QQC2.
If we need it in QQC2 we need to act /now/
Do we need additional API compared to https://doc.qt.io/qt-5/qml-qtquick-tableview.html?
+1 to upstreaming this if possible. One of my persistent pet peeves with QML is how views like this are DIY affairs a lot of the time. More high-level controls and views are always appreciated so you don't need to spend so much time manufacturing the same thing over and over again. Probably best to get it into Qt itself, but I suppose Kirigami could be a backup plan if that fails.
Do we need additional API compared to https://doc.qt.io/qt-5/qml-qtquick-tableview.html?
That tableview is a grid of delegates in a flickable.
It does not have the frame + scrollbars + themed delegates
Maybe it is enough to have a common flickable container and have every user duplicate that little bit?
QQC1 tableview is currently used in:
Action plan: Take the code from plasma-system montior copy pasta to kirigami-addons
Port the 3 things above