Summary: | please use common library for covers (juk, amarok, ...) | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Marco Krohn <marco.krohn> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version: | 1.2-CVS | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Marco Krohn
2005-02-21 23:18:59 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. 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 :-) |