then use font metrics...http://doc.qt.io/qt-5/qml-qtquick-fontmetrics.html

or in this Plasmoid case use Units.gridUnit * 40

which is gonna be basically the same.

it's a bit rubbish, but:

zoom: Units.devicePixelRatio

should sort out DPI.
(not tested)

no it doesn't

Plasma core provides a dataengine QML exposer.
https://api.kde.org/frameworks/plasma-framework/html/classPlasma_1_1DataSource.html

Is there a reason we made a specialised QML wrapper?
(not that I object to this)

Unused?

onAccepted instead of Keys.onReturnPressed

Does this need a Layout.fillWidth: true and Layout.fillHeight: true? The TextField probably also needs Layout.fillWidth?

Ah, yes. That was for "formFactor" as in https://techbase.kde.org/Development/Tutorials/Plasma5/QML2/GettingStarted#Minimum_size
(which I had to fix so the syntax would parse).

But I'm not sure if I need to handle form factors in this applet, and if so, how...

Oh, cool, FontMetrics didn't exist in my first QML attempts.

But yeah if plasmoids should fit a grid, I'll use the grid then.

Layout.fillHeight: true led to a 1-pixel-high webview, not good.

Layout.fillWidth: true is good, it means I don't duplicate the width anymore.

OK, and doing that in the TextField makes the applet resize to the user's wishes, I see. Thanks.

zoomFactor: units.devicePixelRatio
helped indeed, thanks.

Indeed. One day it should, though, I'd like the user to be able to choose which dict to use. Do I have to write a config dialog in QML, though? If so, any example I can use for that?
Or can it use widgets?

Ah, I didn't know.
But I'd rather have as much logic as possible in C++, rather than in JS.
The whole thing about listing dicts, and allowing the user to choose one (or more?), storing that in KConfig, and then using that for querying... I'm not sure but I think using DataSource directly wouldn't make this easy, I would still need a QObject at least for the KConfig part, and it would mean interfacing that with DataSource in JS code...

Hmm, but the user should be able to resize the applet vertically too... I get very confusing behaviour even with
`Layout.preferredHeight: 400
Layout.fillHeight: true`

It resizes down to very little, jumps around in the desktop, etc.
I need to dig further into all this.

Why you prefer invoke rather than a signal ?

Heh, I just didn't think of that, when I turned the direct call into invokeMethod to fix the threading issue. Indeed a signal is much simpler, removes the need for m_dict altogether.
Thanks for the suggestion.