Jonathan,
Adrian,
I am doing a little talking while my brain is driveling through different
ideas here...
but try this on for size....
the current generation of vnc servers all use a gestalt type mechanism to
pass global data back and forth amongst the extension which patches low
level global routines and the server which basically incorporates mouse and
keyboard events and screen updates. am i right in this assumption?
if so, why can't one version of the server be written (a FAT Carbon app)
that has a single switch that "knows" that under os X it uses the
"CGRemoteOperation.h" routines for events, and the tradtitional method for
previous "classic" revs of the OS.
In addition, under "classic" os, the vncPatches extension still does what
it does now, but under OS X, a new carbonised background application (which
is launched at boot time) does the same gestalt thing on the front side,
but on the back side uses the same "CGRemoteOperation.h" for its method of
trapping screen updates.
my thinking is that this would allow the VNC server to incorporate fewer
changes to make it work under OSX... and allow the faceless helper app to
be written in whatever method works best for it (cocoa, carbonPEF, or
carbonMACH)
let me know if this makes any sense. if it does, I can start the
carbonisation process of the server relatively soon (yes i have OSX and CWP6).
Tim
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
