Re: [Gimp-developer] couple possible TODO items

2001-03-30 Thread Kevin Cozens

At 11:43 PM 03/28/2001 +0200, you wrote:
On 27 Mar, Zachary Beane wrote:
  Are credit cards of a standard size?

  Should be. I wouldn't trust sticking them into a machine otherwise.

Using a credit card as a standard object for calibration is not a good 
idea. Students in high school (for e.g.) that want to use the GIMP are very 
unlikely to have credit cards.


Cheers!

Kevin.  (http://www.interlog.com/~kcozens/)

E-mail:kcozens at interlog dot com|"What are we going to do today, Borg?"
 or:ve3syb at rac dot ca   |"Same thing we always do, Pinkutus:
Packet:ve3syb@ve3yra.#con.on.ca.na|  Try to assimilate the world!"
#include disclaimer/favourite   |  -Pinkutus  the Borg

___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer



Re: [Gimp-developer] couple possible TODO items

2001-03-29 Thread Tino Schwarze

Hi,

On Wed, Mar 28, 2001 at 01:12:28PM +0200, Sven Neumann wrote:
   - Biased color reduction
   
 This is a feature I saw in photoshop. When reducing the colors of an
 image, it will try to preserve colors within the active selection
 more than it tries to preserve those outside of it. For example, if
 you want to keep skin tones in an image, but want to otherwise
 reduce the overall number of colors, you would select a few
 representative areas of skin before doing the reduction.
 
  Personally, I can't count the number of times I've converted an image
  to Indexed only to find the black had gone suddenly slightly
  off-black, or another solid color that I really needed at a particular
  value had suddenly shifted slightly. I'd love to be able to select
  those colors before conversion to hint to the Indexed conversion,
  "these exact values are important to me."
 
 Talked to Adam about that issue on #gimp lately and he seems to be
 biased towards changing the conversion-algorithm to be intelligent
 enough to do the right thing without user interaction. 

I doubt that this is possible. An algorithm simply cannot guess that
those three black pixels are more important to me than those two
thousand gray ones.

We need to be able to flag some colors sticky - e.g. for logo /
Corporate Identity work where colors are fixed and must not be changed.
It would have another advantage, especially for web work: I could fix
the important colors and reduce further (to reduce file size) while this
might not be possible if the algorithm chooses all colors itself.

Though, I don't have an idea of how the GUI allowing sticky colors could
look like. :-(

Just my two (Euro)cents, Tino.

-- 
 * LINUX - Where do you want to be tomorrow? *
  http://www.tu-chemnitz.de/linux/tag/
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer