Re: QT/OpenGL (Re: was Potential O'Reilly Cocoa books (was Docs))
Re: QT/OpenGL (Re: was Potential O'Reilly Cocoa books (was Docs))
- Subject: Re: QT/OpenGL (Re: was Potential O'Reilly Cocoa books (was Docs))
- From: Georg Tuparev <email@hidden>
- Date: Mon, 27 Aug 2001 01:16:01 +0200
Brent,
You are right in a way. But I do not agree with your reasoning. It is a
procedural layer because it is an extremely difficult task (probably
even not really achievable) to implement an object model that is general
and flexible enough of solving problem classes as different as games and
scientific visualization. But I am sure that with the time domain
specific object layers will start popping up.
Oh, and I will love to see what Michael (Wave) Johnson from Pixar has to
say about this...
On Sunday, August 26, 2001, at 07:25 AM, Brent Gulanowski wrote:
My feeling after looking into the OpenGL part of this is that these
media
interfaces will always be a layer which operate procedurally, since the
only
way they can offer performance is to be essentially one-way data pipes:
you
provide a stream of data and they process it into images/sounds as
quickly
and/or as smoothly/efficiently as possible. Messaging and 2-way
communication only slow down the media presentation. So I figure that
you
can model your data any way you want, but for presentation, convert it
to
the array or struct preferred by the API, fire off your pointer, and
then go
back to managing the model. OpenGL seems to me like a monolithic object
which is best thought of as a bottomless well. You can only judge if
it's
working right by actually seeing what's on screen. Heck, just dropping
OpenGL from fullscreen to windowed mode apparently kills performance,
and is
a prime example of the one-way street of OpenGL dataflow.
[...]
Georg Tuparev
Tuparev Technologies
Klipper 13
1186 VR Amstelveen
The Netherlands
Mobile: +31-6-55798196