Paul Martz wrote:
That would be true if it weren't for the fact that .osgb is already in use: http://osgbullet.googlecode.com.
Oops! Sorry, I made a mistake. .osgb is _not_ used by osgBullet, but it is used in a related project that is still in development and not yet open source. That code is a candidate for inclusion in osgBullet in the future.
Regardless, I did ask that the .osgb extension be reserved for my uses back in June '09. So, to avoid an extension name collision, I'll ask that we consider an alternative extension for the new binary format.
I'll vote against using the same extension string for both ASCII and binary forms of OSG's (new) native format. It would complicate use of osgconv to convert between the two formats. Also, I like to know what is optimized for production loading and what isn't, and what can be opened in a text editor and what can't; using a different extension gives me this info at a glance.
-Paul _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
