http://bugs.gpodder.org/show_bug.cgi?id=62
--- Comment #10 from Thomas Perl <[email protected]> 2009-01-03 11:58:40 --- (In reply to comment #9) > I'm not sure about how the best behaviour of gpodder will be in the following > case. I don't know if it is useful to be able to run console commands when the > GUI is open, or not? > > 1. The system runs the GUI > 2. The user starts a new console command > > Hence I see two possibilities > > 3a The system pass the console command into the GUI (execute it) > 3b The system exit() the console command (don't execute it) > > Will be glad to get some tip and comments on this. I think "3a" would be the right way to do it, so one can set up a cron job (i.e. download all episodes, etc..) and have it executed no matter if the GUI is running or not (if not, just run as normal console app, if it is running, show the progress of the action in the GUI). With gPodder providing D-BUS entry points for "show window", "update feeds", etc.. the console command can check if the gPodder D-BUS object is running and call "update", etc.. on it or simply carry out the command on the console. Also then, we would also allow other programmers to interface with gPodder through D-BUS, which is a nice feature for developers, I think :) -- 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
