I don't think that there would be any problem with replacing the file /usr/bin/vncviewer with a binary rather than the wrapper script for the Java VNC Viewer Client, in fact that would really be the desired solution since the binary client is more performant than the Java version and also support full-screen mode, which some people prefer.
But what Alan says is correct, we would still leave the jar file (which was there before the script was provided) in place to maintain the Applet functionality. Darren. Alan Coopersmith wrote: > Peter Tribble wrote: >> Case PSARC/2007/545 seeks to integrate RealVNC. The RealVNC viewer >> is missing from that case, apparently because vino already ships a >> binary called vncviewer. (Which is just a shell script to launch the java >> client.) >> >> What I would like to see is the proper RealVNC viewer integrated as >> vncviewer. It has the functionality, features, and performance that >> we VNC users need. > > To clarify (i.e. what I should have said earlier), the RealVNC vncviewer > is included in the sources I'm building in X, so delivering it would just > be a matter of adding it to the package and running another simple ARC > fasttrack. > > The java vnc viewer which is in vino & realvnc needs to remain for the > httpd/java applet functionality (both vino & realvnc include it, for Xvnc > packaging in Solaris/OpenSolaris, I've just linked to the copy vino already > provides instead of duplicating the .jar file on the installed system). >
