[FreeNX-kNX] [FreeNX and "Google Summer of Code"] Proposal 7: "KDE NX client"

[Kurt Pfeifle]

--------------------------------------------------------------------
Proposal 7: 
Create, complete, test and polish a fully integrated KDE version 
of an NX client
--------------------------------------------------------------------

KDE currently only has a "proof of concept" implementation of an NX 
client (knx in kdenonbeta) that was hacked together in 2 half days 
during LinuxTag 2004. This project aims for a complete NX client 
which fully integrates into KDE.
 
Essential parts of this project:
-------------------------------- 
* the new KDE NX Client must work for FreeNX as well as for 
  NoMachine NX servers. 
* the new KDE NX Client must support all the features the 
  "free-as-in-beer" version of the NoMachine NX client supports 
  (SSL encryption, audio tunnelling, CUPS printing, file sharing, 
  suspending a session, terminating a session, re-connecting to a 
  suspended session, some common fixed as well as custom display 
  sizes, establish remote KDE as well as Gnome sessions, flexible 
  port-forwarding, JPEG and PNG compression for bitmaps, 
  configuration of cache sizes for RAM and harddisk, configuration 
  of l10n-ed keyboard settings, and more) . 
* the new KDE NX Client must at least work as a standalone 
  application. 
* the new KDE NX Client must at least provide the stubs to 
  integrate the current "KDE remoting" technology (a.k.a. known as 
  "krdc" or "KDE Remote Desktop Connection") which supports pure
  RFB/VNC and RDP/rdesktop sessions into one interface. 
* the new KDE NX Client should preferrably blend as much as 
  possible into KDE's core technologies: investigate the 
  possibility to run different NX sessions in a "tabbed window 
  mode", preferrably in a tabbed Konqueror; investigate the 
  possibility to create an "nx_kioslave" that allows to start NX 
  sessions via an "nx://"-URL; investigate the usefulnes of dcop 
  for the KDE client. (These investigations should be at least 
  documented with pros and cons, and implemented if the "pros" are 
  compelling where the "cons" are minor). 
* the new KDE NX Client should preferrably be based on the new 
  "nxclientlib" library 
* the new KDE NX Client should be able to run without a window 
  manager, i.e. be usable in thin client situations as replacement 
  of or as an option for KDM 
* the new KDE NX Client must be fully documented (i.e. a user 
  manual that explains all options in the GUI) 
* the new KDE NX Client must be fully "WhatsThis"-enabled (i.e. 
  each widget must have a comprehensible WhatsThis help entry) 

Mentors: Aaron J. Seigo, Kurt Pfeifle

Reply ASAP if you are interested, so you can get approval before the
14th of June.