[Openicc] ucmm 2
ku.b at gmx.de
Wed Apr 4 03:57:42 PDT 2012
ucmm as featured by ArgyllCMS is a nice convention and tool to store
monitor settings. Oyranos uses a slightly different set of keys and
values in a at the moment incompatible DB format. As suggested we would
like to switch Oyranos to a JSON format similar to that used by ucmm. The
advantage would be, that dispwin and Oyranos, including their front
ends, will use one common DB and see the configured devices of each other.
That way we get ride of conflicting DB's, which is irritating to users.
However, there are some minor issues to be decided befor full
compatibility can be achieved. Please read below.
Oyranos uses the keys from "ICC meta Tag for Monitor Profiles" .
These keys are all lower letter case except of the EDID_ prefix.
I would like to support "icc_profile_file" and "EDID_hash", preferedly
lower case key names. The later is intended for Argyll compatibility. In
case Argyll really wants a full EDID blob inside the DB, then I could
add it too. But please consider the mentioned monitor keys or the hash
value only, as a EDID blob can become big. Writing the key set as in
"ICC meta Tag for Monitor Profiles" would be welcome. libXcm has code to
do so conviently.
The equivalent for the key "NAME in ucmm is "device_name" in the Oyranos
DB. Obviously I prefere the later as I think it is more clear.
The next difference is, the JSON format does not need a numbering for each
device. So the devices can be stored inside a JSON array. Here is a
example DB file .
To align with the OpenICC Directory Proposal the DB files need to reside
inside the color/ path, e.g. /etx/xdg/color/settings/ .
IMO the file names of each DB should be verbose like in the
current implementation on SourceForge
How about patching ArgylCMS?
Argyll could be made reading a old style DB and convert that once to the
new format and erase the old config.jcnf after that for a smooth
I will send the OpenICC Configuration 1.0 DRAFT 2 in a separate email.
More information about the openicc