[Amarok] Move Playlist Layout config from toolbar to main m

[Thomas Pfeiffer]

> I'll try to make it short ;-)
> 
> My 4¢
> ------
> a) the playlist environment needs to be improved
> b) the toolbar has become a kitchen sink (unrelated to very recent changes)
> c) toolbar configurability is nice, but won't prevent users from
>  potentially have to recreate a sink
> 
> Analysis:
> ------
> The playlist environment contains elements of three categories:
> 1. Global (mode) settings (sort order, play mode, playlist layout)
> 2. Playlist editing (wipe, undo, redo, save)
> 3. Playlist navigation (show active track)
> 
> Proposal:
> ------
> Just group by category
> 
> - ABOVE the playlist:
> [PLAYMODE] [spacer] [SORTING] [CLEAR sorting button] [stretch] [LAYOUT]
> 
> - BELOW the playlist:
> [stretch] [WIPE] [stretch] [UNDO] [REDO] [stretch] [SAVE] [stretch]
> 

> - The "Show active track" button actually belongs to the scrollbar, esp. as
>  it makes no sense unless there's one, so it should be either
> 	° above or below the scroller or
> 	° a line or icon inside the scroller (this is imho more elegant, but has
> a flaw as the slider has a minimum size, i.e. could cover the indicator
> allthough the current track is not visible - for rather long playlists)
> 
Especially the positioning of "show active track" button sounds logical. The 
others make sense, too. We'd have to see if everything would fit well overall, 
though.

> Cheers,
> Thomas
> 


> Btw (slight OT)
> I'd strongly recommand to consistently place filterlines BELOW their
>  attached content)
> References:
> This is already present for the fileview content and the way it's done in
> dolphin, gwenview, firefox, konqueror, katepart (as "find" is the closest
> match to "filter" in this context) and actually kmail is the only prominent
> exception i'm aware of atm.
> In case of worries about mouse ways - that's what focus buddies were
>  invented for ;-P
I don't agree here. 

- In dolphin (as well as in kopete), the search bar is moveable. On my system 
both are currently positioned above the content, though I'm not sure if maybe 
it was me who moved it there in dolphins case (I'm sure I didn't move it in 
kopete). 
- In firefox, konqueror and kate (and okular, for that matter), the search 
lines are displayed on demand whereas in kontact, doplhin, kopete and amarok 
the search/filter lines are always present. 
- In firefox, konqueror, kate and okular the lines are used for searching 
(outcome: Parts of the text are highlighted) whereas in kontact, kopete and 
amarok they are used for filtering (outcome: Part of the content is hidden). 

For these reasons, I think that although kontact is the only other example for 
a filterline being placed above the content (I'd count dolphin and kopete for 
neither side), it is closer to amarok in this regard than the other 
applications mentioned. So in order to find out if placing a filterline (not a 
searchline) below the content would increase consistency, I'd suggest to look 
where other *filter*lines are positioned instead of looking for apps with on-
demand *search*lines

Regards,
Thomas
> _______________________________________________
> Amarok-devel mailing list
> Amarok-devel at kde.org
> https://mail.kde.org/mailman/listinfo/amarok-devel
>