ali@polya.Stanford.EDU (Ali T. Ozer) (11/09/89)
In article <7596@zygot.ati.com> bruceh@zygot.ati.com (Bruce Henderson) writes: >What happens is that when you say print in an application, the Display >Postscript window server changes from sending postscript code to the >screen, to sending it to a spool file that it then images on the local >printer or passes over the network to a machine attached to a remote >printer. When you use save, the file name you enter is where all of >this postscript ASCII stuff goes. It is a neat way to look at the way >that various apps print, including all of thier custom postscript >definitions, because they must be downloaded in the text of the >documnet as well!! [NeXT PS Hacker secret..] To make life easier for looking at such PS files, you can make a symbolic link to Yap from your own ~/Apps directory. Then, after doing "Find Applications" or logging out and back in, Yap will become your default PS previewer --- thus, when you hit "Preview" in the Print Panel Yap will be launched in place of Preview, and the PS code will be displayed in a Yap window. Ali
jacob@gore.com (Jacob Gore) (11/09/89)
Sigh. I get the feeling that I'm using the wrong tool for the job. Namely, the interface provided by the AppKit, one that every user of a NeXT expects, to print -- of all strange and weird things -- TEXT! From a file!! Already in conforming PostScript!!! On a system designed around a postscript server!!!! Unthinkable!!!!! I can just hear those electrons screaming now, as they hit the cathode: "How DARE he print something that is not in a Window!" All the documentation I've seen either tells me how to print a picture of a window, or it lists a bunch of methods that a WYSIWIG word processing application, if it somehow overrides them to do the right thing, is supposed to use to "produce" conforming PostScript document. It will go into a spool file. The PrintPanel knows where it is. The programmer needs not know how to just give the PrintPanel a file of PostScript. After all, the PostScript will always come from a Window, and all these nice methods are the ones that generate the PostScript. We mustn't bother the programmer with irrelevant details. He can just printPSCode the Window. Or use WriteNow. Or write something as complicated as WriteNow... so what if it's just to print one silly file, already in PostScript. I am not a WYSIWYG-hater, really, I'm not. But this is one case where I dont't want to See what I need to Get! It may be hard to tell (:-), but I'm quite frustrated. If I'm missing something that's supposed to be obvious, PLEASE let me know. I don't care if it's a very stupid omission on my part -- I'll be most happy to have my nose rubbed in it, by anybody, as long as it results in me knowing what to do here! All I'm trying to do is print a PostScript file, which happens to be WriteNow output (saved through its PrintPanel), and do it using a PrintPanel, so that the user can select the printer, the page range, preview it, etc. How? Jacob -- Jacob Gore Jacob@Gore.Com boulder!gore!jacob