On Thu, Aug 24, 2000 at 06:15:16PM -0700, Mathew Yeates wrote:
>
> Can somebody tell me the steps I need to take in order
> to get the latest Hollywood (deep image support) version?
>
> TIA
>
> Mathew
Though not for the faint of heart, you have two ways to
get it...
1) Get it from film.gimp.
Date: Fri, 25 Aug 2000 01:08:42 +0200
From: Sven Neumann <[EMAIL PROTECTED]>
There were no API changes at all. All of the names that are standard
now have been around for a long time and the only thing we did was to
reverse the logic of the COMPAT_CRUFT defines. What was
Can somebody tell me the steps I need to take in order
to get the latest Hollywood (deep image support) version?
TIA
Mathew
>
>Anyway, it seems nobody has the time and energy to really work on the
>needed changes in script-fu to make it a viable programming environment.
>
> > More generally is it possible for script-fu scripts to introduce memory
> > leaks even tough scheme in itself is a garbage collected language?
>
Hi,
> Secondly, I'm confused by the function gimp-file-save. Specifically why do
> I need to pass an image and a drawable? If I load an image, do some image
> level manipulations on it, and then want to save it with gimp-image-save,
> do I need to create a layer?
most save plug-ins can not
On Fri, 25 Aug 2000, Marc Lehmann wrote:
> > More generally is it possible for script-fu scripts to introduce memory
> > leaks even tough scheme in itself is a garbage collected language?
>
I think that if a script terminates unexpectedly it leaks all GIMP
resources that it created. If the res
On Thu, Aug 24, 2000 at 03:06:10PM -0700, christopher baus wrote:
> Secondly, I'm confused by the function gimp-file-save. Specifically why do
> I need to pass an image and a drawable? If I load an image, do some image
> level manipulations on it, and then want to save it with gimp-image-save,
On Thu, Aug 24, 2000 at 03:06:10PM -0700, christopher baus <[EMAIL PROTECTED]>
wrote:
> something like perl, but that's IMHO. I know a lot of people aren't down
> with functional programming languages.
(... like perl ;)
Anyway, it seems nobody has the time and energy to really work on the
nee
Hi,
> While, in theory, I agree that having compatibility cruft inside a
> software package is bad, I think breaking compatibility deep within a
> feature freeze was a very bad idea.
>
> I thought different this afternoon when I could just enable
> GIMP_COMPAT_CRUFT_STH, but it just turned out t
I recently became a gimp user and have the following suggestion for
an addition to the gimp man page that would have saved me some time.
I have Version 1.0.4 of gimp.
The ENVIRONMENT VARIABLES section needs to include GIMP_DATADIR and
GIMP_DIRECTORY. I learned by reading source code that I need
Good Day,
While I've messed around with the gimp for a few years, now that I have a
digital camera, I'm getting started with gimp programming. FYI, I'm a
seasoned programmer, so I won't post any general programming questions...
First off I think the gimp's architecture is totally cool, as it
While, in theory, I agree that having compatibility cruft inside a
software package is bad, I think breaking compatibility deep within a
feature freeze was a very bad idea.
I thought different this afternoon when I could just enable
GIMP_COMPAT_CRUFT_STH, but it just turned out that this define o
Hi,
> Are you not cleaning up CAN_HANDLE_INDEXED and friends?
you are right, we should have done this earlier. I've done it now.
Salut, Sven
Date: Thu, 24 Aug 2000 12:14:20 +0200
From: Sven Neumann <[EMAIL PROTECTED]>
in a final move to finish the 1.2 libgimp API we have changed the
logic of the COMPAT_CRUFT definitions in libgimp. The compatibility
definitions from gimpcompat.h and gimpenums.h are no longer included
Thanks!
--
Robert Krawitz <[EMAIL PROTECTED]> http://www.tiac.net/users/rlk/
Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail [EMAIL PROTECTED]
Project lead for The Gimp Print -- http://gimp-print.sourceforge.net
"
Hi,
in a final move to finish the 1.2 libgimp API we have changed the
logic of the COMPAT_CRUFT definitions in libgimp. The compatibility
definitions from gimpcompat.h and gimpenums.h are no longer included
by default. Old plug-ins that use the 1.0 API will therefore not
compile against the 1.2
16 matches
Mail list logo
