On 01/28/2011 11:55 AM, John A. Sullivan III wrote:
<snip> Hi, Alex. Delighted to hear of the progress. I'll defer to Phil for sharing his testing results regarding stability and resizing. We'd be very happy to communicate with the vcxsrv devs about what we have collectively found.
Excellent idea. If the VcXsrv devs could see their Xserver in action w/x2go it might give them some insight into how to improve their Xserver.
I'm very concerned about the inability to use it with the plugin (we did not have the knowledge to test that ourselves). What is the likelihood of that becoming possible?
We'd like to see the VcXsrv option for the plugin as well.
Regarding the options, Phil and I have put some thought into the user interface. Please take these as suggestions rather than mandates - they are simply phrased as specs :) I would suggest the installer have options for Xming and vcxsrv with a sensible default - probably Xming until the issues with vcxsrv are resolved. There might even be a short note under the vcxsrv option to say that it is experimental. It should be possible to uncheck both options and install X2Go Client without an X Server (for those who already have their own).
+1
The X2Go Client interface, as opposed to the installer, should have QRadioButton options to use Xming, vcxsrv, or other with a QLineEdit for options. The Xming and vcxsrv buttons can be disabled or hidden based upon what has been installed. I would suggest this to just "Other" because the Xming and vcxsrv options are identical. I would really prefer to not have to configure the vcxsrv command line for each user but rather use the settings from the session parameters.
I think it might be preferable to use disabling (grey-out) as opposed to hiding things. I never liked apps that mysteriously made things appear and disappear.
Allowing use of existing installed Xserver is good idea. Like Xming (commercial).
Regards, Gerry