Re: RE:RE: [Openvrml-develop] Doxygen documentation

[Braden M. <br...@en...>]

On 12 Aug 2001 14:53:36 +0200, luc...@li... wrote:
> >What level of success are you looking for? It is quite true that many
> >classes remain undocumented, and doxygen will spew lots of warning
> >messages to that effect. But it should output docs for the classes that
> >*are* documented.
> 
> Actually i would like to get the complete hierarchy: even if many 
> classes are undocumented it is still very useful to have a complete 
> reference about the class hierarchy toghether with a list of all  
> members in each class. This would help a lot to dig in the internals of 
> the library.

As Nigel mentioned, look at the docs for Doxygen and play around with
the config file.

> >So, I'm curious how you're using these classes. If there is a good
> >reason to make them part of the public API, we can do that.
> 
> I am trying to collect the geometry information stored in a vrml file.
> 
> In fact i am trying to port to OPENVRML a robotic simulation enviroment 
> that i coded during my phd course. 
> Now i am using Cosmo Broswer and the COM EAI interface it provides to 
> handle all the VRML visualization, but this is crap because
> it's extremely slow and i dont get any control on the rendering process 
> and most of all since Cosmo is not opensource i cant put this in the 
> open source domanin. I think that Openvrml is the tool that best suits 
> my needs. Also i excuse myself for my insisting questions but i am 
> trying to dig into the library code...

VrmlScene::readWrl() will run the parser and give you the resulting
world as a VrmlMFNode. Are you looking for some other information from
the parser?

-- 
Braden McDaniel                           e-mail: <br...@en...>
<http://endoframe.com>                    Jabber: <br...@ja...>