Java viewer documentation
Brought to you by:
anton19286,
const_k
Menu
▾
▴
Java viewer documentation
|
From: Constantin K. <co...@ce...> - 2002-02-12 17:11:04
|
Hello,
I've documented all the parameters available in the Java viewer
(applicable to the next TightVNC version, 1.2.3). Here I'm pasting the
text. Please notify me about any grammatical problems, typos, unclear
places etc., to let me include a better version into the release.
Also, I don't like the "Restricted colors" parameter's name, but fail
to invent anything better. If you know a better name for this option,
please let me know. But please note that the name should be short
enough (no longer than 2--3 words).
=== cut ===
TightVNC Java viewer supports a number of parameters allowing you to
customize its behaviour. Most parameter names copy settings available from
the Options frame in the Java viewer. Both parameter names and their values
are case-insensitive, with one exception for the "PASSWORD" parameter. Here
is the full list of parameters supported in TightVNC Java viewer:
--> "HOST" (no GUI equivalent)
Value: host name or IP address of the VNC server.
Default: in applet mode, the host from which the applet was loaded.
This parameter tells the viewer which server to connect to. Normally,
it's not needed, because default Java security policy allow connections
from applets to the only one host anyway, and that is the host from which
the applet was loaded.
--> "PORT" (no GUI equivalent)
Value: TCP port number on the VNC server.
Default: none.
This parameter is required in all cases. Note that this port is not the
one used for HTTP connection from the browser, it is the port used for
RFB connection. Usually, VNC servers use ports 58xx for HTTP connections,
and ports 59xx for RFB connections. Thus, most likely, this parameter
should be set to something like 5900, 5901 etc.
--> "PASSWORD"
Value: session password in plan text.
Default: none, ask user.
DO NOT EVER USE THIS PARAMETER, unless you really know what you are
doing. It's extremely dangerous from the security point of view. When
this parameter is set, the viewer won't ever ask for a password.
--> "Encoding"
Values: "Raw", "RRE", "CoRRE", "Hextile", "Zlib", "Tight".
Default: "Tight".
The preferred encoding. "Hextile" is a good choice for fast networks,
while "Tight" is better suited for low-bandwidth connections. From the
other side, the "Tight" decoder in TightVNC Java viewer seems to be more
efficient than "Hextile" decoder so it's possible that this default
setting can be ok for fast networks too.
--> "Compression level"
Values: "Default", "1", "2", "3", "4", "5", "6", "7", "8", "9".
Default: "Default". ;-)
Use specified compression level for "Tight" and "Zlib" encodings. Level 1
uses minimum of CPU time on the server but achieves weak compression
ratios. Level 9 offers best compression but may be slow in terms of CPU
time consumption on the server side. Use high levels with very slow
network connections, and low levels when working over higher-speed
networks. The "Default" value means that the server's default compression
level should be used.
--> "JPEG image quality"
Values: "JPEG off", "0", "1", "2", "3", "4", "5", "6", "7", "8", "9".
Default: "6".
Use the specified image quality level in "Tight" encoding. Quality level
0 denotes bad image quality but very impressive compression ratios, while
level 9 offers very good image quality at lower compression ratios. If
the value is "JPEG off", the server will not use lossy JPEG compression
in "Tight" encoding.
--> "Cursor shape updates"
Values: "Enable", "Ignore", "Disable".
Default: "Enable".
Cursor shape updates is a protocol extension used to handle remote cursor
movements locally on the client side, saving bandwidth and eliminating
delays in mouse pointer movement. Note that current implementation of
cursor shape updates does not allow a client to track mouse cursor
position at the server side. This means that clients would not see mouse
cursor movements if mouse was moved either locally on the server, or by
another remote VNC client. Set this parameter to "Disable" if you always
want to see real cursor position on the remote side. Setting this option
to "Ignore" is similar to "Enable" but the remote cursor will not be
visible at all. This can be a reasonable setting if you don't care about
cursor shape and don't want to see two mouse cursors, one above another.
--> "Use CopyRect"
Values: "Yes", "No".
Default: "Yes".
The "CopyRect" encoding saves bandwidth and drawing time when parts of
the remote screen are moving around. Most likely, you don't want to
change this setting.
--> "Restricted colors"
Values: "Yes", "No".
Default: "No".
If set to "No", then 24-bit color format is used to represent pixel data.
If set to "Yes", then only 8 bits are used to represent each pixel. 8-bit
color format can save bandwidth, but colors may look very inaccurate.
--> "Mouse buttons 2 and 3"
Values: "Normal", "Reversed".
Default: "Normal".
If set to "Reversed", then right mouse button (button 2) will act as it
was middle mouse button (button 3), and vice versa.
--> "View only"
Values: "Yes", "No".
Default: "No".
If set to "Yes", then all keyboard and mouse events in the desktop window
will be silently ignored and will not be passed to the remote side.
--> "Share desktop"
Values: "Yes", "No".
Default: "Yes".
Share the connection with other clients on the same VNC server. The exact
behaviour in each case depends on the server configuration.
--> "Open new window" (no GUI equivalent, applicable only in the applet mode)
Values: "Yes", "No".
Default: "No".
Operate in a separate window. This makes possible resizing the desktop,
and adds scroll bars when necessary. If the server supports variable
desktop size, the window will resize automatically when remote desktop
size changes.
--> "Show controls" (no GUI equivalent)
Values: "Yes", "No".
Default: "Yes".
Set to "No" if you want to get rid of that button panel at the top.
--
With Best Wishes,
Constantin
|