[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnu3dkit-dev] Strings and parameter lists
From: |
Philippe C . D . Robert |
Subject: |
Re: [Gnu3dkit-dev] Strings and parameter lists |
Date: |
Sat, 15 Feb 2003 17:29:57 +0100 |
Hi,
I have now checked in an *initial* version of the rendering API into
the CVS (see G3DRenderer.h). Note that the naming is not final and I am
not even sure if all (needed) Ri* functions are covered, but you get
the idea...:-)
On Friday, February 14, 2003, at 10:13 Uhr, Gerard Iglesias wrote:
Philippe C.D. Robert wrote:
Well, you could do that, but the beauty IMHO would be to have an API
which permits you to render a RIB directly. But I am not sure we want
this at all because first, the 3DKit is a scene graph and should thus
work this way and not directly via renderer bypassing the scene graph
and second, we would then have to make sure to at least understand
everything which is in a RIB.
Sure that it would not be a simple task, RIB file can contains very
rich things, like animation, and I am not sure that 3DKit would
manipulate animation natively for example.
I don't think so. Currently I do not even support it in the interface.
But if we can parse rib file to get tree of geometry node il will be a
good start :)
:-)
But having a render action which does produce a RIB would be cool as
you could then process this further using other, already existing
tools. As an example you could simply pipe the 3DKit's output into
other CLI renderers' input.
Sure, and I think that it would be not so difficult to do so, a lot
simpler than parsing a rib file.
Yup, and it would be a start!
I am exploring PCCTS/ANTLR to parse the rib file format, seems to be
very interesting to use it, any experience ?
I am more in favour of lex/yacc, but from what I have heard ANTLR is a
good product as well.
-Phil
--
Philippe C.D. Robert
http://www.nice.ch/~phip