[Openicc] GoSoC 2011: CPD and target printing
edmundronald at gmail.com
Thu May 12 18:54:25 PDT 2011
On Fri, May 13, 2011 at 3:35 AM, Chris Murphy <lists at colorremedies.com>wrote:
> On May 12, 2011, at 6:21 PM, edmund ronald wrote:
> > Chris,
> > I say applications should have all options open at the behest of the
> user, including printing targets.
> I have no problem with an application developer having the option to
> include or not include it. You do not get to call it an option if it is in
> fact not a choice. A developer has a responsibility to their users, and I
> think it's sloppy and inconsiderate to compel all users to wade through a
> mass of largely irrelevant options used less frequently then a blue moon.
> I said at the behest of the USER. Hide it in a panel, but make it possible
> > You and Mike both say that "special" apps only should be able to print
> It is a suggestion consistent with only certain apps should be able to play
> poker. I do not believe card game functionality belongs in the print dialog
> either. There is no good reason why LibreOffice's print dialog needs to be
> cluttered with near total insanity of options that not one single person in
> their right mind would choose.
> Absolutely. And by this logic Apple has no more obligation to provide an
app for printing targets than to provide one for playing Solitaire.
> > Mike has made a very nice printing system that can just about print
> anything except a target.
> The problems on Mac OS X with respect to target printing predate CUPS, and
> predate Michael's involvement in architecture.
> I do think that the OS X 10.5 system worked very well, and so does 10.6.
AFAIK Cups was always used, and I think It's a nice solid piece of
software. Michael did a large part of CUPS. The only thing I dislike about
it, for some reason it has issues with targets :)
> > I say that if you really want to print targets you are welcome to write
> an app to print targets, as it's pretty clear that otherwise you won't get
> one :)
> No I'm saying the advocates and programmers of an opt-out color management
> system are obligated to provide both an app and API for opting out. Simple
> Apple did not do this. And I'm saying the open source Linux distros need to
> consider very carefully the ramifications of opt-in vs opt-out and the
> baggage they're going to inherit no mater if the opt out mechanism is
> application based, API based, or CPD based. All if it will have to be
> maintained to avoid problems.
They have provided a way to opt out. But they consider that it is too
confusing for this functionality is too confusing for normal developers who
do not understand color, just as you consider that the use of this
functionality is too confusing for normal users. So if you can get them to
accept that you are smart enough and know enough about color to be allowed
to disable CM, they will tell you. I tried, but I got nowhere, but then I
never made the claim of being smart or of understanding color. So there! I
have failed to get the info, so it's up to you to write that target printing
app for Gutenprint :)
> Chris Murphy
> openicc mailing list
> openicc at lists.freedesktop.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openicc