Hi,
Juhana Sadeharju [EMAIL PROTECTED] writes:
I'm still using GIMP 1.2.3 but those problems could still be present
in GIMP 2.0 -- please verify yourself, I cannot do it.
If you are still using GIMP 1.2.3 then we don't want to hear from you
on the gimp-developer list. Update to 2.0 (at least)
Hi,
just wanted to let you know that I have a working pygimp on my win32
system. To get there, I used:
ActivePython 2.3 from http://www.activestate.net/Products/ActivePython/
PyGTK 2.2.0 from http://www.mapr.ucl.ac.be/~gustin/win32_ports/pygtk.html
In order to get the gimp python module working
Juhana Sadeharju [EMAIL PROTECTED] writes:
From: Sven Neumann [EMAIL PROTECTED]
If you are still using GIMP 1.2.3 then we don't want to hear from you
on the gimp-developer list. Update to 2.0 (at least) or keep quiet.
Hey, I just wanted to point out what usability problems we users have.
As
I just built 2.1.0 with --enable-python but there was no python on the menus.
So I went and built 2.0.1 --enable-python and configure failed because I didn't have
pygtk
Installed that and rebuilt both. Python now shows in the menus.
Perhaps the configure for 2.1.0 doesn't fail on missing
Carol Spears wrote:
mr. neary, can you define unpleasant?
I have been on this list only a very short time, yet I can define
unpleasant...
Unpleasant (noun) See Carol Spears
I hate to start a personal attack on a public list, especially against
one who has apparently been involved with the
