After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 728067 - Unable to grab the PlayOrder from Python
Unable to grab the PlayOrder from Python
Status: RESOLVED OBSOLETE
Product: rhythmbox
Classification: Other
Component: Plugins (other)
3.0.x
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-04-11 22:56 UTC by foss.freedom
Modified: 2018-05-24 18:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description foss.freedom 2014-04-11 22:56:52 UTC
I initially posted this on the mailing list...

Having looked at this further, I've convinced myself that it is impossible to actually find the playorder class for the playing source.  I'm hoping I'm wrong.

The shell_player has a string play_order "linear", "shuffle" etc property

You cannot actually translate this to obtain the actual play_order class.

Looking in rb_shell_player.c - the play_order classes are all initialised and hashed - but there doesnt appear to be a method to get that hashed play_order instance from python.  Please can a method be added to rb_shell_player called "get_play_order" to obtain the playorder instance?

The reason for the request is that I would like to write a plugin to obtain the next proposed song that would be played.  In fact - I'm hoping that the playorder actually gives me the next few songs to be played - I want to implement something like the iTunes "up next" functionality giving the user the ability to see what next few songs will be played.  The shuffle makes it currently impossible to see the next few songs directly from the querymodel of the playing source.
Comment 1 Jonathan Matthew 2014-04-12 09:33:46 UTC
RBPlayOrder and its subclasses are an implementation detail that is not exposed to plugins, and I'm not going to expose it because there's not much you can usefully do with them, and most of that you can do other better ways anyway.

Giving plugins access to future play ordering is probably a worthwhile thing to do, but I can't see a good way to do it with the way play ordering works now. Some day I'll rewrite it all to make things better.
Comment 2 foss.freedom 2014-04-12 11:30:39 UTC
ok - cheers for the feedback Jonathan.  I guess this is a wishlist item then.

If you have any further thoughts in the future on the best way to implement the "up next" capability, the just shout.  As I said, I'm happy to write a python plugin - either as part of the main source or as just an external plugin.
Comment 3 GNOME Infrastructure Team 2018-05-24 18:13:55 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/rhythmbox/issues/1336.