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 334884 - hierarchical podcast view
hierarchical podcast view
Status: RESOLVED OBSOLETE
Product: rhythmbox
Classification: Other
Component: Podcast
HEAD
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
: 454185 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-03-17 14:23 UTC by William Jon McCann
Modified: 2018-05-24 11:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description William Jon McCann 2006-03-17 14:23:27 UTC 
It has been discussed a bit in a few places so I thought to give the issue a home.

http://bugzilla.gnome.org/show_bug.cgi?id=327372#c11
http://bugzilla.gnome.org/show_bug.cgi?id=327372#c13

Jonathan, I think you mentioned somewhere else that you/we have already started working toward this, is that right?  What else would need to be done?
Comment 1 James "Doc" Livingston 2006-03-17 23:09:30 UTC 
The biggest thing would be to make code not use RhythmDBQueryModel directly, to allow other model implementations.

RhythmDBQueryModel is a GtkTreeModel with a few additional methods, so one option would be to create an interface called RhythmDBEntryModel (which derives from the GtkTreeModel interface and adds the methods) and rename the RhythmDBQueryModel class to RhythmDBLinearEntryModel or something. We could then write a RhythmDBPropertyGroupedEntryModel which takes a property id to group the entries on.
Comment 2 Jonathan Matthew 2007-07-08 09:09:39 UTC 
*** Bug 454185 has been marked as a duplicate of this bug. ***
Comment 3 GNOME Infrastructure Team 2018-05-24 11:29: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/168.