XExt questions - XShm, Render
Sean Champ <[email protected]> Mon, 13 Dec 2004 06:49:42 -0800
| Newsgroups | gmane.lisp.clx.devel |
|---|---|
| Message-ID | <[email protected]> |
Hello,
I'm utterly new to CLX, but trying to get a handle on it, without any
fuss, etc.
I'm wondering, specifically, about: What the heck to do, regarding a
couple of X extensions, namely: X Shared Memory, X Render; I thought
that I'd just put 'em both, together, in this one message, and be on
with it.
Regarding XShm :
I've started reading the mit-shm.pdf under
http://www.x.org/X11R6.8.1/doc/Xext/
("Yes, just started")
I noticed:
- the mit-shm.pdf document says that the C header files sys/shm.h and
X11/extensions/XShm.h should be included in the C file that would
include some code supposed to use XShm
- This, on page 3 of the mid-shm.pdf document:
The basic capability provided is that of shared memory
XImages. This is essentially a version of the ximage interface
where the actual image data is stored in a shared memory
segment, and thus need not be moved through the Xlib
interprocess communication channel. For large images, use of
this facility can result in some real performance increases.
and that sounds, frankly, great. Of course, I've already mentioned
that I have no idea of what to do, to use XShm from CLX
- some "hits", in a c.l.l search at google, seeming to indicate that:
To get into the {fun} of CLX and XShm, I'm to be up for some working
with some rather-new, but honestly rather-fun-sounding "stuff", in
regards to ... the "low-level" .. er .. "stuff" that the CL
implementation usually gets to hide from me; (I don't know the terms
to communicate anything about such "low-level fun", but, well, if
it's as readable as the ASM book of {someone}, then it should be
understandable to me, too - incidentally, and/or not incidentally,
but plainly so, in any regard)
Also, I'm wondering aftr something I'd read, which seemed to equate
shared-memory "stuff" to IPC -- and wow, I do not know what I will be
dealing with, but that sure sounds fun ("just store it in memory and
let the other app. get to it", instead of "send it over a socket"),
for lisp-to-lisp style IPC
and that's all that I can think to say of what I can think to say of that.
Regarding XRender :
On the CLiki CLX page, I'd read that Gilbert Baumann had been working
on supporting the X Rendering extension, in CLX, and that it was
"almost done". I'm wondering, then, what I could do -- whether to
wait for it, and/or to help, myself, to get that "almost" trimmed of
it, and then it be "yay, done" or just "done" so then we can have some
get-down fun with it.
Incidentally, I'd made some bookmarks, regarding X Render, before I'd
checked the CLiki page about it. They might be of interest, I'd hope:
1) A New Rendering Model for X
Keith Packard; Usenix 2000
http://keithp.com/~keithp/talks/usenix2000/render.html
2) Design and Implementation of the X Rendering Extension
Keith Packard; Usenix 2001
http://keithp.com/~keithp/talks/usenix2001/xrender/
3) The X Rendering Extension, Version 0.0.15, 2000-11-19
Keith Packard; (reported as it being "the current rendering protocol spec")
http://keithp.com/~keithp/render/protocol.html
and so, there's some reading about it, to get a handle on it, and I'll
be glad to direct my attention to it, though I'd also be glad to not
duplicate efforts - absolutely.
Now, I guess I can mention, also, that I'll be plenty-glad to write
some documentation for CLX.
Now, I know there are arguments that might be made, about what would
be "the best approach" for documenting Common LISP code; I just use
DocBook SGML, DocBook DSSSL, and be done with it, generally. (and
DocBook XML is just as doable, though it doesn't support the nice
"internal DTD subset" of SGML, where parameter (%) entities would be
defined, directly within the document - and that limitation of XML
makes it harder to extend the DocBook DTD, but, I digress)
As for one suggestion that I'd like to try the audience on, regarding
Documentation for CLX : I'd not yet "got around to it", but I'd
through of working-up some DSSSL, for reformatting the SGML sources of
the CLX Manual being kept by Gilbert Baumann -- reformatting, to make
some DocBook SGML out of it, so that I and others might edit it,
carefully and such, and extend the documentation for the current
version of CLX
If it sounds like that would be potentially good for anything, I can
contact Gilbert Baumann directly (and keep it off-the-list then,
if it would be preferred) so that I might make sure he's cool with it,
and then get on with it (with all the fun of Scheme-in-SGML DSSSL,
but still, it's a LISP-like thing, I figure - and no, I do not mean to
get off topic or to be swiped-at, by anyone, about it.)
So, thank you.
I look forward to getting into the stuff of XShm and X Render, in CLX,
and to making some XFree86-area fun with it
Will wait on it, to see what can be done of such-and-such with CLX and
XFree86, all "best practice" like.
--
Sean Champ
[email protected]
_______________________________________________
Portable-clx mailing list
[email protected]
http://lists.metacircles.com/cgi-bin/mailman/listinfo/portable-clx
cvs -d :ext:cvs.telent.net:/usr/local/src/cvs co clx # over ssh
cvs -d :pserver:[email protected]:/cvs co clx # anonymous