https://bugs.gpodder.org/show_bug.cgi?id=864
--- Comment #4 from Maxim Prohorov <[email protected]> 2010-08-31 21:32:50 BST --- Created an attachment (id=567) --> (https://bugs.gpodder.org/attachment.cgi?id=567) 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. -- 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
