Hi Robert, > > Hi Peter, Robert, and all > > Thanks... but this is my first post... I've been happily watching the > discussion so I can't take any credit, apart for great patience ;-)
Ahah! This was an insidious way to get your attention! You fell in the trap! :-D > > Thank you for your ideas. I think the metadata container put in > userData is the simplest way. And I fully agree there should be some > minimal base classes to support it in core OSG. > > This has been my preferred option for a while. This topic been > discussed before over the years, and I think a member of the > community > proposed a solution and may have even come up with a partial solution > so it would be worth looking through the archives. Thanks. I'll do. > Having the ability to read/write the data using the new serializers > is > the obvious thing to do. Meta data could even just be used to store > a > unique ID for those who want to use such approaches. > > > > So... Who's for that solution? If so, any idea about implementation > details, or requirements? > > Ooo I think I'll duck for cover w.r.t implementations, I have plenty > of other issues to tackle with getting the OSG ready for 3.0 to not > worry about other stuff. Hmmm... Would you agree if I gradually propose submissions in that way? I mean I'll stick to the idea of metadata container, but I won't do everything in a row, so will you accept to integrate such sumbissions? Cheers, Sukender PVLE - Lightweight cross-platform game engine - http://pvle.sourceforge.net/ _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
