Informal announcement of Intention for supporting ICCCM in CLX

Hello folks,

I just wanted to mention that I intend to start working with support for ICCCM 
in CLX.

Granted, I'm not sure what's already in CLX, for ICCCM  -- if there's 
anything, for it, there.  (A quick grep of the CLX sources turns-up one 
incidiental hit, in manager.lisp - line 314)  I'm not immediately familiar 
with the XFree86 "core protocol" either -- not sure which xspec it would be  
documented in, either. So, I've some run-up to take care of, simply.

* Commentary

I'll check the list archives, for anything that would've been done/said, about 
ICCCM in CLX. 

If there would be any thoughts, for/about ICCCM in CLX, presently, then I 
would be glad to be any party to such -- whether such would be as commentary, 
suggestions, general discussion, suggestion of pseudocode, "else, or other."


* Roadmaps

I cannot presently offer a roadmap, about any code, from myself, for ICCCM 
support in CLX. (This will be a pretty informal effort, here. )

I guess that ICCCM support will be required, before anything wold be done -- 
simple though it should be --  regarding NET_WM properties. So, anyho, I 
guess one could say that NET_WM support would be an upcoming feature, to be 
available sometime after ICCM support would be available.


* Motivation

As for what was the intial part of my own motivion, for this: There is an 
XEmacs "external editing widget" (documented in the info node, 
'external-widget', in the  xemacs Info documentation). I intend to make such 
to work with an LGTK-based GTK interface. 

After a quick perusal of the XEmacs external-widget documentation, it does 
appear that some ICCCM support  will be required, in order for the means to 
be defined, for the XEmacs external widget to work with the XFree86 window 
that would contain it

It may seem as if this was a "long way around", for text editing in a Lisp 
graphical-UI application. I'm not concerned about that. I'll be glad for 
there to be some ICCCM support in CLX, beside any of this.

As for "why not e.g. Hemlock",  I'd rather not start any discussion about 
that. To explan it, though: XEmacs works, quite broadly, already, for text 
editing.


I'll try to document what I will have done, about this. The documentation will 
probably be written as DocBook SGML or XML, and made available as HTML -- 
PostScript also and possibly PDF, if anyone would prefer such. (I won't start 
a thread, here, about the formatting of the CLX manual, either. I've no 
qualms about TeX, incidentally, it's just that I'm not anyhow familiar with 
it, as a means of reprsenting the text and images, of a document.)

I can't think of how else to conclude this email, but to conclude it shortly.

So, there it is.

---
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