Hi there - This is something that has been percolating in my head since the OSX instructions thread - though the instigator was more likely the QT support discussion.
Who is the target audience for Open Image IO? I see it as an open source Image IO library for developers to utilize in graphics applications and pipelines, in some way. I guess my view has always seen it as a means of reading/writing different formats useful for rendering and image manipulation with some extremely handy texture caching built in ( from my bubble of vfx and animation production ). It feels that although you'd like to make sure there is a path of least resistance for use and adoption, there should be some sort of understanding as to the technical prowess of the user in question. This is not to say those who pointed out the need for a bog simple means of installing or clearer instructions aren't technical, but what should be expected of a user? More so - the discussion on implementing QT support had me a little concerned, I agree that QT is a format that many use and rely on for image processing - but from a library standpoint the idea of OIIO inheriting all of the baggage that goes along with QT gives me the willies. Plus, QT support doesn't seem to fit into what my perception of OIIO's scope is ( again, from my bubble ). I imagine this would be on opt in choice, but with the number of opt in's already available how am I sure that my OIIO is compatible with someone else OIIO? Some of this may be due to some of the GSOC discussions and what should/shouldn't be considered an interesting project, once the dust settles it will all be more clear. I guess it just feels like there's potential for aspects of OIIO to end up with feature creep and I wonder if there's any merit for OIIO Core and then OIIO Extensions or something similar to differentiate between the raw core implementation of loading images and texture caching vs. IV and QT formats? There's a very good chance I'm on my own and everyone else is completely happy - but I thought I'd bring it up in case there's a perspective I've missed. Thanks, Colin _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
