Re: advice, supporting dynamic color space additions to config
Haarm-Pieter Duiker <li...@...>
toggle quoted message Show quoted text
If you're working in a single facility and have some way of prompting configs to be regenerated, the Python API gives you most of the functionality needed for an inheritance model.
Something along the lines of a 'global' config module which defined the base color spaces, views, displays and so on followed by show/shot/sequence specific modules that could import that global config module, use it to generate a Python config object and then modify that config object as necessary before writing the config to disk could work for a single facility.
On Thu, Sep 25, 2014 at 3:53 PM, Steve Agland <sag...@...> wrote: