Review Request: include KolorManager in kdegraphics

[Stas Verberkt]

> On Wednesday, March 14, 2012 14:22:54 Sune Vuorela wrote:
> There's a few major points which I think if can be answered would
> help clarify what that would look like:
Indeed, this discussion is going places, but does not really come up with
answers. As someone who has no understanding of colour managemant
whatsoever
and without any bias, I, indeed, see some questions to be answered, in the
hope this will provide us with some structure.

* First of all, how expensive would it be to provide a small abstraction
allowing drop-in replacement of Oyranos by colord and the other way
around, e.g. have one interface and two backends?

* If the platforms supported by the backend are different from the
platforms targetted by KDE, how do we cope on these other targets? Should
we answer question one with: indeed one interface, however, four backends
-- given whatever Windows, MacOSX, or whatever platform you like and KDE
targets uses.

> * What of those extra features are "a big deal" for a desktop environment
> (i.e. would specifically would we *not* be providing our users by
> supporting
> colord and not supporting Oyranos).
>
* Maybe reformulated to: What are the target audiences of the
applications? If one is more aimed at the default user and another at
certain professionals this calls for a different view at the situation. As
some people tend to say: one size does not always fits all.
Furthermore, I expect that there should be some communication between the
goals of KDE and those of the solution we prefer.

> * What feature(s) does Oyranos support over and above colord? I think
> we're
> all in agreement that Oyranos does /more/, but what specifically does that
> mean?
>
* A feature-wise comparison, although that quite easily gives a false
impression. For example, a product may have way more features, but because
of some fundamental design decisions we do not like, or the other way
around, something may be over simplified. Thus, such a comparison requires
real expertise and no bias.
It would probably be best if the developers explained what makes there
software great and not so much what makes other software less worthy.

> * Finally, assuming no direct support for Oyranos in a KCM, what would be
> needed to allow a user to use Oyranos in a KDE Desktop? E.g. let's assume
> that
> colord is always available on Ubuntu and so KDE can interact with it, but
> the
> user wants to use Oyranos... what does KDE have to do to allow the user to
> manually control their color profiles without a KDE daemon interfering?
>
* Maybe this should be asked for all possible solutions? Also, given the
fact that there are people working or willing to work on KDE integration
of both, this hould not be too much of a problem, I would guess.

As a final remark, please note that the diversity in the open source world
in general and the Linux world specific is, most of the time, considered a
good thing. Competing projects are generally responsible for more
innovation than monopolies.
If we can embrace this, it would be wonderful.