Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!maverick.ksu.ksu.edu!ux1.cso.uiuc.edu!milo.mcs.anl.gov!atlantis.ees.anl.gov!korp
From: korp@atlantis.ees.anl.gov (Peter Korp)
Newsgroups: comp.windows.x
Subject: Re: OW as a PostScript X server...
Message-ID: <1990Nov14.060313.2434@mcs.anl.gov>
Date: 14 Nov 90 06:03:13 GMT
References: <9011131842.AA08663@islanders.> <1990Nov13.231333.23226@crl.dec.com>
Sender: news@mcs.anl.gov
Followup-To: korp@athens.ees.anl.gov
Organization: Advanced Computer Application Center, Argonne National Laboratory
Lines: 18
Nntp-Posting-Host: atlantis.ees.anl.gov

Well this topic is getting kind of old, but....

I know that having two sockets to communicate through is kinda gross but then
how often do you really want to do X imaging in the same area as PostScript?
It seems that proper use of clippaths/GC would eliminate most of the problems
jim refers to.

I guess i'm just saying it is not a problem using two imaging models in
OpenWindows. Draw X stuff stuff around PS stuff and vice-versa but why mix
them?

Peter

-------------------------------------------------------------------------------

PostScript Raster imaging in OpenWindows in a 500x500 window?
Can you say 60 frames per second?
I knew you could!