<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'DejaVu Sans'; font-size:9pt; font-weight:400; font-style:normal;">On Thursday 20 August 2009, Kai-Uwe Behrmann wrote: > Am 20.08.09, 18:13 +0400 schrieb Alexandre Prokoudine: > > IIRC, it has functionality similar to what Oyranos does (or is > > supposed to do) -- applying CMS settings consistently for the CS. > > For Oyranos is at least a front end needed like the in development being > Kolor Manager. And there too, I think the logical position of CMS settings is in "KDE Settings" or "Gnome Settings" (or "Windows Settings"). This doesn't prevent application to link directly to those component, we can imagine having a menu entry called "manage your asset" which open dolphin/nautillus in the directory with assets. And I do intend to embedd the kolor manager panel in Krita's configuration dialog, when I will have time to start using oyranos in Krita. We have to keep in mind that Adobe do some of the thing it does because they don't have control on what can be done at each level of the OS, while we have the opportunity to do the right thing :) -- Cyrille Berger</body></html>