Thank you very much smilem. Software piracy is not our main concern, we just don't want people to use our solution without fully understand it.
Let's take a technical example: softproofing. To do proofing, you have to specify the screen profile at an OS level and then within an application (let's says photoshop), you define the printer profile, rendering intent, the CMM, and other options…
We choose to bypass the OS and to have a built in CMM which makes our software multiplateform (MacOS, Windows, Linux). This also means that all color management options are gathered in one place as you can see in the trial version. Options are sorted in a panel ( called "Color Flow" ) the following way:
1. source profile: where your image come from? this is where you can assign it another profile or convert it to any other profile
3. destination profile: printer or screen you want to simulate. Here you choose the rendering intent and this is where you can compute separations
4. virtual illuminant: to simulate lights. Proofing is usually done in D50, here you select any illuminants you want, even measured spectra.
5. screen profile: this is the current screen profile
6. ambient light: plug a spectro, measure ambient light in your office, and it is used in computations to precisely display colors
2. In between 1. and 3. you can insert and design gamut mappings, color transformations and device link to go from source to destination profile.
For us, this color flow looks natural and simple and allows you to simulate any configuration. Unfortunately, this concept, which is the basis of our viewer, is not so easy to understand for most people. If you have any idea on how to design this panel so that everybody understand it at the first look, well, you have my full attention.