[Openicc] CUPS Color Management under Linux... (what is to do ?)

[edmund ronald]

Let's hope that nice Kai-Uwe writes a set of command-line tools first,
that we can then wrap various interfaces around for experimental
purposes. There is one idea in CUPS which I really like is that you
just point a browser at the right place and you have a GUI management
interface.

Edmund

On Fri, Feb 18, 2011 at 6:55 PM, Chris Murphy <lists at colorremedies.com> wrote:
>
>
> On Feb 18, 2011, at 10:38 AM, Kai-Uwe Behrmann wrote:
>
>> Am 18.02.11, 10:03 -0700 schrieb Chris Murphy:
>>> Anyone have Fedora 14 running on a machine? Check out the five network related GUI options:
>>>
>>> Network Authorization
>>> Network Connections
>>> Network Proxy
>>> Network
>>> Network Device Control
>>>
>>> And if you read the documentation many are referred to by a different name, like Network is referred to as Network Manager even though you won't find Network Manager in the GUI at all. It's called Network.
>>
>> Great example. Agreed, common terms are good usability.
>>
>>> The clusterF*ck that is terminology and consistency when it comes to something like networking, is exactly what will happen to color management if everyone has different preferences and this stuff diverges from common ground. Most users find these kinds of fiefdoms irritating as hell. I certainly find it annoying to have to spend hours figuring out how something as basic as networking is supposed to work. And while networking can certainly be complex, it doesn't have to be in five different panels, each with multiple tabs, some of which don't appear to do anything, others which overlap and seemingly contradict, on and on.
>>
>> Beside that I completly agree that it is an issue, we still live in a heterogenous software landscape with the open source operating systems. They do not have one kernel or one toolkit or one icon theme. The same applies for the PDF renderers, spooling softwares, CMMs, CMSes and so on.
>
> Which is why I think the conversations need to be about big picture stuff first. How users, files, devices interact and behave - how we want them to behave. Standardized terminology. Standardized interfaces.
>
> I think the interface and "workflow" aspect is the most important for cohesion in a given distribution and across distributions. That gives programmers something to aim for. If they want to use something other than GhostScript or CUPS, I don't think that matters to the big picture as long as the interface is consistent and the result at the end are the same (or very similar).
>
> Heterogeneity is a disaster for user experience. It just looks cluttered, and makes them go looking for drugs to kill the headaches clutter and extraneous information causes. Android is Linux based but it has substantially constrained the GUI to something approaching sensible. If no one is going to cede territory on their particular GUI manifestation, it will be very difficult to implement anything sensible. And it will tie up limited resources on wild goose chases and rabbit holes that eventually no one will care about.
>
> Chris Murphy
> _______________________________________________
> openicc mailing list
> openicc at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/openicc
>