* cleaned up malformed profile name (ocs_profile_version vs ocio_profile_version) * added better loading error checks * updated raw profile to new yaml format js/master commits: ecf370fdc3e872b4ec78e0

- Added missing NAME arg to add_test() as this was failing to work on linux (worked on OSX, small cmake bug) http://github.com/malcolmhumphreys/OpenColorIO/commit/8e80331866f003b99bbc2bfae627b730980cf

looks good to me.

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

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 load

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 tomorrow. Ve

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

- removed some #pragma's which were breaking the build on linux, there are a few more warnings now to do with template<> visibility in yaml-cpp but it should now link on linux (was working on OSX)http

- added yaml-cpp r443 which contains the new YAML::Newline emitter manipulator http://stackoverflow.com/questions/3982901/how-to-emit-a-blank-line-using-yaml-cpp - added some 'out << YAML::Newline' to

Do you think the 'reference' colorspace should in a separate section in the profile? This would be similar to the PCS in the icc world. It could be an extra line 'reference: !<ColorSpace> ...' before

- Inital pass at GCC visibility http://gcc.gnu.org/wiki/Visibility to hide unnecessary public symbols in an effort to maintain ABI - Added -fvisibility-inlines-hidden and -fvisibility=hidden to the ya

- converted configs/testing/config.ocio to YAML - added OpenColorIOTest to the ctest run ie 'make test & make test_verbose' - some test output was being written to /mcp changed this to /tmp for now ht

Looks good to me. I'll commit this after I finish working through the search path checkins (tomorrow, hopefully). -- Jeremy

Is there a reason to not remove yaml-cpp-0.2.5* from ext? Other than that, looks good to me. -- Jeremy

Nuke plugins wont crash if the specified $OCIO is invalid. This issue is related to calling the nuke IOP::error method during construction, but in the meantime we can at least prevent a crash by not c

We already required cmake 2.8 (for ExternalProject usage), now this is explicit. commits: 949855cca45431a6e813ac3b6f3688de0799f379

OCIO namespace #define is now configured using the CMAKE configure_file mojo. This makes namespace errors far less likely, as it's baked into the header that's a part of make_install. commits: d00581c

Malcolm, I don't see that the reference space should be separate in the profile. It's important, but it is just a role. Where the reference sits in the xml or yaml should matter much. Although quite a

Color profiles suitable for OCIO 0.7 have been posted, along with basic documentation. See https://sites.google.com/site/opencolorio/profiles for additional information. Note 1: Thanks to Joseph Slomk

We're starting to get some actual OCIO users, so it's time to start a new mailing list: http://groups.google.com/group/ocio-users This will focus on issues related to color profile development, artist