home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #26 / NN_1992_26.iso / spool / comp / windows / x / 18798 < prev    next >
Encoding:
Text File  |  1992-11-07  |  1.1 KB  |  30 lines
  1. Newsgroups: comp.windows.x
  2. Path: sparky!uunet!utcsri!newsflash.concordia.ca!sifon!thunder.mcrcim.mcgill.edu!mouse
  3. From: mouse@thunder.mcrcim.mcgill.edu (der Mouse)
  4. Subject: Re: X to PS
  5. Message-ID: <1992Nov6.112819.22305@thunder.mcrcim.mcgill.edu>
  6. Keywords: PostScript
  7. Organization: McGill Research Centre for Intelligent Machines
  8. References: <1992Nov2.164444.5734@murdoch.acc.Virginia.EDU>
  9. Date: Fri, 6 Nov 92 11:28:19 GMT
  10. Lines: 19
  11.  
  12. In article <1992Nov2.164444.5734@murdoch.acc.Virginia.EDU>, heddle@clas01.cebaf.gov (David Heddle) writes:
  13.  
  14. > We are writing a postscript driver for a graphics intensive in-house
  15. > X/Motif application.  Our approach is to open the file, write the
  16. > appropriate header, and to create a postscript analog to every
  17. > low-level X routine.
  18.  
  19. This really isn't possible, unless you are willing to, effectively,
  20. print screendumps of a (possibly relatively-high-resolution) screen.
  21. Think about simulating XCopyArea or drawing with a function of GXxor,
  22. to name just two that come to mind right off.
  23.  
  24. Or, of course, you're willing to (rather severely, IMO) restrict the X
  25. operations you can perform.
  26.  
  27.                     der Mouse
  28.  
  29.                 mouse@larry.mcrcim.mcgill.edu
  30.