> Its a pretty unusal instance - having two plugins > implementing support for a single format,
Hm. I thought I recalled a post from you saying that two plugins for a single format, one for reading and one for writing, should work. (I tried to find this in the archives but they don't seem to go back far enough. Perhaps I am not recalling the post correctly.) > so I'm inclined to > look for specific workarounds for this case rather than > introduce greater complexity into the internals of osgDB. > > One thing I'd do right now is preload your writer plugin > rather than have osgDB load it automatically through > extensions, your writer can than fail on the readNode calls > and let Registry do its thing in finding the OpenFlight plugin. Yes, I thought if this last night after posting. Tried it this morning and it works fine. Thanks for the workaround. > Longer term, will you plugin be open sourced and an potential > candidate for merging with the core OSG's plugin? Yes, it's open source, will be licensed under the OSGPL, and will be contributed to you once it's complete, probably Q1 '08. I'm not inclined to combine this export plugin with the existing import plugin, as they really are two different projects with two different feature sets. I don't want to restrict the exporter by design decisions made for the importer. Paul Martz Skew Matrix Software LLC http://www.skew-matrix.com 303 859 9466 _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
