[FreeNX-kNX] Re: nx 1.5.0 + windows client 1.4.0
LROUFAIL at nc.rr.com
LROUFAIL at nc.rr.com
Fri May 20 11:27:49 UTC 2005
The Windows source for some components are available. These include the
OSS components like nxssh, nxwin, nxcomp, and nxproxy. The source for
the NX client is not available.
A simple command line client for Windows is available and is open
source. I have not yet updated it to support 1.5.0. If you are
interested you can check it out.
http://home.nc.rr.com/moznx/
- L
----- Original Message -----
From: Christopher Layne <clayne at anodized.com>
Date: Friday, May 20, 2005 5:09 am
Subject: Re: nx 1.5.0 + windows client 1.4.0
>
> What I was going off of, in regards to the client source, was this:
>
> But I guess you refering to the NX sources in general in the second
> email? Somewhere in my mind I had filed away that the windows sources
> were available somehow (I guess these two emails had made me think
> that) but if that isn't the case - I'll remove that assumption.
>
> -cl
>
> From: Gian Filippo Pinzari <pinzari at nomachine.com>
> To: NX Users <nxusers at nomachine.com>
> Date: Wed, 30 Mar 2005 14:23:49 +0200
> Subject: Re: A utility for ALT-TAB handling in NX Client
>
> Mario Juric wrote:
> > Hi everyone,
> > A couple of months ago I looked for an option in NX Client to
> pass> ALT-TAB combination(s) to the remote window manager, instead
> of being
> > captured by Windows. When I work remotely, it's really annoying
> to press
> > ALT-TAB expecting to switch to a different remote window, and
> instead> having NX minimized and a Windows window brought up.
>
> Hi Mario,
>
> we are adding an article to the KB so people looking for a solution
> will be able to find your program.
>
> Did you consider adding your code to NXWin.exe instead of using a
> separate program?
>
> /Gian Filippo.
>
>
> From: Gian Filippo Pinzari <pinzari at nomachine.com>
> To: NX Users <nxusers at nomachine.com>
> Date: Wed, 06 Apr 2005 11:49:09 +0200
> Subject: Re: A utility for ALT-TAB handling in NX Client
>
> Mario Juric wrote:
> >Hi Gian Filippo,
> > I wasn't aware that NXClient windows source was available. It
> would>have actually been simpler for me to add this directly to the
> source.> Where can I find the code, and instructions on
> compiling it under
> >Windows (can it be done with cygwin+GCC, because I do not have
> access to
> >MSVC?).
>
> http://www.nomachine.com/sources.php
>
> To build the NXWin X server you need nx-X11, nxwin and nxauth.
> Untar nx-X11 and the other components, then cd to nx-X11 and
> run make World. It uses GCC and Cygwin ;-).
>
> /Gian Filippo.
>
> --
>
>
> On Fri, May 20, 2005 at 10:53:50AM +0200, Gian Filippo Pinzari wrote:
> > Christopher Layne wrote:
> > >I did read this actually and had noticed that nxproxy is not used
> > >anymore. However - does this mean we should wait until a 1.5.0
> > >windows client is snapshotted or released? Or is it possible, via
> > >cygwin, to build one myself?
> >
> > I'm not sure I understand what you mean. The NoMachine nxclient is
> > closed source, so you can't build it yourself, but there are OSS
> > clients, like moznx or kNX. The developers of these projects are
> > reading this list and they will be happy to help you getting in-
> > volved.
> >
> > If you don't like moznx or kNX and don't want to wait NoMachine
> > releasing its client, you can start developing your own. Here is
> > a document dealing with the client server protocol:
> >
> > http://nomachine.com/ar/view.php?ar_id=AR03C00171
> >
> > /Gian Filippo.
>
More information about the FreeNX-kNX
mailing list