Hey
I'm Anmol, and I'm submitting a proposal on revamping Amarok's scripting interface.

Here's the link to my proposal:
http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/darthcodus/1

I was wondering what else the Amarok Scripting Community would like to see integrated into Amarok Script, and if there's anything in my proposal they would like changed.

No problem for asking now, you might also link to the bug reports you already identified as being relevant to the project

FWIW: I moved the topic around a bit so it also shows in the Development section and made it sticky in the General Discussion section, so you have more eyes to see

Thanks

The relevant bug reports are already detailed in my proposal. Should I paste them here?

DarthCodus wrote:The relevant bug reports are already detailed in my proposal. Should I paste them here?

I don't think it is needed.

Also I would name it "Amarok Scripting Interface" or "Amarok Scripting API" because "Amarok Script" is too vague.

strohel wrote:

DarthCodus wrote:The relevant bug reports are already detailed in my proposal. Should I paste them here?

I don't think it is needed.

On the contrary, since the forum users and script writers don't have access to the proposal, a list here would be nice to have. To see the proposal one has to be either a mentor in GSoC or subscribed to the amarok-devel mailing list, so why not just copy-paste the list of bug reports that are relevant to the task here.

Mamarok wrote:On the contrary, since the forum users and script writers don't have access to the proposal, a list here would be nice to have. To see the proposal one has to be either a mentor in GSoC or subscribed to the amarok-devel mailing list, so why not just copy-paste the list of bug reports that are relevant to the task here.

You're right. (notice that Anmol made the proposal public - even I can see it, but even though copying the bugs here won't hurt)

Here's the list of bug reports mentioned in my proposal:

Bug 183497 - Scripting API to add a context menu to everything representing a song or file
Bug 187957 - Create submenus from the Scripting interface
Bug 176663 - Installing a new script requires a restart of amarok
Bug 23271 - Provide scripting interface to customize collection display (filter, sort, group, displayed tags, etc.)
Bug 205509 - Add dbus functions to update podcasts and download podcast tracks
Bug 176663 - Installing a new script requires restart of Amarok
Bug 299218 - Amarok script API track signals are unreliable, undocumented
Bug 150610 - Add Dynamic Playlist API for scripts
Bug 279701 - Scripting support for the equalizer
Bug 243096 - Load a saved playlist in database from script
Bug 313283 - Amarok Scripting API lacks documentation
Bug 245647 - Programmatic access to data objects in QtScript

Hi,
maybe too late now as the summer has already started but one thing I would like to see, is a way for scripts to add content to the context view. Especially for my script Amarok Reader this would obviously be really useful. But also for e.g. Rating Statistics and all others that add some kind of visual features.
I understand there have been plans some time ago:
- from the Scripting Howto 2.0: "There is currently no way to interact with the context view (middle pane) via scripts but there are plans to change this"
- also there is a (rather dead) category 'Amarok Applets' on kde-apps.org which seems to have aimed at this already
Can anybody give an update on what has become of this or if there have been any discussions at all about this recently?
thx,
camico

Hey, thanks for posting. And no, it's not late
A scriptable context view sounds great. Though it isn't really isn't on my todo list currently, I'll be willing to work on it after discussing this with my mentor. (Hey Markey, you reading this?)

Shouldn't this thread be unpinned after 7,5 years of inactivity?

7,5 years? Really?

Well, the last post before mine is from Sun Jul 07, 2013 2:41 pm, this makes it almost 8 years, not?

woah, you mean you already live in the year 2021? Don't exaggerate, this post is 1,5 years old, not 7.5 or 8, seriously.

Ah, my bad... I took the 07 from Jul 07 as the year... Sorry for the spam...