Hi Robert, I spoke w/ Andrew and Mark of the COLLADA group, and yes we'll migrate the OSG plugin source repository from SF to the OSG core. I'll wrap up some loose ends and make a win32 3rdParty binary of the COLLADA DOM. I'll send via osg-submissions tomorrow or so.
Cheers -- mew Robert Osfield wrote: > Hi Mike, > > On 8/13/06, Mike Weiblen <[EMAIL PROTECTED]> wrote: > >> > Anyway, on COLLADA front, thanks for the pointer to the latest plugin. >> > We really need to document this. >> >> Yes, definitely. And some nice packages on SF. >> >> FWIW depending on how the OSG v1.1.1 release schedule aligns w/ other >> tasks, I >> may try to include the plugin in the next win32 binary installer > > > That would be great, a first step towards tigher integration. > >> > Longer term, would Sony be happy to see it moved into the core OSG >> > distribution? >> >> Have to consider how that would work, given the additional dependency >> on the >> DOM. But that decision might best be left for the future primary >> maintainer ;-) > > > All plugins are all optional, something we can enable/disable so I > don't see the extra dependency as a big issue. Hopefully a future > build system will make this easier on platforms like VS and Xcode. > > The reasons why I'd like it integrated into the core are: > > 1) Keeps the COLLADA plugin up to date with all OSG release. > 2) Promotes the COLLADA plugin as a standard means of data interchange > 3) Exposes the COLLADA plugin to many more testers and users > 4) All of the above accelerate the development of our COLLADA plugin and > help put some momentum behind having a standard integerchange format. > > Question that would need to explore are things like the licensing of > the dae14 plugin. I see that the ReaderWriterDAE.cpp is under your > 3DLabs copyright and under the OSGPL. However, the rest of the .h > and .cpp's have no copyright assignment or license details. Which > ever these end up being they'd need to be compatible with at least the > releasing as part of the core OSG. > > Another aspect of integrating things into the core will be that I > could assuming responsibility of maintaining it, its not a big code > base. However, supporting it as seperate project would be much more > of hasel than I'm willing to take on, so if its to stay seperate > you'll need to find another maintainer. > > Robert. _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
