Package Details: amarok-scripting 2.9.0.r376.457fbda25a-1

Git Clone URL: https://aur.archlinux.org/amarok-scripting.git (read-only)
Package Base: amarok-scripting
Description: The powerful music player for KDE (with Qt bindings for scripting)
Upstream URL: http://amarok.kde.org/
Licenses: GPL2, FDL, LGPL2.1
Conflicts: amarok, amarok-git
Submitter: snack
Maintainer: snack
Last Packager: snack
Votes: 2
Popularity: 1.145713
First Submitted: 2019-09-03 10:06
Last Updated: 2019-09-17 07:32

Pinned Comments

snack commented on 2019-09-15 10:10

Note: scripts need to be ported. This package only restores parts of the Amarok scripting capabilities, but old scripts probably won't work out of the box. Here's a partial list of useful tips (I'll keep it up-to-date as new information flows in):

1) Scripts are located in subfolders of .local/share/amarok/scripts/

2) A script.json file must be present inside each script folder. You have to create it manually; the content should be something like:
{
"KPlugin": {
"Category": "Scriptable Service",
"Id": "BurnPlayList",
"Version": "1.0.1",
"Dependencies": ["Amarok2.0"],
"EnabledByDefault": "true"
}
}

Latest Comments

Rhinoceros commented on 2019-09-25 07:20

Oh brilliant! Thank you again for chasing this up.

snack commented on 2019-09-25 06:33

@Rhinoceros Don't loose faith too early :) I just got a reply from the amarok developer that was responsible for the removal of the scripting facility, and it is an extremely positive one (I paste it here since there's nothing confidential):

Hi, I didn't know there is a way to have those bindings in qt5. If you create a phabricator revision with your changes, I'm sure it will be merged. The phabricator discussion you linked clearly says that removing scripting functionality is not an option. In the long run we need to find an alternative, since qtscript is deprecated, but for now I'm in favor of your solution, even if it means merging the qtscriptbindings code into Amarok.

So I'm going to open the phabricator issue (as soon as I understand what to do exactly...), could take a bit but probably scripts in amarok are going to be back, so stay tuned.

Rhinoceros commented on 2019-09-25 03:08

Thanks snack. I appreciate the effort you've put into this. Honestly, I wouldn't spend too much more time on this. It looks like it would only be a short-term fix anyway. (Realistically, I should probably just finally move to another application.) Thanks again.

snack commented on 2019-09-24 08:09

@Rhinoceros: according to what I understand, the lyrics scripting functionality has been removed due to the lack of Qt bindings:

https://phabricator.kde.org/D11862
https://phabricator.kde.org/R181:838e52b555a1c2f6b0708101707a9e890f255375

and the whole scripting as we know will be removed in future. I guess I could revert the removal of the lyrics scripting and restore it but it's a bit non-trivial and my first attempt failed. I can try again later when I will find time; in the meantime I'll try to contact upstream to inform them that I've been able to recover Qt bindings to see if this can change their plans to remove scripting at all (but I honestly don't believe it will make any difference).

snack commented on 2019-09-20 07:33

@Rhinoceros You are right, I see the same behavior with my script (BurnPlaylist). I don't know exactly how to handle it, perhaps the json misses some fields but I can't tell, since I found that template by chance and probably it is not complete. I also feel that some modification to the script and perhaps to the C++ code might be necessary (I had to adjust the script), I can try to play with UltimateLyrics but I can't promise anything. Let's hope a real expert shows up...

Rhinoceros commented on 2019-09-20 01:57

Thanks for creating this package! I tried porting Ultimate Lyrics, but could not get it working. I installed the script using Amarok's built-in manager. I then created ~/.local/share/amarok/scripts/ultimate_lyrics/script.json with the following content:

{
"KPlugin": {
"Category": "Scriptable Service",
"Id": "UltimateLyrics",
"Version": "2.06",
"Dependencies": ["Amarok2.0"],
"EnabledByDefault": "true"
}
}

However, the "Configure Scripts" preference entry is half blank. I also cannot add the script to the main GUI.

snack commented on 2019-09-15 10:10

Note: scripts need to be ported. This package only restores parts of the Amarok scripting capabilities, but old scripts probably won't work out of the box. Here's a partial list of useful tips (I'll keep it up-to-date as new information flows in):

1) Scripts are located in subfolders of .local/share/amarok/scripts/

2) A script.json file must be present inside each script folder. You have to create it manually; the content should be something like:
{
"KPlugin": {
"Category": "Scriptable Service",
"Id": "BurnPlayList",
"Version": "1.0.1",
"Dependencies": ["Amarok2.0"],
"EnabledByDefault": "true"
}
}