Gimp-Print 4.3.17, released June 20, 2003, is a development release of
this package. Like all development releases, this version is
considered unstable and should only be used by those individuals
tolerant of the likelihood of problems. Individuals desiring a stable
release of Gimp-Print should u
while i was waiting to receive my password from mailman so i can leave
this ship of fools, i cvs checkedout gimp-gap from gnomecvs.
apparently, wofgang uses 1.4 and that is good enough for me.
can someone email me with how to tell my autoconf.sh where GIMP-1.4 is?
i will not have time to check th
On Friday 20 June 2003 07:10, Marco Wessel wrote:
> On 20 Jun 2003, Daniel Egger wrote:
> > Am Don, 2003-06-19 um 21.44 schrieb David Neary:
> > > I'll get the ball rolling: 2.0
I wil stay with 1.4
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http
On Fri, 20 Jun 2003 16:50:37 +0200, Sven Neumann <[EMAIL PROTECTED]> wrote:
> Hans Breuer <[EMAIL PROTECTED]> writes:
> > This is the all-or-nothing argument. IMO a macro recorder
> > would already be useful if it only records the calls done
> > as reaction on users menu usage, where many go throug
Last Februrary, I volunteered to help with the GIMP MMX implemetation
that had been languishing and had recently started to cause problems
when building the current GIMP code.
This (http://oak.mysterious.org/~helvetix/practicum/gimp-composite.tgz) is
release 0.0 of an extensible and customisable
This is the best idea so far.
Helvetix
On Fri, Jun 20, 2003 at 01:47:14AM -0700, Joel Eduardo Rodriguez Ramirez wrote:
>
> dont whant to bother,..but how about an totally alphabetic release,..like
> picasso, vinci il mondo, maya art, gliphic insight?,,,ha,..galactic green,..
> ...the number?
>
Hi,
Hans Breuer <[EMAIL PROTECTED]> writes:
> This is the all-or-nothing argument. IMO a macro recorder
> would already be useful if it only records the calls done
> as reaction on users menu usage, where many go through the
> PDB. Without looking further I thought there are already
> core functi
At 15:05 20.06.03 +0200, Sven Neumann wrote:
>Hi,
>
>Hans Breuer <[EMAIL PROTECTED]> writes:
>
>> Sent to gtk-devel w/o response
>
>Did you file a bug-report? This is unlikely ever to be fixed without a
>bug-report.
>
>> Current Gimp cvs (compiled on win32) triggers
>> the one in g_scanner_get_ch
At 15:20 20.06.03 +0200, Sven Neumann wrote:
>Hi,
>
>Hans Breuer <[EMAIL PROTECTED]> writes:
>
>> - Intercept every PDB call if a macro recorder instance is running.
>> (try to guess the call stack depth to avoid recording functions
>>called by a plug-in)
>
>That would mean that all actions
On Thu, 19 Jun 2003 16:46:13 -0700 (PDT)
Joel Eduardo Rodriguez Ramirez <[EMAIL PROTECTED]> wrote:
> Actually I would like to colaborate with a new filter also
> (as Bowie), but mine idea is in the direction of:
> ``Inverse Image Filtering with Conjugate Gradient''
>
> http://people.cornell.edu/p
Hi,
Hans Breuer <[EMAIL PROTECTED]> writes:
> - Intercept every PDB call if a macro recorder instance is running.
> (try to guess the call stack depth to avoid recording functions
>called by a plug-in)
That would mean that all actions go through the PDB. The fact is that
no user action go
Hi,
Hans Breuer <[EMAIL PROTECTED]> writes:
> Sent to gtk-devel w/o response
Did you file a bug-report? This is unlikely ever to be fixed without a
bug-report.
> Current Gimp cvs (compiled on win32) triggers
> the one in g_scanner_get_char() and as a result looses
> it's reference to the inpu
As described in
http://bugzilla.gnome.org/show_bug.cgi?id=51937
I once had a partly working prototype (patch against
Gimp 1.2.x) for macro recording.
I'm about to give it another try with current cvs code
base, but before I would like to get some information
to avoid (if possible) fast rotting
[
Sent to gtk-devel w/o response :
The patch below fixes it on the Gimp level, ok to apply ?
]
In glib/gscanner.c there are various places where
scanner->input_fd is set to -1
Current Gimp cvs (compiled on win32) triggers
the one in g_scanner_get_char() and as a result looses
it's reference to
there are no clear instructions on the information page about this list
to unsubscribe. can someone unsubscribe me. i have wasted too much
time on this project as it is.
carol
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkele
On Thu, 19 Jun 2003 21:44:01 +0200, David Neary <[EMAIL PROTECTED]> wrote:
> I'll get the ball rolling: 2.0
>
FWIW, 1.4.
Yes, I know that I supported 2.0 three days ago, but I have changed my
mind since then.
In any case, I don't think that making the poll on the developers' list
is useful. If
On 20 Jun 2003, Daniel Egger wrote:
> Am Don, 2003-06-19 um 21.44 schrieb David Neary:
>
> > I'll get the ball rolling: 2.0
>
> 1.4
>
Damnit, call it GIMP XP already.
Marco
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.
Am Don, 2003-06-19 um 21.44 schrieb David Neary:
> I'll get the ball rolling: 2.0
1.4
--
Servus,
Daniel
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Hi,
Le jeu 19/06/2003 à 10:55, Sven Neumann a écrit :
> You can get 160 hits on google for whatever statement you would like
> to make. It is a stupid attempt to try to prove anything with a search
> engine that has billions of pages archived.
I also agree that coming up with a google search is
Hi,
Nathan Carl Summers <[EMAIL PROTECTED]> writes:
> Otherwise, the Slashdot headline we will get is "GIMP 2.0 Fails to
> Deliver Promised Features"
Do you really expect this to happen? Well, of course there will be the
inevitable casual trolls, but apart from that, do you really expect
bad pre
dont whant to bother,..but how about an totally alphabetic release,..like
picasso, vinci il mondo, maya art, gliphic insight?,,,ha,..galactic green,..
...the number?
regards
Joel
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkele
21 matches
Mail list logo
