You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
libtdevnc/vncterm
dscho a84b3d072a pointerClient was still static.
do not make requestedRegion empty without reason.

the cursor handling for clients which don't handle CursorShape updates was
completely broken. It originally was very complicated for performance
reasons, however, in most cases it made performance even worse, because at
idle times there was way too much checking going on, and furthermore,
sometimes unnecessary updates were inevitable.

The code now is much more elegant: the ClientRec structure knows exactly
where it last painted the cursor, and the ScreenInfo structure knows where
the cursor shall be.

As a consequence there is no more rfbDrawCursor()/rfbUndrawCursor(), no more
dontSendFramebufferUpdate, and no more isCursorDrawn.  It is now possible to
have clients which understand CursorShape updates and clients which don't at
the same time.

rfbSetCursor no longer has the option freeOld; this is obsolete, as the cursor
structure knows what to free and what not.
20 years ago
..
.cvsignore included vncterm 22 years ago
ChangeLog included vncterm 22 years ago
LinuxVNC.c global structures/functions should have "rfb", "sra" or "zrle" as prefix, 21 years ago
Makefile.am support MinGW32! 21 years ago
README included vncterm 22 years ago
TODO included vncterm 22 years ago
VNCommand.c convert c++ comments to c comments 21 years ago
VNConsole.c pointerClient was still static. 20 years ago
VNConsole.h global structures/functions should have "rfb", "sra" or "zrle" as prefix, 21 years ago
example.c convert c++ comments to c comments 21 years ago
vga.h included vncterm 22 years ago

README

In this stage (beta), there are two programs functional:

LinuxVNC <tty number>
	monitor a virtual console (text mode) of Linux. You need
	root privileges, or at least be in the "tty" group, because
	it reads /dev/vcsN and writes /dev/ttyN.
	It follows the same idea as WinVNC, x11vnc or OSXvnc, i.e. it
	takes an existing desktop and exports it via RFB (VNC), just that
	LinuxVNC exports text.

VNCommand <command> <args>
	executes <command> redirecting stdin from a vncviewer and stdout &
	stderr to the vnc clients. This might be renamed to vncTerm if
	there are some term capabilities added (up to now, bash doesn't look
	nice). Colours and other ANSI sequences need to be added.

My original plan was to create a program named vncTerm. It was meant to
overcome incompatibilities between different TERMs, but I found "screen" to
be just such a program. Maybe once some time in the future I'll make a
patch for screen to use VNConsole to export it's contents via RFB...

These two programs are a simple application of LibVNCServer with a small
console layer in between (VNConsole). You can use them under the terms
(not vncTerms ;-) of the GPL. They where written by Johannes E. Schindelin.