Re: FileTransform interface changes


Jeremy Selan <jeremy...@...>
 

Would FileTransform::setOptionString(...) introduce the same complexity?

Say you wanted to create the OCIOFileTransform in nuke. In this
system, would you expect to see a single knob, 'optionString', or
multiple knobs (cccid, etc)? If a single knob is exposed, how would
the user know what to set? Would we just provide helptext which
documented the options?

What would the string format be? JSON/YAML?

What keys would be supported in 1.0? shaper interpolation + cccid?
How about normal interpolation?

-- Jeremy

On Fri, Sep 16, 2011 at 2:40 AM, Malcolm Humphreys
<malcolmh...@...> wrote:

Could we find a halfway point?
FileTransform::getOptionString()
FileTransform::setOptionString(const char * id)

This could take a 'token1=value1;token2=value2' string. This is a bit ugly
but does allow for the interface to be not so format specific while also
allowing to add other options if they are needed for fixing bugs on the path
to 2.0.

eg.
FileTransform::setOptionString("CCCId=myfavshot;");

Join ocio-dev@lists.aswf.io to automatically receive all group messages.