14:44] but the whole dynamic collection stuff depends on amarok knowing what devices are available, so i might have to delay the whole startup:( [14:45] maxx_k: it'll get those notifications [14:45] you mean, at startup? [14:45] can't the dynamic collection deal with devices added and removed during amarok's running? [14:45] kind of an important point there... [14:45] yes. otherwise there is no way to figure out which songs are actually available atm [14:45] jefferai: yes, as long as mediamanager works correctly [14:46] I think you're missing something here [14:46] mediamanager doesn't really do that much [14:46] working correctly really means it gets a dcop signal from kded [14:46] and that it can parse the fullList [14:46] jefferai: sorry, i menat the kde mediamanager [14:47] but if you want to add, i.e. an Ampache collection, neither the kde mediamanager will detect it, nor will we [14:47] it'd be a manual device [14:47] the focus is on local devices (harddisks, usb drives, CDs) atm [14:48] okay, but there needs to be support for adding and removing track collections at runtime, not just at startup [14:48] otherwise it's not that useful, if, say, a person has to restart amarok when they insert a new CD [14:48] jefferai: there is (as long as the kde mediamanager works correctly) [14:49] that's a very big assumption [14:49] for starters, many people don't have dbus/hal support compiled in [14:49] jefferai: but if the devices are not known at startup, amarok won't even be able to show the statistics in the contextbrowser [14:49] jefferai: daap won't have to be manual though :) [14:50] the kde mediamanager has a backend which uses fstab/mtab [14:50] show what statistics? [14:50] I would think it would show statistics for what's available [14:50] add a new device later, and the statistics get updated [14:50] jefferai: number of songs, number of artists [14:51] I guess I'm missing something here [14:51] but I thought the whole point of the dynamic collection was to be able to add and remove music sources at any time, and have the collection be updated [14:52] so things could be written as, say, mediadevice plugins, and have the source be listed in the collection and statistics added [14:52] and if that's not the point of it, shouldn't it be? [14:53] you are able to remove devices at any time. the problem is amarok needs the device information from the kde mediamanager to figure out which devices are available [14:54] okay, and I think that's a huge problem [14:54] originally the device manager and mediabrowser only handled autodetected devices too [14:54] andrew told me that dynamic collection already works for him, although mediabrowser doesn't [14:54] works for sourced detected from kde mediamanager [14:54] *sources [14:55] so what about my iRiver device? [14:55] what about daap? [14:55] neither of those will be detected with kde mediamanager [14:55] but they should both be seen as sources in the dynamic collection [14:56] jefferai: that's the next step. [14:56] okay [14:56] at the moment amarok only works with songs stored on the local filesystem [14:56] so, the next step is to handle devices that aren't detected via kde mediamanager, or not at startup? [14:57] devices that are not detected via kde mediamanager [14:57] okay [14:57] devices that are detected by the kde mediamanager but are not available at startup are no problem [14:57] right [14:58] or rather, right, they shouldn't be :-) [14:58] mediabrowser's funny like that [14:58] the problem for non-kde users might be that either amarok takes longer to start (because i have to wait for the kde mediamanager) [14:59] or that they don't see their songs immediatly. i hope that i can figure out a way to solve this problem, but those are the two worst cas solutions i can imagine atm [15:01] ok