[Openicc] Fedora CM, was: Google Summer of Code . . .

[Kai-Uwe Behrmann]

Am 20.05.10, 13:09 +0100 schrieb Richard Hughes:
> On 20 May 2010 10:15, Kai-Uwe Behrmann <ku.b at gmx.de> wrote:
>> CM integration in Xorg, GTK, Cairo and so on is fine. Chris' questions came
>> up as he had read that you want to work on CM preferences, device detection
>> and configuration and integration into the toolkit (Gtk). This sounds
>> exactly like CMS work. And as long as we have no other and better term this
>> one will easily be used.
>
> Well, I don't feel GCM is a CMS. It's just a central place to:
>
> * get the profile associated with a device
> * assign profiles to devices
> * create profiles for devices
> * change the session defaults for CM aware applications
> * view details about profiles

Hmm thats much of what Oyranos does. Ok viewing details about profiles 
is not directly part of that. So not much difference but the Oyranos is 
and GCM is not.
(/me is stunning)
But sometimes new terms need time.

>> Qt is rather large for a CMS and in C++. GObject seems far from being easily
>> debuggable. In contrast the used object system is relatively lightwight and
>> very well debuggable with standard means.
>
> I've not found a bug in GObject in 5 years of using it. My point was
> that someone else had already invented an object and type system, and
> it's already been debugged. Re-inventing the wheel (and forcing people
> to use your custom object system if they use your library) isn't

There are enough people who avoid GObject completely because of its 
design not just of being C. That you are proficient with GObject is nice 
for you and all who are too. For me it feels more like autotools.
Nothing which really adresses my points. Code derived from GObject must be 
debuggable, which is hard despite of GObject maybe being bugfree.

> palatable to most maintainers. Adding to that, not using pkgconfig
> makes it even harder to integrate.

Pkgconfig is in git.

>> Naming and their translations are hard to keep in sync. Do you have some
>> special project in mind, where it happens that different projects use the
>> same names for the same thing?
>
> I don't think that there is much to standardize. "perceptual" ->
> "Perceptual"  and that kind of thing looks pretty obvious.
> Translations are also different depending on your DE, as a GNOME "Log
> out" may be a KDE "Exit session". I think it makes sense to agree what
> the enumerated constants should be, and the technical word, and just
> let the translators do their thing. GCM refers to a profile with a
> VCGT tag as having "display correction" and that kind of thing
> probably needs discussing also.

For one thing, you use all four rendering intents for proofing.


regards
Kai-Uwe Behrmann
-- 
developing for colour management 
www.behrmann.name + www.oyranos.org