Hi Robert -- If you don't see this as an issue that merits a mod to osgDB, then I will not pursue the issue and will not submit a change. (Giving this some thought overnight, it seems like I can provide a solution to my clients in a middleware library that avoids mods to the app and also avoids changing osgDB.)

Extension string conflicts do occur. I have encountered this issue in work I've done for my clients. Both my client and I have agreed that it rather defeats the purpose of the plugin system to have to explicitly preload a plugin, but so far that is the solution we've employed.

So the stimulus for this current thread is to avoid the situation in the future, as I create plugins that use rather generic-sounding extensions like ".osgb", ".skel", and ".skeleton".

Recently, someone posted a submission to OSG to load point cloud data in a plugin using the extension ".txt". This seemed ripe with potential for extension string collisions; I believe I (and others) steered him away from that extension, not sure what the outcome was.

Paul Martz
Skew Matrix Software LLC
http://www.skew-matrix.com
+1 303 859 9466



Robert Osfield wrote:
Hi Paul,

Up till now extension name collision hasn't been an issue.  Is there a
reason why you think that this will become an issue now?   In general
having multiple plugins using the same extension will be an
exceptional case and one that can be tackled by pre-loading.  One
could possible have the Registry loading plugins based on a wildcard
i.e. osgdb_ive*  but until we directly see an issue that is going to
affect more than a handful of users I think it would be to keep osgDB
as uncomplicated by extra stuff like this - it's already complex
enough.

With your own new extensions I think it would be best to introduce
these and the motivation behind them, whether they will be open
sourced etc.  A public discussion on any possible collisions and how
to resolve them could be done.  Putting list of extensions into wiki
is a good idea but mainly as an on going reference, we'll still need
the public discussion to highlight the potential problems as the wiki
will get overlooked most of the time.

Robert.



  
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to