From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <1766e9b4ce8a1a43a6748a2049e2c87d@acl.lanl.gov>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] vnc[vs] implementation question
From: andrey mirtchovski <andrey@lanl.gov>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Tue, 18 Jun 2002 11:03:56 -0600
Topicbox-Message-UUID: b31d65ce-eaca-11e9-9e20-41e7f4b1d025

> it's worth noting that vncs is what uses
> the stand-ins for devdraw etc.
>
> vncv doesn't.  vncv probably has good performance
> just because all it does is write blocks to the
> screen.  memmove to the screen is fast.

got it...  the trick (or rather, the problem with xaos) is that it
does
	loadimage(someimage, buffer, ...);
	draw(screen, someimage,...);

in vncv you (I assume) just do a
	loadimage(screen, buffer, ...);

in XaoS' case, unfortunately, one can't use this approach, because the
pixels are written by the program in CMAP8 format (and the image used
in loadimage(); is alloc-ed in CMAP8 too) and if the screen is
anything else loadimage(screen, ...); fails...

it'd be great to have routines that convert between format en masse
(similar to the ones in color(2)), but that's just as expensive as
doing a loadimage();draw() combination.

or maybe there's a trick to it?