Plasma-Desktop: Port kcm fonts to QML.
Review Request #123682 - Created May 8, 2015 and discarded
This patch ports the kcm fonts to QML.
Everything works execpt from the ComboBox and the FontDialog ("Configure Font").
If you open the kcm inside from the system settings, everything is ok.
If you use kcmshell5 fonts, the FontDialog is opening behing the kcm window.
In order to solve this issue we must use the setTransientParent, but how can
i do that in the FontDialog?
If you open the kcm with the "kcmshell5 fonts", the dropdown menu renders fine.
But if you open it inside from the system settings, the dropdown menu, renders
in the left of the ComboBox.
Also these two signals (main.qml line 295)
are being emitted but the kcm.needsSave doesn't work...
Regressions just going by the screenshot:
Doesn't use form layouting (e.g. the font box labels aren't right-aligned).
The font box height doesn't match the button heights anymore.
Missing colons in the text labels.
Wonky margin between combo box label and combo box.
* No keyboard accelerators.
General conceptual problems with this port:
Poor QStyle support, e.g. drag on empty space in Oxygen/Breeze doesn't work with this toolkit.
IIRC QStyle background support (like Oxygen's radial gradient) doesn't work either, don't remember though.
Additional problems after trying it out:
Poor load performance - loading the KCM from the System Settings main page is significantly slower than the old KCM and involves some flicker.
The anti-aliasing config dialog has a white/unstyled background and improper dialog margins. There's also a ton of crap margins/positioning around widget in its form.
* The "Hinting style" combo box popup has wonky margins between the radio buttons and the text labels, and a grey background when it's supposed to be white.
What's the motivation behind this port? What user problem does it solve? How does it make this product better? Remember to not just throw code over the fence; you're supposed to argue for why a change is a good idea on review board. Your review request doesn't adequately answer any of these questions. Note that "but other KCMs use Qt Quick and have similar problems" is no argument for making this one worse (but it's an argument for fixing the others by whatever means).
I have fix the layouting issues. (see screenshot)
Should i merge this one in the kcmQmlPorts branch?
Revision 2 (+978 -913)