> W.r.t UserData I'd suggest placing osgSim container for the > extra OpenFlight flags, users can then do a dynamic cast of > UserData and get the info they want. The > osgSim::GeographicLocation class already serves this purpose.
Good point: This must be done anyway, to allow the app to access the data. I'll work on this ASAP and mull over the 1 or 2 plugins issue. Thanks, -Paul > W.r.t one or two plugins. Simplicity of high level > management would suggest using a single plugin. A single > plugin would also promote code reuse. But... if there isn't > much code reuse it could make the two sets of code rather unwieldy. > > If we do continue with two plugins then one could get the > .flt reader plugin to load the .flt write plugin on demand. > Or extend osgDB::Registry so that one can have multiple > plugins registered per format, but I feel this is quite a bit > of extra complexity for a small amount of gain in terms of > functionality - code complexity in osgDB::Registry itself > does need to be taken into consideration, personally I > already find it complex enough. > > Robert. > > On Tue, Mar 11, 2008 at 5:39 PM, Paul Martz > <[EMAIL PROTECTED]> wrote: > > > > > > Hi Robert -- I'm making good progress on the OpenFlight exporter > > plugin and wanted to bounce a couple ideas off you. > > > > There is a customer requirement to be able to preserve the > OpenFlight > > Object record flags that indicate "don't display at night", "don't > > display at day", etc. Currently, the importer ignores these > flags and > > just creates an osg::Group for an OpenFlight Object record. I'm > > thinking about saving these flags as UserData on the osg::Group. > > > > This brings about the question: Will there be two separate > OpenFlight > > plugins, one for import and one for export? This is the way I had > > originally envisioned it, but there is an issue with the osgDB not > > (fully) supporting two plugins for one extension; the only way I've > > found to get it to work is to explicitly load one of the > plugins first. > > > > If the import and export are separate plugins, then this > complicates > > sharing data structures such as the proposed UserData to > preserve FLT Object flags. > > > > If the two plugins should be combined, then I should > probably get to > > work on this now to save me work in the future. > > > > Thoughts? > > > > 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 > > > > > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-opensce negraph.org _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
