[482] in Zephyr_Bugs
Re: zbrowser
daemon@ATHENA.MIT.EDU ("Mark W. Eichin")
Fri May 28 13:24:30 1993
Date: Fri, 28 May 93 13:24:22 EDT
From: eichin@Athena.MIT.EDU ("Mark W. Eichin")
To: Stephen Gildea <gildea@expo.lcs.mit.edu>
Cc: zephyr-bugs@Athena.MIT.EDU
In-Reply-To: "[481] in Zephyr_Bugs"
[0481] daemon@ATHENA.MIT.EDU (Stephen Gildea) Zephyr_Bugs 05/28/93 08:21 (15 lines)
Date: Fri, 28 May 1993 08:21:23 EDT
From: Stephen Gildea <gildea@expo.lcs.mit.edu>
I'd like to get the functionality of zbrowser.
Then you'll need to redesign it from scratch.
I tried to build it from the sources in ozwgc/ in the 8/31/92 snapshot,
but had problems. And when I got it built it didn't work very well.
I'm a bit suspicious anyway, because I found the sources in an "old"
directory.
Am I starting from the right place? Will this code work with the new zwgc?
They will not work (1) with the new zwgc (2) with the ICCCM (3) with
any release of Xt after X11R2. Maybe I should raid all of the
directories that have the source and delete it :-)
The zwgc issue: ozwgc marked zephyr windows with properties
that were used as the zbrowser labels. The new zwgc doesn't do that.
The ICCCM issue: zbrowser listened for substructure notify
events off of the root, then examined each newly created window for
one of those properties. This is apparently evil, w.r.t. ICCCM
compliance. I'm told there is a hairy way of doing it which has zwgc
set properties in another (hidden) window owned by zbrowser to inform
it of new messages, but I've never looked into it.
The Xt issue: the sources include hooks into one of the Xt
widgets so that you could dynamically set its size without it dumping
core :-) This predates the Xt/Xaw split.
The code may be interesting as a concept example, but xzwrite
or something like it is probably a better starting place.
_Mark_ <eichin@athena.mit.edu>
MIT Student Information Processing Board
Cygnus Support <eichin@cygnus.com>
(Author of ozwgc + zbrowser)
