Hi,
a while ago I posted a list here with things that should be addressed
before we can start doing pre-releases for 2.2. Let's have a look at
what we achieved in the meantime.
Scale/Resize dialogs
We definitely need to redo these. The changes to the File-New
dialog and to the internal
On Friday 01 October 2004 10:46, Sven Neumann wrote:
Python bindings
IMO we should move pygimp out of the gimp tree into a
gimp-python package. That would make it easier to give it a
proper python-like build environment and would make it easier for
packagers. Yosh also had some great
Am 10.09.04, 00:41 +0100 schrieb Alastair M. Robinson:
...
A special case will be the TIFF plugin TIFFs can contain embedded
profiles for a CMYK colour space; ideally the TIFF plugin itself will
use lcms to convert the raw CMYK data to the RGB Working Space.
I had this code inside the tiff
Hi,
David Hodson [EMAIL PROTECTED] writes:
I think it's about time to start to discuss what features we still
want to get into GIMP 2.2.
Something that I'd like to see (if it hasn't been done yet) is
to make the popup progress dialog dockable. How feasible is that?
Well, we don't want
Sven,
Something that I'd like to see (if it hasn't been done yet) is
to make the popup progress dialog dockable. How feasible is that?
Well, we don't want to make it dockable, it should be embedded in the
associated dialog. Yes, that should definitely be on the list for 2.2.
What if there's no
Nathan Carl Summers wrote:
I can't honestly think of a good reason to disable color management, but
couldn't we just have an option for this monitor's colorspace instead of
having two choice to choose from?
The first time I tried to use PhotoShop with color management, I was
totally
On Mon, Aug 09, 2004 at 09:29:46AM -0700, William Skaggs wrote:
Nathan Carl Summers wrote:
I can't honestly think of a good reason to disable color management, but
couldn't we just have an option for this monitor's colorspace instead of
having two choice to choose from?
The first
I would argue that non interactive plugins (or interactive plugin run in non
interactive mode, which I presume to be the same thing), should not bring up any
progress bars.
-Joseph
Sven Neumann wrote:
Hi,
David Hodson [EMAIL PROTECTED] writes:
What if there's no associated dialog? I have some
Joseph Heled wrote:
I would argue that non interactive plugins (or interactive plugin
run in non interactive mode, which I presume to be the same thing),
should not bring up any progress bars.
You would argue incorrectly, then. Even if a plugin is noninteractive,
bad things usually happen
Hi,
Joseph Heled [EMAIL PROTECTED] writes:
I would argue that non interactive plugins (or interactive plugin run
in non interactive mode, which I presume to be the same thing), should
not bring up any progress bars.
No, that would be wrong. Non-interactive means that there's no user
Hi,
one or two things for GIMP 2.2 that I forgot:
Script-Fu vs. Tiny-Fu
We should come to a conclusion whether and how Tiny-Fu can replace
Script-Fu. I'd suggest we make separate packages gimp-script-fu and
gimp-tiny-fu and remove Script-Fu from the gimp tree.
Python bindings
IMO we
PROTECTED]
To: Sven Neumann [EMAIL PROTECTED]
Subject: Re: [Gimp-developer] preparing GIMP 2.2
Status on my pattern changes, in case you are wondering
This list doesn't include tasks that have already been started but
I have most of the patterns done. Now most of them also work off the
current
Hi,
Sven Neumann wrote:
No, that would be wrong. Non-interactive means that there's no user
interaction, it doesn't mean that there's absolutely no feedback such
as a progress bar. Some plug-ins used to behave the way you argue and
we have hopefully found and changed them all to do the right
Hi,
Sven Neumann wrote:
one or two things for GIMP 2.2 that I forgot:
Script-Fu vs. Tiny-Fu
We should come to a conclusion whether and how Tiny-Fu can replace
Script-Fu. I'd suggest we make separate packages gimp-script-fu and
gimp-tiny-fu and remove Script-Fu from the gimp tree.
Hi,
David Neary [EMAIL PROTECTED] writes:
How does gimp-console handle plug-ins then? I assume it doesn't
bring up progress curses windows...
The progress API is implemented as part of the GUI vtable of the Gimp
object (http://developer.gimp.org/api/2.0/app/app-Gimp-gui.html).
gimp-console
Sven Neumann wrote:
The progress bar should then be part of the plug-in dialog that calls
these functions.
OK, of course, should have seen that. Gotcha. (I'm sick today, so
my brain isn't working properly.)
--
David Hodson -- this night wounds time
___
Joseph Heled wrote:
I would argue that non interactive plugins (or interactive plugin run in
non interactive mode, which I presume to be the same thing), should not
bring up any progress bars.
In my case, I have a batch processing plugin that sets up a sequence
of operations interactively, then
Hi Everyone,
Sven Neumann wrote:
Color management
This has been discussed quite thoroughly but it still needs to be
written down in some sort of specification and then been cut down
into tasks.
Here's a first attempt at a suitable specification:
Colour management will bring two major
From: Sven Neumann [EMAIL PROTECTED]
Date: 09 Aug 2004 00:10:48 +0200
I think it's about time to start to discuss what features we still
want to get into GIMP 2.2. We are targetting a feature freeze by
the end of the month and a release shortly after, so it's probably
about
Sven Neumann wrote:
I think it's about time to start to discuss what features we still
want to get into GIMP 2.2.
Something that I'd like to see (if it hasn't been done yet) is
to make the popup progress dialog dockable. How feasible is that?
--
David Hodson -- this night wounds time
* Add a new section in the preferences dialog (or add to the existing
Display section) the following options:
* Enable/disable colour management (Do we allow this to be
enabled/disabled on a per-image basis? The filter will need access to
image parasites for that.)
I can't
21 matches
Mail list logo
