Re: Performer reads iv. Maybe!

New Message	Reply	Date view	Thread view	Subject view	Author view

Jim Helman (jimh++at++surreal)
Mon, 12 Dec 94 19:25:52 -0800

Next message: Jim Helman: "Re: Accessing Frame Buffer"
Previous message: Desmond Hii Toh Onn: "performer and FORMS library"
Next in thread: michael++at++ifr.luftfahrt.uni-stuttgart.de: "Re: Performer reads iv. Maybe!"

> I've been reading Gavin Bell's postings in comp.sys.sgi.graphics.
> He is asking if any Inventor users would be upset if Inventor's C
> API were to disappear in a future (the next?) release. I guess we'd
> better hope the Performer team is moving to C++ or we are really
> going to be left out in the cold.

"Moving"? Just to allay fears, we are *adding* a C++ API
(which is our underlying language) in Performer 2.0. We
have no plans to abandon our C API or leave it less
functional than our C++ API.

I apologize to everyone for the delay in getting the
completed Inventor loader out door. There are still some
optimzations to be done to it. Sometimes we may be too
picky about performance, but it is our obsession.

rgds,

-jim helman

jimh++at++surreal.asd.sgi.com
415/390-1151

Next message: Jim Helman: "Re: Accessing Frame Buffer"
Previous message: Desmond Hii Toh Onn: "performer and FORMS library"
Next in thread: michael++at++ifr.luftfahrt.uni-stuttgart.de: "Re: Performer reads iv. Maybe!"

New Message	Reply	Date view	Thread view	Subject view	Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:50:44 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.