From: ocio...@... [mailto:ocio...@...] On Behalf Of Jeremy Selan
Sent: Thursday, January 13, 2011 10:11 AM
Subject: Re: [ocio-dev] Review: Building/config related docs
Oh, and an observation: we now essentially have two masters for the
docs, the inline documentation, and the webpage version. My
inclination is to treat the git version as the master, and then to do
periodic html / pdf drops to the website. I'm thinking I could make
docs and post them for every dot release. Thoughts?
On Thu, Jan 13, 2011 at 10:08 AM, Jeremy Selan <jeremy...@...> wrote:
Looks good to me.
These commits were all on the same topic, so I merged them into a
single checkin, "Documentation cleanup".
On Thu, Jan 13, 2011 at 6:11 AM, dbr/Ben <b...@...> wrote:
Added Python versions of most of the C++ usage examples (except the GPU one,
as the Processor.getGpuLut3D method isn't exposed). Might not be terribly
practical code, but it's a nice demo of the Python bindings (plus not being
hugely familiar with C++, I find it extremely useful seeing both side by
Other commits relate the docs, mainly the setup page:
Link to license page from FAQ
"Building from source" page. Not totally sure this is best-practices etc,
but seem sensible and looks similar to the existing INSTALL file
Mention the LD_ and DYLD_LIBRARY_PATH env-vars on setup page
"Nuke configuration" section on setup page
...and reorganise the headings for the above changes, to keep the ToC tidy
(rST's heading notation is slightly.. odd)
Temporarily copied a built version of the updated docs
Shall do the CLA tomorrow afternoon!