https://bugs.gpodder.org/show_bug.cgi?id=533
--- Comment #19 from Thomas Perl <[email protected]> 2010-02-19 12:59:57 GMT --- (In reply to comment #18) > (In reply to comment #17) > > (In reply to comment #16) > > > 1. Is any info about the artist of a podcast gathered? > > > > Not yet. The podcast (channel) title is used. We can add a new field to the > > database, if you think it's important, though. > > > > 'twould be nice to have. No biggie though. > > > 2. Where should this tagger module be called? In PodcastEpisode(object)? > > > In > > > gui.py? > > > > Which parts/functions of the tagger module? Ideally, it should be optional, > > and > > if this is the case, we can put it into gpodder.model. If we just put it > > into > > gui.py, other UIs (e.g. the CLI) won't use the tagging module. > > Okay. Should gpodder.model create the tagger object on import, then > gpodder.moddel.PodcastEpisode call the tagger method at the appropriate spot? I'd rather have less global state than we already have. Can't the PodcastEpisode object create a tagger object and use it directly at the appropriate spot? Or is the creation of a tagger object so costly? See http://www.youtube.com/watch?v=-FRm3VPhseI for a motivational talk on why avoiding global state is a good idea :) -- Configure bugmail: https://bugs.gpodder.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes. _______________________________________________ gPodder-Bugs mailing list [email protected] https://lists.berlios.de/mailman/listinfo/gpodder-bugs
