The first release based on YAML is now ready for download. Thanks to Malcolm for his help on this. An updated set of 0.7-format color configs (with many more color spaces!) will be posted

All LGTM, sorry most of these were introduced by me in the switch

Yep, I was thinking about doing that but it's not straight forward if we don't want yaml-cpp in the public interfaces for the Transforms()s. It could also be possible if we have some form of

These commits fix a bunch of bugs we discovered when testing our in-house apps on real production color configurations. * Yaml serialization fix, resource_path is updated properly * Relative path

Thinking about this topic further, I think the right thing to do it to have __str__ call through to the C++ ostream implementation for each class. (If that happens to use yaml, great! But it's not a

Looking at this quickly it would be a pretty small patch to add out << YAML::NewLines(3); Something along the lines of: --emittermanip.h-- struct _NewLines { _NewLines(int value_): value(value_)

This looks all pretty good to me - Can we call AddBaseTransformPropertiesToYAMLMap = EmitBaseTransformKeyValues - Can we call ReadBaseTransformPropertiesFromYAMLMap = ReadBaseTransformKeyValues, and

A bunch of changes related to yaml serialization: * ColorSpace transform a base Transform, instead of GroupTransform. * GroupTransform Yaml serialization supports nesting * Direction is now

I did see that comment, forgot to address it in the last post. I'd prefer to not expose the exact yaml serialization using __str__(). I'm pretty biased against "non-obvious" operator overloading

looks good to me. <malcolmh...@...> wrote:

- Added missing NAME arg to add_test() as this was failing to work on linux (worked on OSX, small cmake

LGTM, Did you see my comment in one of the threads about also supporting the .__str__() method?

LGTM

This makes the naming unified across C++ / python, and also gets rid of "getXML" (which is no longer xml). js/master commits: bd559608bdfbbc930634ef78eebd42cda83647da

* cleaned up malformed profile name (ocs_profile_version vs ocio_profile_version) * added better loading error checks * updated raw profile to new yaml

Folks, I've deleted the OCIO yaml branch. The main trunk now is up to date with all recent commits. -- Jeremy

LGTM. This was a compilation warning though, right? (It shouldnt have been an error). -- Jeremy <malcolmh...@...> wrote:

Works great on our linux distro now, thanks! (LGTM) I agree that it may make sense to include boost/shared_ptr.hpp, let me look into this. -- Jeremy <malcolmh...@...> wrote:

PyOpenColorIO.so wouldn't compile on linux http://github.com/malcolmhumphreys/OpenColorIO/commit/bb90284fa98161aae4ace74987246ae301ec1822 - Added some const_cast<char*>(..) ie. 'error: invalid

Hi, This should fix the link error on linux http://github.com/malcolmhumphreys/OpenColorIO/commit/7b016f274aefd8a4ce2deb7c72639351db8de0b4 I always forget how to create these diffs so I guess other