http://bugs.gpodder.org/show_bug.cgi?id=62
Anders Kvist <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #9 from Anders Kvist <[email protected]> 2009-01-01 19:04:21 --- The solution becomes less straight forward because gpodder consists of two groups of applications, the GUI and some console commands. I suggest the following solutions, use case sketches: 1. The system runs the GUI 2. The user starts a new instance of GUI 3. The system change focus to the 1st instance of GUI, exit() on new instance of GUI 1. The system runs a console command 2. The user starts a new instance of GUI 3. The System exit() the new instance of GUI 1. The system runs a console command 2. The user starts a new console command 3. The system exit() the new console command 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. -- 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
