Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!uwvax!uwmacc!jwp
From: jwp@uwmacc.UUCP
Newsgroups: comp.graphics
Subject: GKS, Postscript questions (summary needed)
Message-ID: <1049@uwmacc.UUCP>
Date: Wed, 11-Feb-87 14:15:45 EST
Article-I.D.: uwmacc.1049
Posted: Wed Feb 11 14:15:45 1987
Date-Received: Thu, 12-Feb-87 18:40:34 EST
Organization: UWisconsin-Madison Academic Comp Center
Lines: 21
Keywords: GKS postscript

I have asked questions about these things in the past,
but I am still a little confused, so I thought I'd try again.
I have a fair idea of what GKS is (standardized functionality)
and what the binding is (standardized routine names and argument
lists).  Now, the GKS calls produce some generic information
(is this the VDI?) that is interpreted by "drivers", right?
A driver can go from VDI to, say, a TEK4014 or a Versatec.
It could also go from VDI to a metafile.  Is this metacode
part of the standard?  Can I produce a metacode file using
vendor A's software, and plot it on a versatec using vendor
B's metacode-to-versatec interpreter software?  Is this picture
flawed in any big way?

See, we have a GKS package from a vendor, without a postscript driver.
We also have a postscript printer.  Do we need a whole new GKS
package with a postscript driver included, or is it sufficient
to advertise for a "metacode-to-postscript" driver?

Any GKS packages out there with postscript support?
-- 
	Jeff Percival ...!uwvax!uwmacc!sal70!jwp or ...!uwmacc!jwp