Hi,
Trying to get an understanding for the object model,
are there any uml style object diagrams or similar available over
the engine. Perhaps by part / subsystem or similar?
/Andreas
irrlicht object diagram
-
randomMesh
- Posts: 1186
- Joined: Fri Dec 29, 2006 12:04 am
Re: irrlicht object diagram
Irrlicht uses Doxygen comments all over the place. You can generate some nice diagrams using this software.
If you can live without the diagrams, you can have a look at the API online.
If you can live without the diagrams, you can have a look at the API online.
"Whoops..."
There is no need for you to get any Irrlicht UML diagram for 2 reasons.
1st, It is extremely easy to use, which is not a part of the Irrlicht engine object is a simple class which provides basic functionality that Irrlicht uses, all pretty simple and quite well documented, i must say.
2nd, UML diagrams are much more useful when describing the functionality of a system, (What the system does), not the procedures the system uses. (How the system does what it has to do)
I have already reversed engineered it, and the engine is really complex to understand in an UML diagram. Basically because most of the objects are defined on their own, inheriting from an interface. There is no clear relations between them, save that one.
What the users see, and only need, IMO, is a collection of interfaces, in runtime, the architecture of the engine process the functions it will use, so, in fact, an UML diagram is of very little utility here
1st, It is extremely easy to use, which is not a part of the Irrlicht engine object is a simple class which provides basic functionality that Irrlicht uses, all pretty simple and quite well documented, i must say.
2nd, UML diagrams are much more useful when describing the functionality of a system, (What the system does), not the procedures the system uses. (How the system does what it has to do)
I have already reversed engineered it, and the engine is really complex to understand in an UML diagram. Basically because most of the objects are defined on their own, inheriting from an interface. There is no clear relations between them, save that one.
What the users see, and only need, IMO, is a collection of interfaces, in runtime, the architecture of the engine process the functions it will use, so, in fact, an UML diagram is of very little utility here
"There is nothing truly useless, it always serves as a bad example". Arthur A. Schmitt