Hello x2go list,
I've added one of my not so important mail accounts to this list to share my opinion about nx based development in the future. I don't like mailing lists because they only collect spam (to add my opinion to a already discussed topic). I've read some of the mesages here and I've taken a look to this project. I really don't think this is a good idea to work on a not compatible nx server. There are already enough free servers and clients in the world and we all should try to save a amount of compatibility to all projects. There is also a plugin for mozilla (moznx) so you won't need to develop a own. Although i like the idea of the file transport and print module of x2go (pulseaudio too is already possible with opennx). If you would change to python, i would help you to get things to work with neatx/freenx. Then you too would have no problem with the packaging, because everything you need is already done. What do you think about at minimum getting those interesting features build up in external programms, so you can use it with all nx servers (or even vncs)?
eli
On Wed, 2010-06-30 at 18:58 +0000, Eli K. wrote:
Hello x2go list,
I've added one of my not so important mail accounts to this list to share my opinion about nx based development in the future. I don't like mailing lists because they only collect spam (to add my opinion to a already discussed topic). I've read some of the mesages here and I've taken a look to this project. I really don't think this is a good idea to work on a not compatible nx server. There are already enough free servers and clients in the world and we all should try to save a amount of compatibility to all projects. There is also a plugin for mozilla (moznx) so you won't need to develop a own. Although i like the idea of the file transport and print module of x2go (pulseaudio too is already possible with opennx). If you would change to python, i would help you to get things to work with neatx/freenx. Then you too would have no problem with the packaging, because everything you need is already done. What do you think about at minimum getting those interesting features build up in external programms, so you can use it with all nx servers (or even vncs)?
<Snip> I can't speak for the developers but I think the goal is to develop something broader than any of the NX projects. I suppose it's a bit like I've taken great open source projects like iptables, iproute2, openswan, and openvpn and built a new project for a powerful network security framework in the ISCS project (iscs.sourceforge.net). So Heinz and Oleksandr have taken the NX libraries, pulseaudio, sshfs, openldap, etc., and combined them into a broader project.
We had originally planned to use NoMachine for our new company but were frustrated with the sound problems. We thought about starting a new project to combine technologies including NX to do what we needed to do but that's when we stumbled across X2Go. We haven't looked back.
I think the lack of compatibility is not about isolationism but simply because the goals of the project are bigger than simply an NX client/server. At least that's my take - John
--- John A. Sullivan III <jsullivan@opensourcedevel.com> schrieb am Mi, 30.6.2010:
Hello x2go list, <Snip> I can't speak for the developers but I think the goal is to develop something broader than any of the NX projects. I suppose it's a bit
Von: John A. Sullivan III <jsullivan@opensourcedevel.com> Betreff: Re: [X2go-dev] getting features inside neatx/freenx instead of developing something different An: x2go-dev@lists.berlios.de Datum: Mittwoch, 30. Juni, 2010 19:49 Uhr On Wed, 2010-06-30 at 18:58 +0000, Eli K. wrote: like I've taken great open source projects like iptables, iproute2, openswan, and openvpn and built a new project for a powerful network security framework in the ISCS project (iscs.sourceforge.net). So Heinz and Oleksandr have taken the NX libraries, pulseaudio, sshfs, openldap, etc., and combined them into a broader project.
Those features you've mentioned are already available - so this is nothing new/broader. And the only new feature of that new version is Session Shadowing which is working on all other nxs since years... Again this is all already done.
We had originally planned to use NoMachine for our new company but were frustrated with the sound problems. We thought about starting a new project to combine technologies including NX to do what we needed to do but that's when we stumbled across X2Go. We haven't looked back.
You should taken have a better look on the internet. As I mentioned before OpenNX can solve your sound problems without getting something not compatible.
And Perl is dead! You will only find helping people if you use better languages as C++ Perl and C. This thing here is developed like 10 years ago.
Again I would offer my help to port the good ideas to python and to make it usable for all nxs.
bye
Hi Eli,
On Mi 30 Jun 2010 20:58:54 CEST "Eli K." wrote:
Hello x2go list,
I've added one of my not so important mail accounts to this list to
share my opinion about nx based development in the future. I don't
like mailing lists because they only collect spam (to add my opinion
to a already discussed topic). I've read some of the mesages here and I've taken a look to this
project. I really don't think this is a good idea to work on a not
compatible nx server. There are already enough free servers and
clients in the world and we all should try to save a amount of
compatibility to all projects. There is also a plugin for mozilla (moznx) so you won't need to
develop a own. Although i like the idea of the file transport and print module of
x2go (pulseaudio too is already possible with opennx). If you would change to python, i would help you to get things to
work with neatx/freenx. Then you too would have no problem with the
packaging, because everything you need is already done. What do you think about at minimum getting those interesting
features build up in external programms, so you can use it with all
nx servers (or even vncs)?eli
Thanks for your statement.
I too personally was rather sad to find out that freenx upstream was
without future...
I then was happy to see that launchpad nx people changed to neatx...
Enthusiastically, I installed it right away, faced my first dependency
problems (that is Ubuntu / Launchpad) etc.
My 6 week experience with neatx is very frustrating, unfortunately. It
crashes unpredictably during login process, only a couple of session
logins are successful, session resume does neither work reliably...
I then remembered a magazine article about x2go and tried that. And I
must say, if you want to use it as normal remote desktop software, it
is the most reliable NX derivative I have met, so far. The current
stable release and probably also some future versions will still/ever
need work, of course - as any opensource project, but the approach
already works convincingly.
AND MAIN POINT: x2go is no NX server/client software... It is a
concept to setup a whole company network based on server based
computing (SBC) and thin client technology, that also utilize slim
transport features of the NX protocol. The session management is
(becoming) far more elaborate and comprehensive than normal NX
server/client applications target at.
You can also take a look at a project that utilizes x2go and creates a
greater virtualization context around it: http://www.osbd.eu.
Usability counts.
Thanks for you time, Mike
PS: I personally like Python quite well, too. If you can code Python,
Perl is not that difficult to learn. BTW: Perl with Python's code
indentation style improves readability of Perl scripts...
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
eMail-LeseSchreibStunde: wochentags 8h-10h mail: m.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Eli K. schreef:
Hello x2go list,
I've added one of my not so important mail accounts to this list to share my opinion about nx based development in the future. I don't like mailing lists because they only collect spam (to add my opinion to a already discussed topic).
Strange ideas do you have.
Why don't you use this? http://news.gmane.org/gmane.linux.terminal-server.x2go.devel
Or read this list as a usenet group. With both you can post too.
I've read some of the mesages here and I've taken a look to this project. I really don't think this is a good idea to work on a not compatible nx server. There are already enough free servers and clients in the world and we all should try to save a amount of compatibility to all projects.
You have a point, but I like the way how X2go works more. It's cleaner. The way how Nomachine NX works is strange, and not really compatible with how SSH works.
There is also a plugin for mozilla (moznx) so you won't need to develop a own. Although i like the idea of the file transport and print module of x2go (pulseaudio too is already possible with opennx).
I did not know about openNX. Interesting project.
If you would change to python, i would help you to get things to work with neatx/freenx. Then you too would have no problem with the packaging, because everything you need is already done.
If everything is done, you don't need X2go!
What do you think about at minimum getting those interesting features build up in external programms, so you can use it with all nx servers (or even vncs)?
A proxy would be nice, but not very important in my opinion. I think it's not much work for other NX clients to support the X2go way.
You say "all nx servers". In my opinion there is not even a good alternative for an OSS NX server. Only FreeNX, but that seems to be dead. And I have heard the new version of Nomachine NX will become completely different...
With regards, Paul van der Vlis.