Return Playdarcollection from "the Dead" ;)

[Mark Kretschmann]

On Sun, Mar 20, 2011 at 10:07 PM, Stefan Derkits <stefan at derkits.at> wrote:
>>> Means, that a User could (if he/she wants) enable Playdarcollection from
>>> the new Plugins Page in Settings.
>>> It would be a pitty to leave the PlaydarColllection Code
>>> "force-disabled" even in 2.4.1
>>
>> As far as I understand, the Tomahawk Player [1] started by Muesli is
>> basically a new implementation of Playdar (the original code base is
>> dead). Muesli said, Tomahawk is fully compatible with Playdar:
>>
>> [1] http://tomahawk-player.org
>>
>
> so that doesn't answer the Question of what should happen with the
> PlaydarCollection in and post 2.4.1 (an old Mail said the Reason why it
> is disable was that User experienced slower Startup times) ... could we
> reactivate it now that Users can enable/disable it on their own?

It doesn't answer it, but it provides a new perspective: Before
Tomahawk, the Playdar collection was Vaporware, because its dependency
did no longer exist. That made it absolutely useless, slow start-up or
not. Including completely useless features in any form does not make
any sense.

That said, Tomahawk is at version 0.0.1, so I'm not sure it justifies
as "usable Playdar replacement". Also, it might be hard for the user
to understand what "Playdar" actually is, because it only exists as a
concept. Tomahawk says it's "Playdar Compatible", but who will know
what that means? Ergo, we have a discoverability problem here.

I can't say if the sum of all that is enough for making a decision.
Let's ask the others here ;)

-- 
Mark Kretschmann
Amarok Developer, Senior Software Engineer at Nokia
Fellow of the Free Software Foundation Europe
http://amarok.kde.org - http://fsfe.org - http://nokia.com