Hi,
Tor Lillqvist [EMAIL PROTECTED] writes:
I don't know what the solution is. Maybe some way to (temporarily)
associate an invokation of the colour selector with a specific image?
An entry in the Image menu Select colour in image's colour space?
The color selector is opened from the toolbox
Hi,
Tor Lillqvist [EMAIL PROTECTED] writes:
Assume GIMP uses Sven's original idea (i.e. Alastair's preferred
method) where images keep their original colour space. Say a user is
working on an image in some colour space with a much larger gamut than
sRGB. If the colour selector allows only
Hi,
Quoting Sven Neumann [EMAIL PROTECTED]:
All we are discussing here is
whether it makes sense to use display filters to color-correct the
image display (and optionally color selector displays).
I don't think there is any argument about that. It does make sense to apply the
monitor's
Hi,
Dave Neary [EMAIL PROTECTED] writes:
point that we are discussing is how file plug-ins should handle
embedded color profiles, i.e. whether to attach the profile to the
image or not.
I may be listening to a different conversation. The other point was
whether embedded profiles should
Hi Carol,
On Tue, Jul 06, 2004 at 08:47:14AM -0700, Carol Spears wrote:
the bug report suggests this rearrangement of the Xtns menu (which is a
huge mess if you install all of the difference scripting options that
the linux gimp has):
The New Structure Toolbox/Xtns/:
Module Manager
By using vectors I was able to very quickly update the portion of those
scripts which used SIOD array functions. I have not changed the Tiny-Fu
marshalling code yet but I will do that soon and release a new tarball.
Now since there is essentially a one-to-one correspondence between Tiny-Fu's
Hi David,
David Neary wrote:
I'll conduct some tests some time and try and figure out just how bad
these quantisation errors could be.
Great - quantitative data will really help.
I've done some testing - I wrote a little program that puts every
possible 8-bit RGB colour through an lcms
Hi Sven,
Sven Neumann wrote:
Well, it got to be doable in the file plug-ins since we don't want to
have the core depend on lcms. Applying the embedded profile at load
time could very well happen in the file plug-ins though. If the core
needs to perform colorspace transformations then we should
Hi Alastair,
Alastair M. Robinson wrote:
Given the limitations we're trying to work within, I think the best
compromise is likely to be something like this:
snip some very good suggestions
- Change the GIMP's working profile to match this image. This will
leave the image data
Hi,
David Neary [EMAIL PROTECTED] writes:
So say I open an image with a color profile, and then load a
second image with a different profile. If I now decide to do the
above, what do we do to the first image?
1) We stop using the profile for the first image (and if the
image window is
Hi,
Sven Neumann wrote:
David Neary [EMAIL PROTECTED] writes:
1) We stop using the profile for the first image (and if the
image window is open, this will obviously change the visual
representation of the image), but keep it attached to the image
so that we can re-save it with the image
Hi Dave,
David Neary wrote:
So say I open an image with a color profile, and then load a
second image with a different profile. If I now decide to do the
above, what do we do to the first image?
1) We stop using the profile for the first image (and if the
image window is open, this will obviously
It really isn't all that complicated. Here is all you need to do
(this is basically what Sven outlined with a couple of extra details.)
1) Gimp uses the same color space internally for all images. This
could be either sRGB or a user-selected one (in which case it is
specified by a
hello Roman,
On Fri, Jul 09, 2004 at 02:03:26PM +0200, Roman Joost wrote:
On Tue, Jul 06, 2004 at 08:47:14AM -0700, Carol Spears wrote:
the bug report suggests this rearrangement of the Xtns menu (which is a
huge mess if you install all of the difference scripting options that
the linux
Hi,
Carol Spears [EMAIL PROTECTED] writes:
so the link to the documentation should go directly to whatever
scripting documentation came with the gimp.
Is there any? And how would gimp know where it is installed?
bookmarks go to online sources of information.
For reasons I outlined already,
At 01:38 PM 07/09/2004, you wrote:
Now since there is essentially a one-to-one correspondence between Tiny-Fu's
vectors and Script-Fu's arrays, it might be worth considering adding
compatibility definitions to init.scm (similar to gimpcompat.h for
plug-ins), that would, depending on a certain
16 matches
Mail list logo
