Label buttons - one more time

[Leo Franchi]

On Wed, Feb 17, 2010 at 8:00 PM, Thomas Lübking <thomas.luebking at web.de> wrote:
> Am Wednesday 17 February 2010 schrieb Leo Franchi:
>> I agree very much with this point. Various times i've wanted to quit
>> amarok (I have "resume playing on startup" on) and have it *not* start
>> playing a song. But as there is no way to "reset" amarok right now in
>> the toolbar, i've  been forced to do various hackish things so that
>> the song doesn't resume.
>
> That's actually different from Thomas' problem as you want to impact the state
> on the next startup, and not just reset the position now.

How about the context applets, that show different content when in a
"stopped" state to when in a playing/paused state? The albums applet,
for instance, shows recently added albums. That's nice to see
sometimes. There's no way to get there really without stop-after-track
and waiting for the track to end.

While we could make the applets switch on pause, I think that's a bad
idea. There could be a lot of pauses during a track and making the CV
jump around and show different information all the time would be
confusing and annoying.

> AND: this is harder to achief :-\
>
> Amarok does not quit on the window close button, but either on
> - menubar entry
> - session end (sigkill?)

Amarok quits when you close the window if you don't have the tray icon enabled.

> menubar entry is pretty easy to do:
> "Stop & Quit" or "Quit & Resume on start"
>
> controlling the behaviour on session end is however a different thing.
> the only "solutions" w/o an explicit signal that i could imagine are:
> - heuristics on the track position (e.g. < 20secs ->restart, resume otherwise)
> - heuristics on lag ( > 5h -> restart)
> - explicitly ask (has the advance that the user does not have to predict)
> - a combination of the above :-\

In all of these, you are making assumptions about what the user wants.
That's not good---you will be wrong most of the time. We want to give
them to tools to do what *they* want, not limit their options by
assuming what they want (within reason). But all the options above are
tailored to such specific use cases as to make them useless.


> --
> No offense, but what exactly is the point on "resume on start"?
> I mean, i can image it makes a lot of sense on audiobooks, but i'd rather not
> start a music tune (whether classical movement or rocksong) from the center.
>
> -> shouldn't this feature rather be genre dependent? (just asking ... )

I quit amarok sometimes in the middle of a song (hey, i'm a
developer). I like to restart it and have it play where it left off.

So you disagree with the feature. I disagree with some design
decisions in amarok too. We're a community, and we come to conclusions
that sometimes aren't to the full agreement of everyone. It happens.

leo

-- 
_____________________________________________________________________
leonardo.franchi at tufts.edu         Tufts  University 2010
leo at kdab.com                                 KDAB (USA), LLC
lfranchi at kde.org                             The KDE Project