2025-01-13 - OCIO UX Working Group Notes
Date
January 13, 2025
Participants
Mark Titchener (TSC) - Foundry
Doug Walker (TSC Chief Architect) - Autodesk
Joseph Goldstone
Barry Dempsey
Apologies:
Michael Dolan (TSC) - Epic Games
Discusson
First WG call this year so a relatively short catch-up. Primarily a recap on where we finished up last year.
We would like to add more UI/UX examples to
ocioviewto form the basis of the UX implementation guide.Ultimately we would like the UX guidelines to be included in/alongside the main OCIO documentation.
Doug has set up a Github Project for the UX WG.
Mark to start breaking down the work into tasks. The basis of this being our original UX Google doc.
Mark spent some time using
ocioview. I’ve written some thoughts/bugs in a Google doc for now but I’ll start logging them as issues on GitHub.At the previous meeting we discussed whether many people were using
ocioviewas we haven’t heard much in the way of feedback or bugs.One reason may be that getting it running requires a bit of knowledge/effort.
We wondered if it could be separated out as a PyPi package with a dependency on OCIO. It still requires quite a lot of other dependencies though.
Michael said he would like to consolidate the graphics engines being used as there are currently quite a few (possibly use pygfx for everything?).
Shortly after the last meeting Thomas Mansencal submitted this PR to add support for Astral’s uv which could lower the bar to entry and get more people using
ocioview.
Joseph planning to take a look at
ocioviewwhen time permits.Had questions about whether
ocioviewcould support full use of HDR capable displays e.g. XDR on MacBook Pro laptops.Mark - I believe this should be possible to implement with Qt/PySide6 i.e. tagging the image buffer accordingly for the OS (to massively oversimplify).
Action Items
ocioview issues/feedback as GitHub Issues.