Bug 99951 - please use common library for covers (juk, amarok, ...)
Summary: please use common library for covers (juk, amarok, ...)
Status: RESOLVED INTENTIONAL
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 1.2-CVS
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-21 23:18 UTC by Marco Krohn
Modified: 2006-06-11 12:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Krohn 2005-02-21 23:18:59 UTC
Version:           1.2-CVS (using KDE 3.3.92 (beta2), compiled sources)
Compiler:          gcc version 3.3.5 (Debian 1:3.3.5-8)
OS:                Linux (i686) release 2.6.7-1-k7

I am using amarok as well as JuK. Both have their strength thus I keep switching. What I love about both applications is that they show the covers of the albums. Unfortunately juk and amarok do not seem to share the same backend for cover handling. That means:

* the covers are stored in different directories
* they follow a different naming scheme (unfortunately the amarok file names do not say anything about their content)
* amarok allows fetching covers from amazon, juk uses google images (which find less, but better images)

It would be great if amarok, Juk and others (noatun?) developers could unite and develop one backend for cover handling in the same spirit as taglib. This could also lead to a new freedesktop standard. 

Note: I have _not_ filed a seperate wishlist item for JuK in order to not polute the bug database.
Comment 1 Mark Kretschmann 2005-02-22 10:26:10 UTC
Sorry, we can't do this. Using Amazon's webservices we are bound to their special licensing terms. Allowing other applications access to the files would mean a breach of their terms.
Comment 2 Andreas Silberstorff 2005-05-18 17:51:38 UTC
What about plugable covermanagers? Not in the near future, but as a point on the wishlist I would vote for it (if my c++ capabilities where more advanced I would even like to code for it).

I could imagine a covermanager plugin that would be shared with juk (or whosoever, freedesktop.org standard sounds nice) and that does NOT use amazon, so I am NOT forced to download my covers anew over my small bandwith every third month.

Of course a plugin using Amazon's webservice would have to prevent access to the covers by other apps then the one that was using the plugin for fetching. So writing that plugin would be more demanding. That plugin would have to store the covers app specific and even protect the contents (could store the covers in a crypted dir and show it only when viewed with the plugin used by the same app that demanded the download).

The google-plugin would be easier to write as it would be allowed to share the downloaded contents :-)