...and it attempts to load exactly one plugin, and if the IO operation fails, osgDB returns "failure" to the app. It does not go out looking for additional plugins to load. This is a problem if there are multiple plugins supporting multiple different formats that happen to share the same extension string. Unless the app preloads the plugins (which kind of defeats the purpose of plugins), current unmodified OSG will not support different plugins supporting different formats with the same extension.Only if no plugins can handle the read/file attempt does th Registry then attempt to load a new plugin from disk based on the extension name. If you'd like to keep OSG as it stands, then it seems reasonable to have some kind of public "extension registry" such as a wiki page, where developers can lay claim to certain extension strings so that we avoid the situation described above. I'd like to lay claim to ".osgb", ".skel", and ".skeleton" for my own work, as it seems reasonable that someone could possibly try to make their own format with extensions like those somewhere down the road, and I want to avoid the conflict that would occur from multiple plugins supporting different formats with the same extension string. I realize this "claim" is only as good as the ether I'm writing in. :-) -Paul |
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
