To me on my 13" screen they look a little big-ish. I’ll be happy with 3/4 or perhaps better with 3/5 of the size. I have looked a bit around in the settings but so far I haven’t found one related to this.
By windows do you mean the sys tray plasmoids themselves? Specifically the calendar day grid sizes?
Take a look in /usr/share/plasma/plasmoids, this is where the qml for these system plasmoids live.
For instance in /usr/share/plasma/plasmoids/org.kde.plasma.calendar/contents/ui/main.qml you could playaround with the default grid sizes in the qml code and see if it looks better on your small 13" screen.
Plasmoid.switchWidth: PlasmaCore.Units.gridUnit * 12
Plasmoid.switchHeight: PlasmaCore.Units.gridUnit * 12
Make a copy of the original file first of course, if you want to refresh and test your changes then restart plasmashell with …
killall plasmashell && kstart5 plasmashell&
If you bugger it all up then just copy the original file back and restart plasmashell.
Remember that any system plasmoid changes you make will get overwritten each Plasma update. I have 3 or 4 qml files I have to re-edit each update to make plasma ui more to my liking.
1 Like
Sorry for my clumsy formulation. I’m making a foray into Plasma Land, so much of it is quite uncharted territory for me.
I wish if I could resize the overall size of of them all.
I’ll follow your instructions and see how it will look in the calendar plasmoid.
After breakfast 
I’ll get back with the result.
Is there any way one could change them unde ~/.config somewhere?
And isn’t there one config somewhere to “govern” them all? At least when it comes to their “general” size.
Hi @otherbarry
I changed those two lines as instructed. I set the value to 8 for both to test. But something seems to go wrong on my end when I restart the plasmashell and there is no change in the size of the plasmoid afterwards.
$ killall plasmashell && kstart5 plasmashell&
[1] 3827
[pebcak@arch-plasma ~]$ Omitting both --window and --windowclass arguments is not recommended
kf.plasma.quick: Applet preload policy set to 1
trying to show an empty dialog
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height"
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height"
Plasma Shell startup completed
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:531:9: QML Label: Binding loop detected for property "height"
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:486:13: QML Label: Binding loop detected for property "height"
trying to show an empty dialog
Entry is not valid "kontact.desktop" QSharedPointer(0x5593d4b87a40)
Entry is not valid "ktp-contactlist.desktop" QSharedPointer(0x5593d4b41a40)
Entry is not valid "kontact.desktop" QSharedPointer(0x5593d4b89960)
Entry is not valid "ktp-contactlist.desktop" QSharedPointer(0x5593d4b0cf70)
Failed to register unity service
file:///usr/share/plasma/plasmoids/org.kde.panel/contents/ui/main.qml:30:1: QML DropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth"
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:486:13: QML Label: Binding loop detected for property "height"
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:531:9: QML Label: Binding loop detected for property "height"
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:553:5: QML Label: Binding loop detected for property "height"
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:213: Error: Invalid write to global property "prefix"
Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationHeader.qml"
QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
trying to show an empty dialog
When I put back the values to the original 12 and restart the shell once again, I get still the same “errors” as above. Perhaps something is not right a bit deeper under the hood?
Yeah, I get warnings and errors too restarting plasmashell … much of the qml in the system plasmoids is old, not to mention any older plasmoids from KDE store, hence warnings and a few errors. They still work though.
Tis the nature of an old, community developed, modular beast.
I didn’t spend any time looking at the calendar qml, I was showing where to look rather than telling you how to do it.
If it is possible to resize certain system plasmoid ui elements I think that is where you would look first. Be careful though, don’t change anything without making a .bak copy first.
Anyway, doesn’t the calendar sit within the Digital Clock plasmoid?
$ ll /usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui
drwxr-xr-x 2 root root 4096 Aug 9 15:40 .
drwxr-xr-x 4 root root 4096 Aug 12 2020 ..
-rw-r--r-- 1 root root 25332 Aug 8 18:30 CalendarView.qml
-rw-r--r-- 1 root root 10335 Aug 8 18:30 configAppearance.qml
-rw-r--r-- 1 root root 3522 Aug 8 18:30 configCalendar.qml
-rw-r--r-- 1 root root 9359 Aug 8 18:30 configTimeZones.qml
-rw-r--r-- 1 root root 25914 Aug 8 18:30 DigitalClock.qml
-rw-r--r-- 1 root root 5760 Aug 8 18:30 main.qml
-rw-r--r-- 1 root root 810 Aug 8 18:30 MonthMenu.qml
-rw-r--r-- 1 root root 4065 Aug 8 18:30 Tooltip.qml
I don’t think it will be straight forward with nested plasmoids, but not impossible if this is something you really want.
Thanks for the reply!
Sure, I have a better idea of where to look for this stuff and what I perhaps want to change and modify in there. This is all new for me so I will take it piece by piece.
Copied!
This is a very recent install of Arch with KDE. Mostly for having fun as a learning experience. If I could scale down the plasmoids to be more in harmony with the size of the screen, all the better.
But it is absolutely not a matter of urgency.
Thanks for your time and support! I appreciate it.