[Oiio-dev] Check for ability to write an image to a type

[Larry Gritz]

Jonathan, did you ever get a chance to look at this?


> On Jan 18, 2017, at 8:10 PM, Jonathan Tilden (2K) <jonathan.tilden at 2k.com> wrote:
> 
> Ahh it totally did. I’ll take a look tomorrow. Thanks Larry!
>   <>
> From: Oiio-dev [mailto:oiio-dev-bounces at lists.openimageio.org] On Behalf Of Larry Gritz
> Sent: Wednesday, January 18, 2017 4:05 PM
> To: OpenImageIO developers <oiio-dev at lists.openimageio.org>
> Subject: Re: [Oiio-dev] Check for ability to write an image to a type
>  
> Jonathan, this may have fallen through the cracks on your end over the holidays, but I still have this PR pending and was wondering if it looked satisfactory to you before I merge it.
>  
>             -- lg
>  
>  
> On Dec 7, 2016, at 12:02 PM, Jonathan Tilden (2K) <jonathan.tilden at 2k.com <mailto:jonathan.tilden at 2k.com>> wrote:
>  
> Thanks Larry! We are still on 1.6.12 (primarily because we have to support py2.6, which is a much older version of MSVC). Let me check out what you have from the master, and see if I can backport it. Thanks!
> -J
>  
> From: Oiio-dev [mailto:oiio-dev-bounces at lists.openimageio.org <mailto:oiio-dev-bounces at lists.openimageio.org>] On Behalf Of Larry Gritz
> Sent: Tuesday, December 06, 2016 11:33 PM
> To: OpenImageIO developers <oiio-dev at lists.openimageio.org <mailto:oiio-dev at lists.openimageio.org>>
> Subject: Re: [Oiio-dev] Check for ability to write an image to a type
>  
> Addressed this with new queries in this code review: https://github.com/OpenImageIO/oiio/pull/1577 <https://github.com/OpenImageIO/oiio/pull/1577>
> 
> Do you work from master, or will you need this backported to 1.7?
> 
> 
> > On Dec 5, 2016, at 10:04 PM, Larry Gritz <lg at larrygritz.com <mailto:lg at larrygritz.com>> wrote:
> > 
> > You can ask for the full list of formats like this:
> > 
> > std::string formats;
> > OIIO::getattribute("format_list",formats);
> > 
> > And you'll get a comma-separated list of all the supported formats.
> > 
> > But that doesn't tell you which are read-only. You could figure it out, as you say, by trying to instantiate an ImageOutput for each one, but that seems wasteful. It would be better if you could directly query the set of writeable formats. I'll add a query like that, it should be straightforward.
> > 
> > 
> > 
> >> On Dec 2, 2016, at 12:05 PM, Jonathan Tilden (2K) <jonathan.tilden at 2k.com <mailto:jonathan.tilden at 2k.com>> wrote:
> >> 
> >> Hi!
> >> 
> >> I was wondering if there was a way to determine which types support write capabaility using OIIO. 
> >> 
> >> For example, I'd like to present a list of options in a save-as dialog that lists the image types that are 1) known to OIIO, and 2) have valid ImageOutput implementations. For example, PSD doesn't look to have a valid ImageOutput implemention, so I would not list that as an available type. 
> >> 
> >> I know you can check the results from trying to open the ImageOutput to determine if you can save, but is there a higher-level way to do this before even attempting to write the file?
> >> 
> >> Is this possible and if so, what would be the best way to get at it?
> >> 
> >> Thanks!
> >> -J 
> >> 
> >> ====================================
> >> Jonathan Tilden
> >> Principal Technical Artist
> >> 2K Games
> >> Email: jonathan.tilden at 2kgames.com <mailto:jonathan.tilden at 2kgames.com>
> >> Phone: +1.415.507.7623
> >> ====================================
> >> 
> >> _______________________________________________
> >> Oiio-dev mailing list
> >> Oiio-dev at lists.openimageio.org <mailto:Oiio-dev at lists.openimageio.org>
> >> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org <http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org>
> > 
> > --
> > Larry Gritz
> > lg at larrygritz.com <mailto:lg at larrygritz.com>
> > 
> > 
> > _______________________________________________
> > Oiio-dev mailing list
> > Oiio-dev at lists.openimageio.org <mailto:Oiio-dev at lists.openimageio.org>
> > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org <http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org>
> 
> --
> Larry Gritz
> lg at larrygritz.com <mailto:lg at larrygritz.com>
> 
> 
> _______________________________________________
> Oiio-dev mailing list
> Oiio-dev at lists.openimageio.org <mailto:Oiio-dev at lists.openimageio.org>
> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org <http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org>
> _______________________________________________
> Oiio-dev mailing list
> Oiio-dev at lists.openimageio.org <mailto:Oiio-dev at lists.openimageio.org>
> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org <http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org>
>  
> --
> Larry Gritz
> lg at larrygritz.com <mailto:lg at larrygritz.com>
>  
> _______________________________________________
> Oiio-dev mailing list
> Oiio-dev at lists.openimageio.org <mailto:Oiio-dev at lists.openimageio.org>
> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org <http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org>
--
Larry Gritz
lg at larrygritz.com


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openimageio.org/pipermail/oiio-dev-openimageio.org/attachments/20170316/90fdd08b/attachment.htm>