> > dviv program uses simply put pixel routines to write into framebuffer
> If you use the X-target then everything is unaccelerated, because the
> X-target emulates a framebuffer.
> Try the Xlib-target. You can force each ggi program to use a certain
> target by setting the environment variable GGI_DISPLAY="<target>"
> All operations are accelerated Xlib, only blitting is slower than X.
Please note, that stuff like Putpixel is probably slower with xlib calls.
This is due to call overhead in the X protocol which is even worse than
the call overhead in LibGGI itself.
For applications that effectively do lots of Putpixel type operations to
form a whole screen, the "right thing to do" would be to use higher
primitives like PutBox, HLine and similar whereever possible to minimize
call overhead.
If there is no such possibility, it would be reasonable to render into an
application internal buffer with Macros (!) and Pointers to avoid the
call overhead and then blit to screen or to use the LibGGI DirectBuffers.
CU, Andy
--
= Andreas Beck | Email : <[EMAIL PROTECTED]> =
