Re: X for s48

you really want a native interface so you can write a pure-scheme UI
toolkit.  unfortunately, the size of the protocol makes one shrink
from the very thought.  this is the legacy of X.  but the fact is, you
only need a few dozen calls in the heart of the toolkit.  99.7% of the
protocol is almost never used.  so, i would use the automatic C glue
system to attach Xlib, but not to use it in the main path of the
toolkit, only during initialization and exceptional conditions etc.
you probably have to put Xlib in synchronous mode to avoid its
buffering, but in general, i think this is a good way to bootstrap a
native X interface.

rant: get rid of stdio!

opinion: if i wrote such a toolkit, i would not mirror my widget
structures with server structures. (X window per widget, as all
current toolkits do.) minimize the infection of server brain-damage!
tabula rasa!  this also makes the toolkit more portable to other
graphics hardware (other than X, eg svgalib).