[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gimp-print-devel
Subject:    Re: [Gimp-print-devel] Identifying color options
From:       "Alastair M. Robinson" <blackfive () fakenhamweb ! co ! uk>
Date:       2010-09-02 7:56:40
Message-ID: 4C7F58B8.40400 () fakenhamweb ! co ! uk
[Download RAW message or body]

Hi :)

On 02/09/10 06:43, Kai-Uwe Behrmann wrote:

> Maybe the Gutenprints unprint command of a reference version can be
> applied in a test scenario to detect any changes. E.g. 5.0 is considerd
> a reference and all upcomming versions are compared to unprint-5.0 .
> Once it breaks eigther bump to Gutenprint 6.0 then thats reflected in
> the PPD. Or bump a *GutenprintColorAPI variable inside PPD?

The only problem with that is that once it changes, your reference has 
to change for future runs.  Since you don't want to bump every printer's 
colour version just because some other printer's response has changed, 
you'd then have to keep track of which level each printer's reached!

It might make more sense to store a value digested from current response 
- but it would have to be derived from a few rows printed at each 
resolution the printer supports, because for variable-drop-size inkjets 
it's entirely possible for the colour response to remain the same at one 
resolution but change at another.  That might end up being quite 
expensive to compute.

All the best
--
Alastair M. Robinson

------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Gimp-print-devel mailing list
Gimp-print-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel
[prev in list] [next in list] [prev in thread] [next in thread]