gPodder Bug Tracker – Bug 864
Autosync device when connected
Last modified: 2012-10-13 16:30:26 BST
While gPodder mostly automates fetching and keeping podcasts, it doesn't allow no-brain delivery of them (like iTunes :) So, it would be nice to have: - Watcher of Hal/Devkit dbus calls. - Some pre/post-sync actions (To be aware of no-automount enviroment, some deletions/additions defined by user) i.e. like it already does with cmd_download_complete
Also interested in this feature. It would be nice if you could configure things so you could just hook up your device and downloaded podcasts are immediately synced to it. Or, if your device was already connected, as soon as a download completes, the podcasts are immediately synced. I assume this is the same thing Maxim is talking about. (I've never used iTunes.)
I think the most sane (and extensible) way would be to provide a dbus function in gPodder that simply starts the sync process, and a dbus signal that gets sent by gPodder when the sync has been completed. This way, such a "autosync" utility/daemon can be implemented by any of you (and heavily customizable), and it would work nicely with all the requested features (including mounting before sync and unmounting/ejecting after sync).
I will very happy if this feature will add to gPodder. manual sync is unnecessary work.
Created attachment 567 [details] Additional dbus methods&signals (In reply to comment #2) > I think the most sane (and extensible) way would be to provide a dbus function > in gPodder that simply starts the sync process, and a dbus signal that gets > sent by gPodder when the sync has been completed. > > This way, such a "autosync" utility/daemon can be implemented by any of you > (and heavily customizable), and it would work nicely with all the requested > features (including mounting before sync and unmounting/ejecting after sync). (Almost forgot about this bug entry) Draft of what this would be like from gPodder's side. The only real problem (sort of) is that sync-ui window shows up. Possibly it's good idea to split things a bit, and implement syncing process more or less self-sufficient. But this could be emulated with api.py call.
Maxim: Can you update the proposed patch for gPodder 3?