Bernard Kwok

Hi @lfl-eholthouser, I am just avoiding the problem of packaging / platforms altogether :). This is just a tiny change to add the logic to allow switching the font at...

Currently only the `doc` attribute on nodes or inputs are used though a `` element does seem inline with earlier discussion of separating docs from structure. If there are separate...

> The question that immediately popped in to my head when I read the code - was that it was very similar, if not the same as the code @bernardkwok...

One side note: It would be good to get some "real" geometry other than a sphere which doesn't test boundary cases. e.g. Would be nice to get the shader ball...

It's quite possible that not all shading languages and code generation variants will be supported as this restricted to code generation built into OCIO and does not produce a shading...

I guess if it is indeed doing a string compare then it should do a numeric value compare instead for `operator==`. Then string format would not matter. Would need to...

This all sounds very promising. I'd suggest the following interfaces to allow the same scoping flexibility as `operator==` 1. A `normalizeValueString(string)` utility that returns the normalized version of input string....

I will put up something for this. Note that the per Element scope is useful as I've had to write different equivalence code to work around the strict ordering check...

This makes sense for `node`s but not so much for `nodegraph`s especially as they can be dynamically added / removed. Also order of nodes in a graph shouldn't make any...

That is basically what I need. - That is -- is the document functionally equivalent even when not organizationally identical. - For interop, I'm round tripping from MTLX and back...