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

[Nikolaj Hald Nielsen]

Ok, so I did misread your original post. I am sorry about that, but at
least we basically agree! :-)

With regards to gui, my own idea that I have been toying with for a
while is to always show stuff in the service browser ( if nothing
else, it gives us a powerful visual representation of the services we
support, and I use most stuff from here, so I figure some users will
as  well ) and then simply, for the services where it makes sense,
also add a small "show in collection" checkbox to the service on the
service selection page.

Smart and dynamic collections should, I think, automatically use
whatever collections are shown in the collection browser, but I think
it should be possible to manually add more ( such as Jamendo and
Magnatune )

- Nikolaj

>  I'll repeat myself w.r.t. my reply to markey so I don't break up the thread:
>
>  It isn't necessary to derive Service from something else then
>  Collection, a.k.a. a technical change. Code reuse needs to be
>  encouraged. And the "migration to full Collection" is very valid.
>
> But we do need to separate the two in our heads, and then decide if we want that
>  particular case presented to the user as either collection or service
>  (notice the lack of capitals to describe the concept).
>  So I guess I'm asking that we change our perspective to a user point
>  of view (see Celeste Paul's blog, usablility, user profile) when
>  deciding weather something is a service or a collection. As we know,
>  there are little or no technical differences.
>
>  There is also the option to let the user decide. Some possible UI sollutions:
>  * In the Internet Services pane of amarok's configuration dialog the
>  user can select in what browser the Ampache service is shown.
>  * Above the CollectionBrowser, next to the group by button, we'll put
>  small buttons with icons representing the different available
>  (running) Collections. The ServiceCollections that are active will be
>  disabled by default. The state of these buttons, should be saved
>  between sessions, offering a way to tell Amarok which Services have to
>  be loaded on startup: button enabled means load that Collection or
>  service by default.
>
>  Bart
>
>
> _______________________________________________
>  Amarok-devel mailing list
>  Amarok-devel at kde.org
>  https://mail.kde.org/mailman/listinfo/amarok-devel
>