gulik@motcid.UUCP (Gregory Gulik) (02/01/91)
I've been using Openwindows 2.0 on my Sun 3/60 for several weeks now,
and I'm still amazed.
Does anyone know how it performs the magic to get X and Sunview
applications to run on the same screen?
While we're at it, why do Sunview applications always have that annoying
white border around them? Is there any way to get rid of it?
Thanks.
-greg
--
--
Gregory A. Gulik
mcdchg!motcid!gulik || greg@gagme.chi.il.us
|| gulik@depaul.edufischer@iesd.auc.dk (Lars P. Fischer) (02/08/91)
>>>>> On 31 Jan 91 20:33:36 GMT, gulik@motcid.UUCP (Gregory Gulik) said: In article <4619@melon11.UUCP> gulik@motcid.UUCP (Gregory Gulik) writes: Gregory> I've been using Openwindows 2.0 on my Sun 3/60 for several weeks now, Gregory> and I'm still amazed. Gregory> Does anyone know how it performs the magic to get X and Sunview Gregory> applications to run on the same screen? X and NeWS are both really network protocols. Each protocol has messages that allows for the creation of windows, etc. Running X and NeWS applications together is a matter of being able to handle both protocols. No big deal - in theory. Gregory> While we're at it, why do Sunview applications always have Gregory> that annoying white border around them? SunView is a kernel-based window system, i.e. all the primitives are built directly into the kernel and everything works by writing directly to video memory. All OpenWindows does is fool the kernel into believing that SunView is running. That's why SunView windows always stay on top of everything else -- they are written directly to video memory, behind the back of the window server. The white border is added to mark these windows as "special", and because strange things most be done when the cursor moves from one type of window to the other. It's a nice feature, but it is really only a stopgap. /Lars -- Lars Fischer, fischer@iesd.auc.dk | Beauty is a French phonetic corruption CS Dept., Univ. of Aalborg, DENMARK. | - FZ