🚀 go-pugleaf

In article <468@imp.diablery.10A.com>
	devil@diablery.10A.com (Gil Tene) writes:
>- Is there a PHIGS/PHIGS+ compatible library that interfaces to PEX 
>  (One that lets you simply link with working PHIGS code).

The PEX-SI includes a PHIGS/PHIGS-PLUS API.

>- Any other toolkits?

"Toolkits" is an over(ab)used term.  What kind of "toolkit" are you
looking for?

>- Are there any standards trends out there?

Again, this question is so vague that I don't know how to answer it.
Are you talking abotut X Consortium Standards, OSI/ANSI standards, or
"defacto" standards?

>- What is the "safest, most standard" toolkit to use on a long-lasting
>  project? 

I would guess that the "safest" toolkit to use would be one where you
have all the source code, since you are guaranteed access to the code.
Thus if you want to switch to a new platform, you can port the toolkit
if it isn't provided by the vendor of that platform.

>- What is the difference between a PEX library and a PEX toolkit?
>  (e.g. PEXlib vs. PEXtk)

PEXlib and PEXtk are both interfaces to the protocol, although PEXlib
is intentionally more protocol-specific than PEXtk.  PEXtk is another
API that generates the protocol.

>- Where is the best place to get up-to-date informations and
>  documentation on PEX related subjects?

This newsgroup is probably the best place; I'm pretty sure all the PEX
vendors read this newsgroup (and lots of others too).

						-- Rich
-- 
	Repeal the personal income tax; vote Libertarian in 1992.
Disclaimer: I speak for myself, except as noted; Copyright 1992 Rich Thomson
UUCP: ...!uunet!dsd.es.com!rthomson			Rich Thomson
Internet: rthomson@dsd.es.com	IRC: _Rich_		PEXt Programmer