Update README

This commit is contained in:
Stephen Heumann 2016-09-30 00:24:27 -05:00
parent 1e7b5a13fe
commit 4788d6ac0c
3 changed files with 18 additions and 8 deletions

BIN
._README

Binary file not shown.

13
README
View File

@ -56,15 +56,20 @@ Edit->Send Clipboard: Transfers the contents of the IIgs clipboard to the server
VNC Server Interoperability
VNCview GS should be able to connect with any VNC server that fully implements the RFB protocol as defined in RFC 6143 or earlier compatible specifications. Here is a list of some VNC servers; many others are also available.
Microsoft Windows, *nix (X11), and OS X: RealVNC, http://www.realvnc.com/
OS X: Vine Server (OSXvnc), http://www.testplant.com/dlds/vine/
*nix (X11) and OS X: x11vnc, http://www.karlrunge.com/x11vnc/
Microsoft Windows, *nix (X11), and macOS: RealVNC, http://www.realvnc.com/
macOS: Vine Server (OSXvnc), http://www.testplant.com/dlds/vine/
*nix (X11) and macOS: x11vnc, http://www.karlrunge.com/x11vnc/
x11vnc is a good option, because it supports server-side display scaling, which is useful to fit more information on the IIgs screen.
VNCview GS does not work with the Screen Sharing functionality in OS X, because the Screen Sharing server does not support the pixel format that VNCview GS requires. The above servers can be used instead.
VNCview GS does not work with the Screen Sharing functionality in macOS, because the Screen Sharing server does not support the pixel format that VNCview GS requires. The above servers can be used instead.
Version History
1.0.2
Support for typing non-ASCII characters
Smoother transitions between 640 mode and 320 mode
Improved UI responsiveness during raw pixel decoding
1.0.1
Improved clipboard transfer routines, with support for non-ASCII characters
Improvements to help the display "catch up" when content is changing rapidly

View File

@ -64,16 +64,21 @@ VNC Server Interoperability
---------------------------
VNCview GS should be able to connect with any VNC server that fully implements the RFB protocol as defined in RFC 6143 or earlier compatible specifications. Here is a list of some VNC servers; many others are also available.
* Microsoft Windows, *nix (X11), and OS X: __RealVNC__, http://www.realvnc.com/
* OS X: __Vine Server (OSXvnc)__, http://www.testplant.com/dlds/vine/
* *nix (X11) and OS X: __x11vnc__, http://www.karlrunge.com/x11vnc/
* Microsoft Windows, *nix (X11), and macOS: __RealVNC__, http://www.realvnc.com/
* macOS: __Vine Server (OSXvnc)__, http://www.testplant.com/dlds/vine/
* *nix (X11) and macOS: __x11vnc__, http://www.karlrunge.com/x11vnc/
x11vnc is a good option, because it supports server-side display scaling, which is useful to fit more information on the IIgs screen.
VNCview GS does not work with the Screen Sharing functionality in OS X, because the Screen Sharing server does not support the pixel format that VNCview GS requires. The above servers can be used instead.
VNCview GS does not work with the Screen Sharing functionality in macOS, because the Screen Sharing server does not support the pixel format that VNCview GS requires. The above servers can be used instead.
Version History
---------------
##### 1.0.2
* Support for typing non-ASCII characters
* Smoother transitions between 640 mode and 320 mode
* Improved UI responsiveness during raw pixel decoding
##### 1.0.1
* Improved clipboard transfer routines, with support for non-ASCII characters
* Improvements to help the display "catch up" when content is changing rapidly