[X2go-bugs] [Tickets #60] Re: Restart from desktop

[bugs at x2go.org]

Ticket URL: http://code.x2go.org/horde4/whups/ticket/?id=60
------------------------------------------------------------------------------
  Ticket             | 60
  Updated By         | Mike Gabriel <mike.gabriel at das-netzwerkteam.de>
  Summary            | Restart from desktop
  Queue              | pyhoca-gui
  Version            | HEAD
  Type               | Enhancement
  State              | Feedback
  Priority           | 1. Low
  Operating System   | 4
  Owners             | Mike Gabriel
------------------------------------------------------------------------------


Mike Gabriel <mike.gabriel at das-netzwerkteam.de> (2011-03-11 15:32) wrote:

Hi Dick,

as I understand we are talking about running the CVix ,,application''  
in rootless mode. The is the word ,,application'' relates to a set of  
rootless X2go session windows that are controlled by PyHoca-GUI.

> After the initial start of pyhoca-gui, the program has started and  
> shows in the system tray. Most of the users will not see that icon  
> (and not understand what it stands for). So, after they quit the  
> application, they will expect the application to restart when they  
> click the icon on the desktop anew. When I do that, nothing happens,  
> because pyhoca requires you to click the icon in the system tray. It  
> is very important that the user can restart the application by  
> clicking the desktop icon.

There are a few ways to solve this:

1.

   o use PyHoca-CLI instead of PyHoca-GUI (start a single session till  
it finishes or crashes)

For PyHoca-CLI to be usable again I have to run some tests...  
PyHoca-GUI shall not only be a proof of concept. It will be maintained  
as long as Python X2go is maintained by me. However, currently it is  
slightly broken because of focus on PyHoca-GUI

2.
   o let a message window pop up if you start a second instance of  
PyHoca-GUI (which is
      not allowed). This message notifies the user about the systray icon...

This is simple and I will in short create its own enhancement request  
in this tracker.


3.
Another possibility would be to close PyHoca-GUI after sessions have  
been disconnected:

   o by adding a cmdline option to PyHoca-GUI: --exit-on-disconnect

Which approach do you prefer?