[Gimp-developer] gimp-2.3.12 / win32 / python

2006-10-31 Thread lode leroy
I'm having problems with the python support in gimp-2.3.12... I installed the following packages: gtk+-2.10.6-setup.zip python-2.4.4.msi pycairo-1.0.2-1.win32-py2.4.exe pygtk-2.8.6-1.win32-py2.4.exe gimp-2.3.12-i586-setup.zip When I run the script Xtns-Python-Fu-Test-Sphere, it works perfectly

[Gimp-developer] python scripts not working (2.3.8/linux)

2006-04-27 Thread lode leroy
when trying the pygimp-sphere.py, I get an error message PDB calling error for procedure 'gimp-context-set-foreground': Argument 'foreground' (#1, type GimpRGB) out of bounds (validation changed 'not transformable to string' I tracked this down to this: gimpmodule.c:

[Gimp-developer] help needed with Python plugin

2006-03-27 Thread lode leroy
on region using Otsu's method (adapted from code in GOCR-0.14), Lode Leroy, Lode Leroy, 2006, Image/Filters/Misc/_Threshold..., *, [], [], python_otsu_threshold) main() ___ Gimp-developer mailing

[Gimp-developer] Re: P.S. / GLIB Problems

2005-12-12 Thread lode leroy
The guys over at inkscape have a all-in-one download for building on windows... This probably contains everything for building gimp too... (haven't tried yet) http://inkscape.org/win32/gtk28-051122.7z ___ Gimp-developer mailing list

Re: [Gimp-developer] GIMP 2.3.4

2005-10-05 Thread lode leroy
When installing Python from Python-2.4.1.msi, the headers are not in C:/Python24/include/python24 but in C:/Python24/include. This fixes that problem. --- pythondev.m4.orig 2005-10-05 17:29:40.015625000 -0700 +++ pythondev.m42005-10-05 17:27:01.609375000 -0700 @@ -10,9 +10,9 @@

Re: [Gimp-developer] GIMP 2.3.4

2005-10-04 Thread lode leroy
From: Tor Lillqvist [EMAIL PROTECTED] To: lode leroy [EMAIL PROTECTED] CC: gimp-developer@lists.xcf.berkeley.edu Subject: Re: [Gimp-developer] GIMP 2.3.4 Date: Tue, 4 Oct 2005 01:48:10 +0300 lode leroy writes: In fact, what happens is that when linking with ZLIB.DLL, the exe expects ZLIB-1

Re: [Gimp-developer] PBM

2005-09-09 Thread lode leroy
PROTECTED] To: lode leroy [EMAIL PROTECTED] Subject: Re: [Gimp-developer] PBM Date: Wed, 7 Sep 2005 16:27:45 -0400 On 9/7/05, lode leroy [EMAIL PROTECTED] wrote: Would it be possible to support the .pbm as extension in Save As in GIMP? It should be possible. The question is whether or not someone

[Gimp-developer] PBM

2005-09-07 Thread lode leroy
Would it be possible to support the .pbm as extension in Save As in GIMP? -- lode ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer

[Gimp-developer] problem creating simple plugin

2005-07-27 Thread lode leroy
Hello, I have a problem creating a cery simple gimp plugin.. The idea is to select a part of an image, and the plugin should create a new image with the size of the selection, and put (processed) pixels in that new image (a bit like Copy Past As New). The plugin compiles, runs without

Re: [Gimp-developer] gimp-cvs on msys/mingw

2005-06-29 Thread lode leroy
From: Manish Singh [EMAIL PROTECTED] Reply-To: Manish Singh [EMAIL PROTECTED] To: michael chang [EMAIL PROTECTED] CC: lode leroy [EMAIL PROTECTED],gimp-developer@lists.xcf.berkeley.edu Subject: Re: [Gimp-developer] gimp-cvs on msys/mingw Date: Tue, 28 Jun 2005 09:45:38 -0700 On Tue, Jun 28

Re: [Gimp-developer] gimp-cvs on msys/mingw

2005-06-29 Thread lode leroy
From: Manish Singh [EMAIL PROTECTED] On Tue, Jun 28, 2005 at 11:31:48AM +0200, lode leroy wrote: ... Your libwmf library is too old. Upgrade. will do. I just took the stuff from tml's gimp-for-windows page the autodetection of python on MSYS is not too good: the \es need to be replaced

Re: [Gimp-developer] gimp-cvs on msys/mingw

2005-06-29 Thread lode leroy
From: Manish Singh [EMAIL PROTECTED] Yes, and the configure script should take care of this. This is why I asked for confirmation that you have all the stuff needed for this to work (which you did not answer). I did run cvs update, and it did compile. ... Except the stuff you changed isn't

[Gimp-developer] gimp-cvs on msys/mingw

2005-06-28 Thread lode leroy
some hints and remarks for building gimp-2.3.1+ from cvs ftruncate is not present in my version of mingw, so I changed it to make it compile. diff -u -r1.5 gimpwin32-io.h --- libgimpbase/gimpwin32-io.h 19 Feb 2005 00:50:35 - 1.5 +++ libgimpbase/gimpwin32-io.h 28 Jun 2005 09:19:09

[Gimp-developer] pygimp on windows? success!

2005-06-24 Thread lode leroy
Python's module mechanism doesn't recognize the dll files as a python module. Once you solve this (e.g. add or remove the compiler or linker flag that makes it work or break resp.), it should work. well, the first problem just now is that there is no .dll resulting from the autotools

[Gimp-developer] pygimp on windows?

2005-06-23 Thread lode leroy
Hi folks, I'm trying to get pygimp to work on gimp-2.3.1 for windows/autotools. For some reason, the pygimp plugin seems not to be initialized. Could someone sketch the mechanism by which pygimp is supposed to be loaded? It looks like the pygimp.interp file is actually read and used: it

[Gimp-developer] pygimp on windows?

2005-06-23 Thread lode leroy
Could someone sketch the mechanism by which pygimp is supposed to be loaded? It is a python module (actually two of them), but even if you make sure that python should find them (either by a .pth file in python's Lib/site-packages directory or by copying it there, it doesn't work. I meant

[Gimp-developer] pygimp on windows? (Duh!)

2005-06-23 Thread lode leroy
ok, I found the missing link ! from http://hans.breuer.org/ports/readme.win32 set PATHEXT=%PATHEXT%;.py ok. so now the .py plugins are getting loaded, but I get Traceback (most recent call last): File C:\msys\1.0\target\lib\gimp\2.0\plug-ins\shadow_bevel.py, line 20, in ? from gimpfu

[Gimp-developer] autogen.sh on msys

2004-11-25 Thread lode . leroy
IIRC, autogen checks for versionned automakes and aclocals to see if newer versions are installed in parallel to the non-versionned ones. I think it misses the latest (1.8 and 1.9, and just checks for 1.7 or 1.6) I modified my autogen.sh to test for newer versions of automake: echo -n checking