Well, I understand, but I use OSG as a base. That is to say OSG nodes are what is the higest level in the app. I could create a scene graph above OSG, but that's absolutely not what I want... So putting components "at my side" means here to put components in the OSG scene graph.
Proposal of putting a "ComponentContainer" object as a userdata could be suitable, but I wonder if it could be nice for OSG users to have this kind of features in the core (with a CMake option of course). Thoughts? Sukender PVLE - Lightweight cross-platform game engine - http://pvle.sourceforge.net/ ----- Mail Original ----- De: "Roland Smeenk" <[email protected]> À: [email protected] Envoyé: Jeudi 13 Août 2009 15h17:58 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: Re: [osg-users] Suggestion: Add components in nodes (aggregation) Sukender wrote: > Anyway, I could add my "ComponentContainer" object as a userdata to avoid > being too intrusive in OSG code, of course. > That's what I had in mind. We are using a componentized design ourselves. Simulation objects are composed of viewer and controller components much like the MVC pattern. OSG is used for implementation of the viewer components in the 3D graphical domain. So I think the componentization should be done at your side and not on the OSG side. Roland ------------------ Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=16187#16187 _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
