[4146] in SIPB bug reports
Re: vax 7.6E: xmosaic
daemon@ATHENA.MIT.EDU (Calvin Clark)
Fri Oct 8 20:19:57 1993
Date: Fri, 8 Oct 93 20:19:09 EDT
From: Calvin Clark <ckclark@mit.edu>
To: John T Kohl <jtkohl@mit.edu>
Cc: bug-sipb@mit.edu
In-Reply-To: Your message of Fri, 08 Oct 93 19:47:23 -0400.
<9310082347.AA03494@milquetoast.MIT.EDU>
I agree that merging the resources is bad.
When I wrote the script, I considered making it set XFILESEARCHPATH
instead of actually running xrdb -merge, but the problem is that the
resources are different for color and monochrome displays; i.e., the
app-defaults file contains #ifdef COLOR conditionals. I don't know
whether it is necessary for xmosaic to have separate resources for
different types of display, but if it is, X doesn't provide a good way
of handling the situation.
I suppose the C source could be modified to query the type of display and
load a special external resource file for color, greyscale,
etc. displays. That's not to hard, and I'd be willing to do it as long
is there isn't a better way.
-Calvin
P.S. This is one advantage the "Jets" toolkit used by Dash and the
Console application has over the X toolkit. The non-standard color
converter allows one to set resources for color, greyscale, and
monochrome monitors in a single X resource line. Of course, if you
could weave m4 into Xlib, then you don't have any of these problems.
Don't laugh; just imagine what would have happened if Wcl preceded Xt.
