Robert Osfield wrote:
Hi John,
On Mon, Dec 14, 2009 at 10:21 PM, Jan Pečiva <[email protected]> wrote:
OSG plugin takes one look at the "foo" extension and returns an error.
(This is correct behavior; the .osg plugin doesn't support the "foo"
extension.)
This is exactly the point I am trying to point out! The plugin reports that
it does not support the extension!
I am telling that this is NOT a good idea. And finally, the discussion about
"design" ideas can start.
For your it's NOT a good idea. So please couch it without the
capitals and within the context of your opinion, and please don't
"telling" us, we aren't children.
I am sorry. I started to be nervous because I had to repeat the same
thing few times in the discussion. Anyway, OSG is very good and well
designed system. I was just trying to point on a speck that can be
improved in my opinion. Sorry for a strong words.
[...]
The osgDB alias is not a scheme for co-opting an existing plugin to
handle a file extensions that isn't a recognized one. One might
propose an additional scheme for doing this, and we might debate the
merits of this, personally I'm rather dubious that it's that a great
thing to do, and given we've gone a decade without needing this I
would suggest that it's not at all a common requirement.
Thanks. This is an answer in this discussion. So, you prefer not to
change the design idea and meaning of "alias". Let's close the
discussion with this conclusion. I am not planning to reopen it unless
other people come up with the same topic / the same problem.
I don't know if you are aware but one way of tackling what you are
trying might simply have your own plugin as your were originally
talking about and have it open the file you want with whatever
extensions you have as an istream and then load the plugin you want to
do the actual loaded and pass this to it. Given what you after is
such a niche requirement then I would think this is a sensible route
to take rather than expect intrusive changes to the OSG to achieve
what you specifically want.
I will do, although it is nearly more work than to, say, "improve" these
aliases. Inventor plugin (ReaderWriterIV) does not have istream methods
implemented. I will consider to implement them and submit them (together
with bunch of fixes I have done in plugin past month, including shader
support...).
Anyway, why these aliases should not be automatically in plugin's
extension support list? Non-supported alias is non-sence - why to create
alias to plugin that refuses it to load? It is just confusing in my
eyes... and it is few lines of code.
John
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
