Oleksandr Shneyder wrote:
The look of X2Go Client is our (developers of x2goclient) vision of UI. We are very grateful for your suggestion about how x2go client should look like. But at the moment we have other opinion.
Would you accept a patch to toggle between your current UI and a more compact one, if I paid Mike or some other developer to add it? Or would such an addition have to remain a fork of your official client?
Kind Regards, Stefan
Hello Stefan,
Alex an I have discussed your feature request. Due to the huge amount of features implemented in the past, x2goclient has grown big and this way we are planning a rewrite of the client. This means that the accepted patch would only live until this new release and the whole work is lost. The new client is planned to be capable to show remote sessions embedded inside the client window.
Please be aware that you can control x2goclient perfectly by command line options. So this means it is possible to cover own ideas by using the x2goclients hidden mode and key authentication.
I really understand that x2go can bee seen as nx replacement, but this is not the projects "main focus".
If you have questions about how x2goclient can be controlled by command line options, please try x2goclient --help.
Though we don't think we will accept such a patch at the moment, we've recognized your idea as a feature request and will discuss it again by time.
Regards,
Heinz
Am 10.12.2011 13:42, schrieb Stefan Baur:
Oleksandr Shneyder wrote:
The look of X2Go Client is our (developers of x2goclient) vision of UI. We are very grateful for your suggestion about how x2go client should look like. But at the moment we have other opinion.
Would you accept a patch to toggle between your current UI and a more compact one, if I paid Mike or some other developer to add it? Or would such an addition have to remain a fork of your official client?
Kind Regards, Stefan
X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
2011/12/13 Heinz-M. Graesing <x2go-dev@x2go.org>:
Alex an I have discussed your feature request. Due to the huge amount of features implemented in the past, x2goclient has grown big and this way we are planning a rewrite of the client. This means that the accepted patch would only live until this new release and the whole work is lost. The new client is planned to be capable to show remote sessions embedded inside the client window.
Interesting, do you have a roadmap for the updated client? New features planned?
Please be aware that you can control x2goclient perfectly by command line options. So this means it is possible to cover own ideas by using the x2goclients hidden mode and key authentication.
One thing I miss (that NoMachine has) is the possibility to use files to start sessions, the session sessings are saved to files that can reside wherever you want them to be. Unless I've misunderstood how x2goclient currently works, the settings are saved in the registry and therefore not "portable" like a file is.
Cheers, Daniel
Hi Heinz, hi Stefan, hi Alex, hi Daniel,
On Di 13 Dez 2011 08:44:01 CET "Heinz-M. Graesing" wrote:
Alex an I have discussed your feature request. Due to the huge amount of features implemented in the past, x2goclient has grown big and this way we are planning a rewrite of the client. This means that the accepted patch would only live until this new release and the whole work is lost. The new client is planned to be capable to show remote sessions embedded inside the client window.
Please be aware that you can control x2goclient perfectly by command line options. So this means it is possible to cover own ideas by using the x2goclients hidden mode and key authentication.
I really understand that x2go can bee seen as nx replacement, but this is not the projects "main focus".
If you have questions about how x2goclient can be controlled by command line options, please try x2goclient --help.
Though we don't think we will accept such a patch at the moment, we've recognized your idea as a feature request and will discuss it again by time.
Such a thing as requested (X2Go client UI that looks like NX client)
can easily be implemented with python-x2go. You just need a little bit
of Python knowledge and a bit of knowledge in GUI programming
(python-qt, python-gtk, pyside, wxPython). All the hard stuff that
relates to X2Go session handling that is its client API implementation
is covered up by Python X2GO (the underlying python module of
pyhoca-gui and pyhoca-cli).
If any one is brave enough to start such a new project (an X2Go client
that looks and behaves like NX client), I am happy to give support
with the python-x2go integration into your GUI project.
I am also thinking of approaching such a project myself, but currently
there are too many other (paid) projects that need my focus.
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Am 13.12.2011 08:44, schrieb Heinz-M. Graesing:
Hello Stefan,
Alex an I have discussed your feature request. Due to the huge amount of features implemented in the past, x2goclient has grown big and this way we are planning a rewrite of the client. This means that the accepted patch would only live until this new release and the whole work is lost.
:-( What's the expected release date for this new client? Are we talking about a few weeks, a month, six months, a year?
The new client is planned to be capable to show remote sessions embedded inside the client window.
Exactly what do you mean by that? Will rootless, single-application sessions still be possible?
Kind Regards, Stefan
Hello Stefan,
Am 16.12.2011 16:19, schrieb Stefan Baur:
Am 13.12.2011 08:44, schrieb Heinz-M. Graesing:
Hello Stefan,
Alex an I have discussed your feature request. Due to the huge amount of features implemented in the past, x2goclient has grown big and this way we are planning a rewrite of the client. This means that the accepted patch would only live until this new release and the whole work is lost.
:-( What's the expected release date for this new client? Are we talking about a few weeks, a month, six months, a year?
We really can't say at the moment, but this step is definitely needed. It will not be part of the upcoming release (baikal).
The new client is planned to be capable to show remote sessions embedded inside the client window.
Exactly what do you mean by that? Will rootless, single-application sessions still be possible?
Yes - no feature will be lost. But it will be possible to embed the x2go session into the x2goclient window. This will enable things like a tabbed interface and a shared interface (session + client options visible).
Best Regards,
Heinz
Am 16.12.2011 19:18, schrieb Heinz-M. Graesing:
Hello Stefan,
Am 16.12.2011 16:19, schrieb Stefan Baur:
Am 13.12.2011 08:44, schrieb Heinz-M. Graesing:
Hello Stefan,
Alex an I have discussed your feature request. Due to the huge amount of features implemented in the past, x2goclient has grown big and this way we are planning a rewrite of the client. This means that the accepted patch would only live until this new release and the whole work is lost. :-( What's the expected release date for this new client? Are we talking about a few weeks, a month, six months, a year? We really can't say at the moment, but this step is definitely needed. It will not be part of the upcoming release (baikal).
Well, don't get me wrong, I'm not trying to hurry you here. It's just that if you come to the conclusion that it will be, say, at least six months until this new client is released, I might even decide that the feature is important enough for me to pay for its addition twice - once in the current client and once in the upcoming one. Or maybe I'll stick with the current client (plus my paid-for patch) for a while, assuming it will still be compatible with the $NEXT_INCARNATION_AFTER_BAIKAL server.
So, is there a *minimum* time frame after the Baikal release where you can more or less guarantee that a new client will *not* be released, and old clients will continue to function with new server releases?
Kind regards, Stefan
Am 16.12.2011 19:18, schrieb Heinz-M. Graesing:
Hello Stefan,
Am 16.12.2011 16:19, schrieb Stefan Baur:
Am 13.12.2011 08:44, schrieb Heinz-M. Graesing:
Hello Stefan,
Alex an I have discussed your feature request. Due to the huge amount of features implemented in the past, x2goclient has grown big and this way we are planning a rewrite of the client. This means that the accepted patch would only live until this new release and the whole work is lost. :-( What's the expected release date for this new client? Are we talking about a few weeks, a month, six months, a year? We really can't say at the moment, but this step is definitely needed. It will not be part of the upcoming release (baikal).
In addition to my previous post, where I asked if there's a minimum life expectancy for the current/upcoming client, I would like to present you with a few screen mockups of my suggestion, so everybody can easily visualize what I'm talking about.
Again, I fully understand that you need the current look of the X2Go client for your thinclient approach, but a commandline switch or a compile-time option that triggers when the target platform is Microsoft Windows, and changes the look to what I'm suggesting here, would be nice.
Please see the attached PDF for screenshots. (It's 106kb in size, so I hope it gets through).
Kind Regards, Stefan
Hi Stefan,
On Fr 16 Dez 2011 16:19:07 CET Stefan Baur wrote:
Am 13.12.2011 08:44, schrieb Heinz-M. Graesing:
Hello Stefan,
Alex an I have discussed your feature request. Due to the huge amount of features implemented in the past, x2goclient has grown big and this way we are planning a rewrite of the client. This means that the accepted patch would only live until this new release and the whole work is lost.
:-( What's the expected release date for this new client? Are we talking
about a few weeks, a month, six months, a year?The new client is planned to be capable to show remote sessions embedded inside the client window.
Exactly what do you mean by that? Will rootless, single-application
sessions still be possible?
How about supporting an X2Go plugin project write for remmina
client??? Have you taken a look at remmina?
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Am 17.12.2011 23:12, schrieb Mike Gabriel:
How about supporting an X2Go plugin project write for remmina client??? Have you taken a look at remmina?
I had never heard of that before, but from the screenshots and download page, it's only available for Linux. I need a client that works on Windows and Mac OS X, too. Plus, I'd prefer to stay as close to the plain, native X2Go server/client-system as possible. Using an "alien" client means that whenever you run into functional issues (say, after a server upgrade, or a seemingly unrelated library upgrade on the client), the developers of the native system are less likely to be willing and able to help you than if it affects their native client.
-Stefan
On Sa, Dez 17, 2011 at 23:12:36 (CET), Mike Gabriel wrote:
[...]
How about supporting an X2Go plugin project write for remmina client??? Have you taken a look at remmina?
Remmina sounds (and looks!) pretty promising. On the first look, it looks like it has a sane architecture. However, integrating x2go into remmina properly requires to re-implement the complete x2go session handshake logic in C with glib/gtk, which is not an easy task if you are not familiar with glib/gtk.
Still, I think for our purposes it looks like remmina might be an excellent architecture for using in a PXE-booted thin client.
Cheers, Reinhard.
-- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4