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?
On Fri, Sep 16, 2011 at 2:40 AM, Malcolm Humphreys