http://bugs.gpodder.org/show_bug.cgi?id=74
Thomas Perl <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Replace BitTorrent with |[PATCH] Replace BitTorrent
|Transmission |with Transmission
--- Comment #3 from Thomas Perl <[EMAIL PROTECTED]> 2008-03-25 09:16:22 ---
(In reply to comment #2)
> When using an external program to download the torrents, it's not exactly
> integrated into gPodder. Whether that external program is gnome-bittorrent or
> Transmission or Azureus. The downloaded files aren't in gPodder's MP3-player
> synchronization and they don't just play when you push play.
Making gPodder act on torrent files brings two problems:
* Someone has to maintain the code (bug fixes, new torrent features)
* gPodder has to do all these funky port forwarding things for bittorrent
I think it's out of gPodder's scope to provide these services, the same way we
don't have full-blown obex send support for Bluetooth file transfers, but
simply call the right GUI tool that carries out the file sending.
If you are motivated to get this feature into gPodder, you're welcome to work
on it. I am offering mentoring and to help you find your way around the code
base and review things.
> The way I'd rather see it is that gPodder silently downloads the .torrent
> files
> when updating the feed. Then when you push Download, it begins to download the
> MP3 file(s) that the torrent points to. It does this without using an outside
> GUI program. Using an outside program for the actual downloading isn't bad.
> gPodder already does this with wget, just extend it to Transmission (command
> line version) too.
gPodder doesn't use wget since some program versions, because interacting with
a CLI tool is awkward, especially when you have a long-running process that you
want to monitor and modify (i.e. bandwidth limits, etc..). As the official
BitTorrent client is written in Python, and (I guess) it's usable as a library
(isn't that what gnome-bittorrent does?), IF we were going to do this, we would
probably going this way.
As I said, you are welcome to work on getting this feature into gPodder, and I
am offering my help showing you around the gPodder codebase.
> MP3 and other files then get put into gPodder's managed database of downloaded
> files. They can be played, synced, and removed from gPodder. It seems like a
> slick way of doing to me.
That's the only problem with my point of view: When we are "outsourcing"
Torrent downloading to external programs, it's difficult to do this kind of
tight integration with the sync process. But then again, I have yet to see a
torrent RSS feed that serves content that is to be put on iPods or MP3 players.
> Is there anything wrong with wanting to download torrent podcasts in a simple,
> no-hassle way like this? Maybe it's not easy enough to integrate. Maybe it's
> not how you want the program to work. I think it'd be nice. You don't have to
> get rid of the options of just saving the torrent files or using an external
> GUI program.
As I said, it's a feature that I deem not important enough to spend my time
working on it. gPodder needs any help it can get, and I'd be very glad if we
had this feature in gPodder, but someone else (probably you) has to work on it
and put this feature into a good shape, so that it can be included.
--
Configure bugmail: http://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
