Installing JavaScript Plasmoids in KDE 5
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
For the last year, I have been a happy user of KDE Plasma 5. KDE widgets, however, make me miss more directly programmable systems such as conky. Setting up an ad-hoc monitor for anything that needs monitoring at a given moment is not an easy task with KDE Plasma 5, whereas it is a matter of throwing together a shell script and adding a line to ~/.conkyrc
.
I understand that to expect conky's extensibility of KDE Plasma 5 would be to misunderstand the project's priorities. Nevertheless, KDE Plasma 4 appears to have JavaScript bindings, which would be much more suitable for ad-hoc desktop scripting compared to the primary Qt C++ API. The kdeexamples Git repository even contains a number of example plasmoids written in JavaScript. However, when I download the Git repository and install an arbitrary example widget:
$ git clone git://anongit.kde.org/kdeexamples.git
$ kdeexamples/plasma/javascript/plasmoids
$ (cd mediaplayer/; zip ../mediaplayer *)
$ plasmapkg -i mediaplayer.zip
Successfully installed /home/witiko/kdeexamples/plasma/javascript/plasmoids/mediaplayer.zip
the widget never appears in the âÂÂAdd Widgetâ menu regardless of whether or not I restart Plasma:
$ killall plasmashell; kstart plasmashell
I am guessing that either things changed between KDE Plasma 4 and 5, or that I am doing something wrong. I will be grateful for pointers in the right direction.
kde kde5 plasma5 javascript
add a comment |Â
up vote
1
down vote
favorite
For the last year, I have been a happy user of KDE Plasma 5. KDE widgets, however, make me miss more directly programmable systems such as conky. Setting up an ad-hoc monitor for anything that needs monitoring at a given moment is not an easy task with KDE Plasma 5, whereas it is a matter of throwing together a shell script and adding a line to ~/.conkyrc
.
I understand that to expect conky's extensibility of KDE Plasma 5 would be to misunderstand the project's priorities. Nevertheless, KDE Plasma 4 appears to have JavaScript bindings, which would be much more suitable for ad-hoc desktop scripting compared to the primary Qt C++ API. The kdeexamples Git repository even contains a number of example plasmoids written in JavaScript. However, when I download the Git repository and install an arbitrary example widget:
$ git clone git://anongit.kde.org/kdeexamples.git
$ kdeexamples/plasma/javascript/plasmoids
$ (cd mediaplayer/; zip ../mediaplayer *)
$ plasmapkg -i mediaplayer.zip
Successfully installed /home/witiko/kdeexamples/plasma/javascript/plasmoids/mediaplayer.zip
the widget never appears in the âÂÂAdd Widgetâ menu regardless of whether or not I restart Plasma:
$ killall plasmashell; kstart plasmashell
I am guessing that either things changed between KDE Plasma 4 and 5, or that I am doing something wrong. I will be grateful for pointers in the right direction.
kde kde5 plasma5 javascript
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
For the last year, I have been a happy user of KDE Plasma 5. KDE widgets, however, make me miss more directly programmable systems such as conky. Setting up an ad-hoc monitor for anything that needs monitoring at a given moment is not an easy task with KDE Plasma 5, whereas it is a matter of throwing together a shell script and adding a line to ~/.conkyrc
.
I understand that to expect conky's extensibility of KDE Plasma 5 would be to misunderstand the project's priorities. Nevertheless, KDE Plasma 4 appears to have JavaScript bindings, which would be much more suitable for ad-hoc desktop scripting compared to the primary Qt C++ API. The kdeexamples Git repository even contains a number of example plasmoids written in JavaScript. However, when I download the Git repository and install an arbitrary example widget:
$ git clone git://anongit.kde.org/kdeexamples.git
$ kdeexamples/plasma/javascript/plasmoids
$ (cd mediaplayer/; zip ../mediaplayer *)
$ plasmapkg -i mediaplayer.zip
Successfully installed /home/witiko/kdeexamples/plasma/javascript/plasmoids/mediaplayer.zip
the widget never appears in the âÂÂAdd Widgetâ menu regardless of whether or not I restart Plasma:
$ killall plasmashell; kstart plasmashell
I am guessing that either things changed between KDE Plasma 4 and 5, or that I am doing something wrong. I will be grateful for pointers in the right direction.
kde kde5 plasma5 javascript
For the last year, I have been a happy user of KDE Plasma 5. KDE widgets, however, make me miss more directly programmable systems such as conky. Setting up an ad-hoc monitor for anything that needs monitoring at a given moment is not an easy task with KDE Plasma 5, whereas it is a matter of throwing together a shell script and adding a line to ~/.conkyrc
.
I understand that to expect conky's extensibility of KDE Plasma 5 would be to misunderstand the project's priorities. Nevertheless, KDE Plasma 4 appears to have JavaScript bindings, which would be much more suitable for ad-hoc desktop scripting compared to the primary Qt C++ API. The kdeexamples Git repository even contains a number of example plasmoids written in JavaScript. However, when I download the Git repository and install an arbitrary example widget:
$ git clone git://anongit.kde.org/kdeexamples.git
$ kdeexamples/plasma/javascript/plasmoids
$ (cd mediaplayer/; zip ../mediaplayer *)
$ plasmapkg -i mediaplayer.zip
Successfully installed /home/witiko/kdeexamples/plasma/javascript/plasmoids/mediaplayer.zip
the widget never appears in the âÂÂAdd Widgetâ menu regardless of whether or not I restart Plasma:
$ killall plasmashell; kstart plasmashell
I am guessing that either things changed between KDE Plasma 4 and 5, or that I am doing something wrong. I will be grateful for pointers in the right direction.
kde kde5 plasma5 javascript
kde kde5 plasma5 javascript
edited Oct 9 '17 at 15:48
asked Oct 9 '17 at 14:11
Witiko
334215
334215
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
kpackagetool5 -i this.plasmoid
is enough to get a proper plasmoid available to place, say on desktop.
try it with a known working one such as the steam punk clock: https://store.kde.org/p/1002162
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
kpackagetool5 -i this.plasmoid
is enough to get a proper plasmoid available to place, say on desktop.
try it with a known working one such as the steam punk clock: https://store.kde.org/p/1002162
add a comment |Â
up vote
0
down vote
kpackagetool5 -i this.plasmoid
is enough to get a proper plasmoid available to place, say on desktop.
try it with a known working one such as the steam punk clock: https://store.kde.org/p/1002162
add a comment |Â
up vote
0
down vote
up vote
0
down vote
kpackagetool5 -i this.plasmoid
is enough to get a proper plasmoid available to place, say on desktop.
try it with a known working one such as the steam punk clock: https://store.kde.org/p/1002162
kpackagetool5 -i this.plasmoid
is enough to get a proper plasmoid available to place, say on desktop.
try it with a known working one such as the steam punk clock: https://store.kde.org/p/1002162
answered Jun 22 at 22:58
j mp
114
114
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f397034%2finstalling-javascript-plasmoids-in-kde-5%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password