Ookala Modular Calibration Framework

I can't defend or explain Xrite's policy/philosophy on this. It is what it is and since it's their code, we'll just have to live with it.

Regarding use of ArgyllCMS code, the current code base supports customization in a fairly straightforward manner. A stub-example driver is provided with the code so that any developer could (if they wanted to) link to other interfaces such as ArgyllCMS. The basics of control are fully documented from the interface layer, so there shouldn't be anything is standing in the way of such a linkage.

At this time, we have no plans to do more than what's currently available due to lack of available HP resource and, frankly, due to lack of community interest. Could you explain more as to what would be of use to you?