[Openicc] d-bus in CUPS server? [was: colord 0.1.0 released!]

[Kai-Uwe Behrmann]

Am 14.01.2011 02:11, schrieb Graeme Gill:
> colord joins/competes with Oyranos as a convenient way of managing
> profile (as well as ArgyllCMS's jcnf to a limited degree).
>
> I'm wondering though, whether colord is a solution that will work
> with more than just GNOME ? How about FreeBSD :-) ?
>
> (i.e. how cross UNIX-like-platform or desktop is it ?)

cupsdRegisterColorProfiles() appers to be acting in
server side code. So the desktop d-bus messages are supposed to
hook really into CUPS server?

cupsdRegisterColorProfiles() modifies the PPD during its parsing stage.
I guess that is the stage, where the PPD is already flattened out from
all user decisions and contains just the final options to apply to a
given job.
With the actual plans in the common print dialog (CPD) there
is a good chance to modify the PPD already there and avoid the
trouble of hooking from a desktop daemon into server side code.
Given that there was already interest in using a printing profile in CPD as
signaled by Peter Sikking [1], the usability expert for CPD, I think
placing
the ICC profile inside CPD in the pipe would lead to a much cleaner
architecture. That would as well happen in client side land, where
d-bus is not become that much a problem.


kind regards,
Kai-Uwe

[1]
https://lists.linux-foundation.org/pipermail/printing-architecture/2011/002189.html