diff options
author | Richard Hughes <richard@hughsie.com> | 2011-06-19 22:57:54 +0100 |
---|---|---|
committer | Richard Hughes <richard@hughsie.com> | 2011-06-19 22:57:54 +0100 |
commit | 01f87a39129c4896b91e253f19432a92fe2c58e6 (patch) | |
tree | daa1f635b19dd34b167f6ea4a68384032a76cad9 /doc/device-and-profile-naming-spec.txt | |
parent | fc14fa6f8dba808b7f7fa3f0d8aa260ab521413f (diff) | |
download | colord-01f87a39129c4896b91e253f19432a92fe2c58e6.tar.gz |
trivial: Update some of the documentation to reflect reality
Diffstat (limited to 'doc/device-and-profile-naming-spec.txt')
-rw-r--r-- | doc/device-and-profile-naming-spec.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/device-and-profile-naming-spec.txt b/doc/device-and-profile-naming-spec.txt index 8ec13e0..a870a1c 100644 --- a/doc/device-and-profile-naming-spec.txt +++ b/doc/device-and-profile-naming-spec.txt @@ -17,11 +17,11 @@ This also allows applications to create new types of devices and profiles in the CMS without the CMS being aware of all the nuances of what the application is trying to do. -This is illustrated well, with gcm-session creating xrandr devices for -colord and also auto-creating profiles based on the device EDID. +For an example, gnome-settings-daemon creates xrandr devices for colord +and also auto-creates profiles based on the device EDID. When this happens, colord saves the device->profile mapping and on next session start re-maps the devices which causes the session policy the -be applied in gcm-session. +be applied in the gnome-settings-daemon color plugin. In this way, the CMS knows nothing about XRandR and everything works transparently and correctly. |