Debian Codegraph @

doc/website/specifics.html

raw
1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
2 <html xmlns="http://www.w3.org/1999/xhtml">
3 <head>
4 <title>colord - What is colord?</title>
5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
6 <link rel="stylesheet" href="style.css" type="text/css" media="screen"/>
7 <link rel="shortcut icon" href="favicon.ico"/>
8 </head>
9 <body>
10
11 <p>Back to the <a href="index.html">main page</a></p>
12
13 <h1>How it works:</h1>
14
15 <img src="img/architecture-plan.png" alt="[logo]"/>
16 <p>
17 <i>General architecture plan</i>
18 </p>
19 <br/>
20 <br/>
21 <br/>
22 <img src="img/cups-plan.png" alt="[logo]"/>
23 <p>
24 <i>CUPS query architecture plan</i>
25 </p>
26 <br/>
27 <br/>
28 <img src="img/cups-detailed-plan.png" alt="[logo]"/>
29 <p>
30 <i>Detailed CUPS integration plan</i>
31 </p>
32 <br/>
33 <br/>
34
35 <h2>Mapping the device to the profile</h2>
36
37 <p>
38 The configuration of devices to profiles is stored in the colord mapping
39 database, which is <code>/var/lib/colord/mapping.db</code> by default.
40 The schema is really simple, and as follows:
41 </p>
42 <pre>
43 CREATE TABLE mappings (id TEXT PRIMARY KEY,device TEXT,profile TEXT, timestamp INTEGER DEFAULT 0);
44 </pre>
45
46 <p>
47 Multiple profiles can of course be assigned to the same device.
48 Persistent devices and profiles can also be saved to the storage database,
49 which is <code>/var/lib/colord/storage.db</code> by default.
50 The schema is again really simple, and as follows:
51 </p>
52 <pre>
53 CREATE TABLE devices (device_id TEXT PRIMARY KEY,device TEXT);
54 CREATE TABLE properties (device_id TEXT,property TEXT,value TEXT);
55 </pre>
56
57 <h2>Setting the system default</h2>
58 <p>
59 One user may want to set the default for all users.
60 We cannot reference files in <code>/home/foo/.icc/</code> when logged in
61 as user bar, as the user will not have access permissions, or in the
62 worst case, <code>/home/foo</code> may be encrypted and inaccessible even as root.
63 For this reason, colord copies the ICC profiles to a system-wide directory,
64 <code>/usr/lib/color</code> that is per-machine and accessible to all users.
65 </p>
66 <img src="img/polkit.png" alt="[PolicyKit authentication dialog]"/>
67 <p>
68 It is <a href="http://lists.freedesktop.org/archives/openicc/2010q2/002167.html">encouraged</a> that other CMS implementations also read ICC profiles from the per-machine
69 <code>/usr/lib/color</code> directory.
70 </p>
71
72 <h1>General points:</h1>
73
74 <p>
75 I think most of the CMM functionality can be (and should be) integrated
76 into the platform, e.g. <a href="http://www.gtk.org/">GTK</a> and Cairo.
77 </p>
78 <p>
79 It's my opinion that it's best to have two different applications for
80 something that share a common specification, rather than trying to be
81 a jack-of-all-trades.
82 It's a cliché, but KDE users do want options, and GNOME users do want
83 things to 'just work'.
84 You can't design a library, or even an application for those different
85 user types.
86 </p>
87 <p>
88 I do think the concept of a <i>monolithic CMS</i> is flawed.
89 Color management has to be integral to the stack, so Xorg, GTK, Cairo,
90 etc. all have to play their part.
91 You can't really push a monolithic library when you need to interface
92 with so many parts of the stack.
93 I see all the heavy lifting being done by cairo, lcms and
94 <a href="http://www.argyllcms.com/">ArgyllCMS</a>.
95 </p>
96
97 <p>Back to the <a href="index.html">main page</a></p>
98
99 <p class="footer">
100 Copyright <a href="mailto:[email protected]">Richard Hughes 2011 - 2013</a><br/>
101 <a href="http://validator.w3.org/check/referer">Optimized</a>
102 for <a href="http://www.w3.org/">standards</a>.
103 </p>
104
105 </body>
106 </html>