Improve Plasmoid/Kirigami documentation
I am not the author of this; I'm just copying some helpful user feedback from this thread here for better findability. Just extracting the relevant snippets; there is also some praise in the original post.
Getting on Board Documentation. [...]
What I find confusing, it’s three different domains: techbase., develop. and api.. I get the idea that develop. is guides while api.* is doxygen generated, but in practice I don’t remember where exactly I saw a specific information and how to find it again. A quick example, I referred to Plasmoid class description on develop., but Plasma Components entry point is on api.. Techbase has also something on plasmoids but with slightly different syntax. QML docs on the other hand have cross links in every class API to higher level guides/manuals and back, I’d go in the same way for KDE docs. It'd nice to have three sources more integrated.
Another thing is not immediately clear how to manage widget size in compact mode(and full mode as well). I set minimumHeight and minimumWidth for now. Do preferredWidth or width have any effect? Is it possible to change widget’s width/height in compact mode or it’s settled once panel appears? Didn't find anything on this.
Kirigami. [...]
I was not able to make Kirigami passive notifications work to warn the user when they try to start another activity while a previous one is still active in the widget. I didn’t go deeper into why. Is it supposed to work in widgets? Now I am still w/o notifications. Help me pleeease. Also, QML requires specify versions to import components. I was confused when to use which version. It backfired in the end. I also don’t understand practical difference between QtQuick components, Plasma(and Extra) components and Kirigami ones except obvious idea that Plasma components aren’t available on other platforms. I’d include into Kirigami tutorial footnotes cross linking underlying QtQuick components and related Plasma components explaining briefly the difference and intention. I ended up using mix of all 3 libraries in the widget promiscuously.
I’ve written *.qml files manually. That’s by far the biggest and most prominent issue. Even when I started programming dozens of years ago I was already using WYSIWIG editors to develop GUI visually. QtCreator 6 I heard is able to design QML visually, does it support Kirigami? I am using QtCreator 5 and had to test GUI after every few lines changed. I couldn’t stress enough importance if WYSIWYG approach for GUIs.
[...] Another issue, I was not immediately able to find information on Data Engines. It's briefly mentioned in one Develop example, but that's about it. Little more information is on yet another domain https://community.kde.org/