Filling org.kde.plasma.quicklaunch per user

[Ludwig Cornelius]

Am 12.10.2017 um 14:31 schrieb Marco Martin:
> On Thu, Oct 12, 2017 at 12:53 PM, Ludwig Cornelius <t_d_l_c at gmx.de> wrote:
>> 1.) Put a javascript file in:
>> ~/.local/share/plasma/shells/org.kde.plasma.desktop/updates/
> should be in
> ~/.local/share/plasma/shells/org.kde.plasma.desktop/contents/updates/
> (you forgot contents)

In this wiki the path is written without "contents":

https://userbase.kde.org/KDE_System_Administration/PlasmaTwoDesktopScripting#Running_Scripts

But I will try with "contents". I will test with plasma 5.10.90 and 
KDE-Frameworks 5.39.0.

>> a.) Is it possible to log if this script was executed? Which would be the
>> right component in kdebugdialog? ksmserver?
> in order to know if the script was executed, look in
> ~/.config/plasmashellrc
> [Updates]
> performed=
>
> (for instance i have
> [Updates]
> performed=/opt/kde5/share/plasma/shells/org.kde.plasma.desktop/contents/updates/obsolete_kickoffrc.js,/usr/share/plasma/shells/org.kde.plasma.desktop/contents/updates/obsolete_kickoffrc.js
> )
>
> if the path of your script is in the updates list, has been executed.
>

Thank you, that is very helpful.

>> b.) Is it possible at all to execute a javascript file on first login?
> i am not sure that an update script would be executed at first
> login... maybe you need to have a variation in the initial layout.js
> ...
> perhaps a look and feel package which is installed locally in the user
> home (and is slightly different for each user in regard to the
> quicklaunch configuration?)
That's an idea.
>> 2.) Put a desktop file in ~/.config/autostart that executes a script to
>> manipulate ~/.config/plasma-org.kde.plasma.desktop-appletsrc. The problem is
> don't touch the appletsrc by external programs/scripts, it won't work well.
>
> --
> Marco Martin

I am aware of that is not a good solution.


Best wishes