I recently added the ability to load the extension map from a configuration file. Currently the application has to call into the registry and pass the name of the configuration file, then the Registry sets the map contents from the file.
As I made that change, it did bring up the discussion of runtime plugin discovery. You might search the archives for about 1 month back to see what was discussed. -Paul > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Hartmut Seichter > Sent: Wednesday, February 21, 2007 3:07 PM > To: osg users > Subject: [osg-users] runtime plugin discovery > > > Hi there, > > I was wondering how others here around would solve the > following "feature": > > An end user application should be able to fill up the file > dialog with a list (to filter files) of available 3D model > formats (or Image file) depending on what plugins are known > to the registry. > > Brute force version of this would be to load all osgdb_* > plugins and query the map (unfortunately protected) ... but > there we run into all kinds of problems with: which plugin > was first? hence, which one should be used/ has priority as > the alias will be overwritten by the latest one loaded. > > Ideally osgDB::Registry should be really a registry which > doesn't hardcode the alias maps. I would argue the plugins > themself know better what they can be used for. And I think > somebody already seen the problems: > > line 191 in osgDB/Registry.cpp: > // really need to decide this at runtime... > > Any thoughts welcome! > > /Hartmut > > > > > > _______________________________________________ > osg-users mailing list > [email protected] > http://openscenegraph.net/mailman/listinfo/osg-users > http://www.openscenegraph.org/ _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
