Ampache service, was: Re: extragear/multimedia/amarok/src

[Nikolaj Hald Nielsen]

What I was responding to was mainly this:

>  I think it's helpful to think of Services and Collections as to
>  separate things with different goals. A service is internet content
>  that is accessible but not fully integrated in Amarok. The full
>  integrated experience is reserved for Collections, with statistics,
>  querying and such, which are supposed to implement all that "added
>  value". As anyone who tried implementing a collection would agree, it
>  is hard work to create a "complete" Collection.

which in my mind ( I might be reading it wrong ) sounded like an
argument for creating a technical distinction between services and
collections. I think this would be a very bad idea as most full
collections will likely start life as "simple" services and then
expand in features until they reach "full collection" status. I am
very against adding technical roadblocks to this process. This will
allow stuff to evolve over time which I think is very important. Take
Mp3Tunes for instance. Right now, the underlying collection is very
basic, but if we launch Amarok 2.0 with their service integrated as
well as we can ( shameless plug for the up and downloading project )
they might be willing to work with us on their API allowing us to
mature it enough that the content from here could be added to dynamic
playlists later on.

So to sum up, Services and collections are the same things. From a
collection point of view, some just support more features than others.

- Nikolaj


On Thu, Apr 3, 2008 at 10:00 AM, Mark Kretschmann <kretschmann at kde.org> wrote:
> On 4/3/08, Nikolaj Hald Nielsen <nhnfreespirit at gmail.com> wrote:
>  >  The thing about defining the difference between services and
>  >  collections I think should be done on a per case basis. All services
>  >  are collections, we just need to decide if they are complete enough to
>  >  be usable with regards to dynamic playlists and if it makes sense to
>  >  do so.
>
>  Right, and I think this is basically what Bart was saying too:
>  Deciding per case.
>
>  One example for a service that is probably unsuitable as a complete
>  collection is the Shoutcast service. There's no random access in
>  streams, so it doesn't make sense to put it in the collection.
>
>  --
>  Mark
>
>
> _______________________________________________
>  Amarok-devel mailing list
>  Amarok-devel at kde.org
>  https://mail.kde.org/mailman/listinfo/amarok-devel
>