Summary: | Custom configuration for Applets (XDG configs and rc files) | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | Sergey Katunin <sulmpx60> |
Component: | general | Assignee: | Unassigned bugs <unassigned-bugs-null> |
Status: | RESOLVED NOT A BUG | ||
Severity: | wishlist | CC: | kde |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Sergey Katunin
2025-07-09 14:27:07 UTC
Please see https://develop.kde.org/docs/plasma/scripting/ You can run hooks on first run or on new applet creation. (In reply to David Edmundson from comment #1) > Please see https://develop.kde.org/docs/plasma/scripting/ > > You can run hooks on first run or on new applet creation. To be honest, I didn't quite understand how to hook to the creation of a new applet? But by the way, as far as I know, these scripts will change the values in the `plasma-org.kde.plasma.desktop-appletsrc` file in the same way as if they were changed by the user himself. And this differs from the default values in the sense that if the system administrator or system integrator then makes new changes to the default configuration of applets, they will not automatically change for the user, since old values will be explicitly written in `plasma-org.kde.plasma.desktop-appletsrc'. And it will be difficult to distinguish which values were set by the scripts last time, and which values were set by the user himself. But if we change the default values in main.xml, then it will automatically upload new changes for the default settings, unless the user has manually set their own value through the interface, which is saved in `plasma-org.kde.plasma.desktop-appletsrc`. |