On 12 Mar 2009, at 00:36, Erik Massop wrote:
Hej,
If a client shows songpool S instead of playlist P, then the user sees
the active entry jumping through S. This looks just like random-play.
(No client has implemented such a view on pshuffle however...)
Ah yes that's cool. I will add that S can be any playlist, so it's
really a "virtual random" applicable to anything including playlists.
An advantage of this approach over really jumping through a playlist
is that you can still go back to a previously played entry.
And you can know what's going to play next, too. Sort of a random
queue (think 'Q' queue in XMMS1).
We have purposely removed the "random playback" feature because we
wanted to promote party shuffle instead. I think there should still
be
some way to activate it, even if it's not done by the server itself.
We could hack nycli to show pshuffle-playlists like explained above?
I think we'd still like regular pshuffle, but if we allow a "random
mode", we could do that yes.
Unfortunately, service clients are not merged yet and we shouldn't
make any assumption that it will be before GSoC. So such a project
should be done as a standard client initially, and we should
determine
whether it still makes sense to have it in these conditions (other
clients would not be able to talk to it).
What do you mean by "other clients would not be able to talk to it"?
That only the server would talk to the playlist-updating service-
client?
No, that until service clients are merged, nobody can talk to playlist-
updating clients, so they'd act in isolation (except through config
vals perhaps). Just a remark in terms of making this a GSoC project
for this year.
I quite like this idea of making it a UI/client abstraction, which
would mean there is much less work needed too. I still think the
set_next function is annoyingly limited, but that's not necessarily
related.
--
Sébastien Cevey
--
_______________________________________________
Xmms2-devel mailing list
Xmms2-devel@lists.xmms.se
http://lists.xmms.se/cgi-bin/mailman/listinfo/xmms2-devel
