Hi,
On Sat, 2008-09-27 at 22:41 +0200, Samuel wrote:
Where can I find the actual Python docs for GIMP? I know this site:
http://www.gimp.org/docs/python/index.html
These docs are very outdated. But unfortunately there is no newer
documentation available at this point. I suggest that you have a
Hi,
On Sun, 2008-09-28 at 17:15 -0700, Greg MacDonald wrote:
I've been fiddling around with writing gimp-python plugins and ended
up creating a template for myself. It took me a day to put together so
I was thinking I might post it.
This is interesting. Is there a particular reason that your
Hi Sven,
No reason really. But now that you bring it up, I wonder if gimpfu
might be more useful to people. If I had needed to setup a gui, I
probably would've stuck with gimpfu for it's auto gui generation
features. I think I may have gone with gimpplugin too because it just
felt familiar to me;
I have been at the GIMP IRC channel and they told me that C is faster than
Python if I want many pixel ops. I wrote a test plugin in Python which copies a
layer pixel per pixel to another one and it needs several minutes for a vga
picture.
I put it here:
http://pastebin.com/m1e61c74a
Regards
Hi,
On Mon, 2008-09-29 at 12:10 +0200, Samuel wrote:
I have been at the GIMP IRC channel and they told me that C is faster
than Python if I want many pixel ops. I wrote a test plugin in Python
which copies a layer pixel per pixel to another one and it needs
several minutes for a vga picture.
Hi,
I would very much welcome if you could change the call to
gimp.install_procedure() to not pass the full menu path. The procedure
is supposed to be passed the menu label only. There's a seperate
procedure to register the menu entry: gimp.menu_register().
Sven
Hi Samuel,
On Mon, Sep 29, 2008 at 7:40 PM, Samuel [EMAIL PROTECTED] wrote:
I have been at the GIMP IRC channel and they told me that C is faster than
Python if I want many pixel ops. I wrote a test plugin in Python which copies
a layer pixel per pixel to another one and it needs several
I made a speed test with Python and found out that it's
too slow for pixel ops. I change to C now.
Furthermore the docs for a C plugin are much better than
these for Python.
Hi Sam,
Thanks for your response.
Sven seems to know alot about it, he thinks python speed is good.
That would be
Maybe when you save the selection at the beginning of the plugin with
selection = drawable.image.selection #The selection mask for the image.
bounds = drawable.mask_bounds #The bounds of the drawable's selection.
#or like in feca_hdr: http://registry.gimp.org/node/4752
Hello all:
I submitted what is probably the last yafr patch for a while. (Unless
I figure out how to use Geert's patch to do more careful boundary
conditions and compute pixel values past the abyss boundary, which is
documented through a #define in the code.)
I really believe that this is
Apologies:
The yafr email was meant for the gegl-developer list.
Nicolas Robidoux
Laurentian University/Universite Laurentienne
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
11 matches
Mail list logo
