[FreeNX-kNX] FreeNX development still active

[Alastair Johnson]

If we weren't trying to maintain compatibility with the NoMachine client 
(which most people use) that might work. It could be provided as an option 
for open clients like George Wright's QtNX where we can change the behaviour 
of the client as well as the server. With the NoMachine client we have to 
live with the restrictions it imposes. This is of course a good reason for 
helping out with QtNX improvements ;-)

I suspect a method involving CUPS is the right way to go about printing 
transparently, but we may have to give FreeNX the right to create printers on 
the server's system CUPS. I also think we could include more printing options 
than we do now as one method probably won't suit everybody.

We should probably find out what people want from printing before going much 
further though. Any ideas, or usage scenarios?

On Wednesday 24 January 2007 18:08, Cardon Denis wrote:
> Hi Johnson et al.,
>
> > The RPMs for Fedora use NX 2.1.0 AFAIK, and are stable.
> >
> > Some development on printing has happened on list recently, but none of
> > those involved have SVN access. Unfortunately CUPS 1.6 breaks that. Other
> > than that my experience is that it just works.
>
> about printing, I was wondering how hard it would be to implement the
> following type of printing :
> - on the freenx server, instead of printing to a cups printer, I print
> to a pdf file in a specific folder (let's say $HOME/tmp/freen-printjob).
> This is already possible in most of the gnomified/kdeified apps and
> should be quite easy to be extended to other apps.
> - a pooling (or a push) realise there is a pdf file in the
> $HOME/tmp/freenx-printjob and transfert the job through tunneling on the
> established ssh connexion on the freenx client box in the
> $HOME/tmp/freenx-localjobs directory
> - acroread is launch on the freenx client side and open the pdf file in
> the $HOME/tmp/freenx-localjobs directory
> - the user can choose among all the local printer on his freenx client
> for printing
>
> This scenario seems to be quite doable and quite straight forward. It
> should solve most common printing task (there is no ppd info on server
> side, but anyway 99% of printing needs are just plain A4/letter, so
> shouldn't be much of a issue). What do freenx gurus think about it?
>
> Cheers,
>
> Denis
>
> > On Saturday 20 January 2007 14:13, Holger Mense wrote:
> >> Hi,
> >>
> >> is the development of FreeNX still active? The last SVN commits are 6
> >> months old, the last offical release (version 0.4.2) was 1.5 years ago.
> >>
> >> Is there any stable code available, that works with NX 2.1.0 backend and
> >> client?
> >>
> >> Sincerly
> >> Holger Mense
> >
> > ________________________________________________________________
> >      Were you helped on this list with your FreeNX problem?
> >     Then please write up the solution in the FreeNX Wiki/FAQ:
> >   http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
> >          Don't forget to check the NX Knowledge Base:
> >                  http://www.nomachine.com/kb/
> >
> > ________________________________________________________________
> >        FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
> >       https://mail.kde.org/mailman/listinfo/freenx-knx
> > ________________________________________________________________