🚀 go-pugleaf

In article <Bxv0KL.F6H@dei.unipd.it>, moka@esse3.dei.unipd.it (Enrico Minelle) writes:
|> 	I need to know something about PHIGS systems and PEX.
|> 
|> 	I work with an hp700 hewlett packard machine with HP-PHIGS
|> 	and i have read about PEX but i don't know anything about
|> 	it.
|> 
|> 	Which are the differences between HP-PHIGS and SunPHIGS ?
|> 	What is PEX and can i use pex libraries with my hp-phigs?
|> 
|> 	I will be very happy if someone can post a FAQ or answer me.
|> 	
I think that Rich Thompson has been doing a good job with the FAQ.
Hopefully he can send it to you or will repost it soon.  I don't have a
copy at the monment.

I don't want to get into specifics on HP-PHIGS or SunPHIGS because I may
not have the latest information.  But in general, a vendor can create
their own "vendorPHIGS" implementation that generates PEX.   (PEX is
a protocol - PHIGS is an API that may generate PEX) These particular
implementations require that a X/PEX server be used to display the graphics.
The application can be on the same machine or on two different machines in
a network.  In fact, the machines can be from different vendors, which is the
whole point behind PEX.

As a vendorPHIGS programmer/user, you may not be aware that vendorPHIGS
generates PEX, beyond the requirement that you'll need a PEX server to
see the results.  You would not NEED to use 'pex libraries' if you are
coding in vendorPHIGS.  However, it MAY be possible to use something
like PEXlib inside a PHIGS program to do things that you can't do with
vendorPHIGS.

-- 
Karl Schultz                             schultz@vnet.ibm.com
These statements or opinions are not necessarily those of IBM