Re: [Gnu3dkit-dev] G3DRenderer.h

[Brent Gulanowski]

On Sunday, March 16, 2003, at 05:19  PM, Philippe C.D. Robert wrote:

> > > Yes, there will be such classes. BTW it is the renderer action which 
> > > accesses the data (geometry, shaders, ... ), not the other way 
> > > around!
> >
> > Erm, all I want to know is, who sends the messages to the renderer? 
> > Who calls the methods in the renderer API? The "action"? What class 
> > exists which represents an action? Does this class act as the brains, 
> > first asking the scene for its data, then passing it to the renderer 
> > via the RenderMan-style interface which you have produced?
>
> An instance of G3DRenderAction is used for this purpose. It traverses 
> the graph and renders the scene by first calling the appropriate 
> methods on its renderer (context management, optimised state handling, 
> shader setup and so on) and then requesting the geometry to draw 
> itself.
>
> So you can use n render actions using m different renderer backends 
> concurrently on the same scene. This also makes life in a 
> multithreaded environment much easier as this is non intrusive.

You can solve this all for me with one question: who calls 
[someGeometry drawGeometry]? Does the Render action call it or does the 
shape call it? I can honestly see it in both ways, and neither looks 
any different from where I'm standing. When a geometry instance 
receives the drawGeometry message (from whomeve), does IT then call 
[someRenderer objectInstance:objHandle] or [someRenderer 
drawPolygons:myPolys params:myParams]?

Sidebar: why isn't -objectInstance: call -drawObject: ?

>
Brent Gulanowski                        address@hidden
--
keyboard not found, press F1 to continue