2.4 planning

[Marius]

Hallo,

on Thursday 23 September 2010 15:54 Bart Cerneels <bart.cerneels at kde.org> 
wrote:
> Now I'm tempted to bring up the big Play Queue vs. Playlist debate
> again which would simplify both EngineController (back to the simple
> phonon wrapper or even less) and PlaylistModel. The complexity would
> be entirely gone if we only determine playback order when adding to
> the Play Queue i.e. completely remove our current queue feature.
> In addition PlaylistModel and it's views could be used for other
> purposes as well (Saved Playlists specifically) because it wouldn't
> contain any of the nasty feature-creep bits.
> 
> Bart

I also missed the Queue Manager in the beginnings of Amarok2, but after I had 
thought about it and long discussions on this list I think the problem is not 
the missing QM, but the fact that for many people (including me) the current 
playlist tends to become a container for anything you want to "remember" for 
playing later. Thus it grows uncontrolled and it becomes hard to "queue" songs 
by rearranging their order. A possible solution I would really love to see is 
consists of two things:
1) a dynamic playlist, which feeds the current playlist from songs of a static 
playlist (sounds complicated, I hope you understand me :)
2) detach the saved playlists view from the collection view, so you can show 
them side by side and drop songs directly from the collection or file browser 
into saved playlists. That would prevent people from misusing the current 
playlist as a container for everything.

If you use the "dynamic playlist from static playlist" approach, you have only 
a few tracks in the current list at a time, and if you want to "queue" a song, 
it should be easy to place it directly behind the playling one.

Some nice ideas are also in the QM bug: 
https://bugs.kde.org/show_bug.cgi?id=198180

-Marius