Bug 165469

Summary: Add KIO support for the collection scanner
Product: [Applications] amarok Reporter: Robert Grønning <slimg>
Component: generalAssignee: Amarok Developers <amarok-bugs-dist>
Status: RESOLVED NOT A BUG    
Severity: wishlist CC: faplap
Priority: NOR    
Version: 2.0-SVN   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Robert Grønning 2008-07-01 10:05:50 UTC 
Version:           1.4.9.1 (using KDE 4.0.5)
Installed from:    00

Currently the collection scanner in Amarok is limited
to the local filessytem (/) only, Amarok would really
gain from implementation KIO into the collection scanner.

What is KIO? (wikipedia):
-------------------------
KIO (KDE Input/Output) is part of the KDE architecture.
It provides access to files, web sites and other
resources through a single consistent API. Applications,
such as Konqueror which are written using this framework
can operate on files stored on remote servers in exactly
the same way as they operate on those stored locally.
This allows for a file browser like Konqueror to both be
a highly versatile and powerful file manager as well as
a web browser.
-------------------------

Gains:

 * Amarok would ex. be able to detect if it
   looses connection with the collection,
   and prevent the database from beeing flushed.

 * Several computers with Amarok could share the
   same MySQL collection database as the
   collection-path would be the same for each computer.

 * No more need to manually maintain the ***fs mointpoint.

There is a whole world outside localhost, please do not limit us from it ;)
Comment 1 Lydia Pintscher 2008-07-01 10:08:08 UTC 
Well the reason for this is that the engines we used could not handle KIO slaves.
In Amarok 2 this might change due to Phonon. Someone with a better knowledge of Phonon needs to comment on that though.
Comment 2 Lydia Pintscher 2008-07-01 10:10:37 UTC 
*** Bug 142006 has been marked as a duplicate of this bug. ***
Comment 3 Mark Kretschmann 2008-07-01 10:20:32 UTC 
That's not going to happen because TagLib does not use KIO. However, there's currently a Nepomuk collection in development for Amarok 2, which may (or may not) support KIO. Depends on how Strigi works.
Comment 4 Robert Grønning 2008-07-01 11:07:15 UTC 
I do not quite understand why TagLib should be KIO-capable (Might be to my lack of experience with both).

Also afaik Amarok already have KIO-support when not playing from the collection browser, or am I mistaken?
Comment 5 Jeff Mitchell 2008-07-02 14:12:29 UTC 
 * Amarok would ex. be able to detect if it 
    looses connection with the collection, 
    and prevent the database from beeing flushed. 

Amarok already does this.

  * Several computers with Amarok could share the 
    same MySQL collection database as the 
    collection-path would be the same for each computer. 

Amarok already does this.
Comment 6 Robert Grønning 2008-07-02 14:52:30 UTC 
Amarok already does this 1: How do Amarok do this? Only way I know is to turn off the collection monitoring, but then you will loose that feature for this, that would not really be an improvement.

Amarok already does this 2: Again, how? Only way I know is if all the Amarok MySQL-clients mounted the music collection from the server in the same folder at their localhost, and they still need root priveleges (not everyone has root priveleges or is familiar with FUSE).
Comment 7 Saurabh Asthana 2008-07-02 18:42:55 UTC 
The MySQL support is so thin as to be essentially non-existent. I
shouldn't have to know how to setup MySQL, manage NFS shares, etc., in
order to maintain a shared music collection.

On 2 Jul 2008 12:52:31 -0000, Robert Gr