This is an enhancement request. Repeated calls to gimp_env_init should
yield warnings and not fatal errors. It has benefits for gimp plugins
written in Python.
Currently gimp_env_init() calls g_error (fatal) if called a second time.
Instead, pygimp_main(), which calls gimp_env_init(), should
On Sun, 2010-02-28 at 11:23 +0100, Sven Neumann wrote:
On Sat, 2010-02-27 at 14:35 -0500, lloyd konneker wrote:
This is an enhancement request. Repeated calls to gimp_env_init should
yield warnings and not fatal errors. It has benefits for gimp plugins
written in Python.
Currently
plugin to extend the path. Not difficult but annoying.
On Tue, 2010-03-02 at 08:49 +0100, Sven Neumann wrote:
On Sun, 2010-02-28 at 17:18 +, Omari Stephens wrote:
On 02/28/2010 02:43 PM, lloyd konneker wrote:
::snip? SNIP!::
Here is proposed addition for plug-ins/gimpmodule.c
On Tue, Mar 2, 2010 at 2:58 PM, Sven Neumann s...@gimp.org wrote:
On Tue, 2010-03-02 at 08:01 -0500, lloyd konneker wrote:
I wonder if importing a plug-in from another plug-in is really
something
that we want to support. If the goal is to share code, then perhaps
the
code that is worth
On Sat, 2010-03-06 at 08:41 +1030, David Gowers wrote:
On Tue, 2010-03-02 at 08:01 -0500, lloyd konneker wrote:
I agree with Joao S. O. Bueno and disagree with David Bowers.
Well, I'm glad you don't disagree with me, but who is that?
Sorry I mangled your name. BTW David Bowers
I uploaded a prototype of an Inspect plugin to the gimp registry.
Refer to a previous thread about gimp_env_init() and a proposed patch.
If I get encouragement and the proposed patch to GIMP-Python is
approved, I might continue development.
I think this plugin fits the Gimp practice of keeping
I have posted a Make shortcut plugin to the Gimp Registry. It lets a
user choose from a view of the menu tree of plugins, to create a new
plugin (a script) that is a shortcut to a target plugin.
It is very rudimentary, but could be extended into a visual editor of
sorts, to create named
On Mon, 2010-04-12 at 23:20 +0200, Avgoustinos Kadis wrote:
Thanks Sven, very important to know that!
How feasible are these options?
1. Randomly pick a value for each parameter. From what you said (that
it depends a lot on the parameters) this wont give us the best results
but at least we
useful and popular plugin packages.
Putting it in Gimp and getting the bugs fixed would help many users.
I would be glad to provide more details.
Lloyd Konneker
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https
and ought to
be one of the core plugins.
On Wed, 2010-05-19 at 23:49 +0200, Sven Neumann wrote:
On Wed, 2010-05-19 at 10:03 -0400, lloyd konneker wrote:
This is a request to put the Resynthesizer plugin in the Gimp project.
The author, Paul Harrison, has given me permission to maintain
a script (on invalid
argument for the display.)
A patch is attached. It includes changes in display.pdb to
gimp_display_new() and gimp_display_delete().
From 218285d3cb532e01177616b3434654bd20e2ae14 Mon Sep 17 00:00:00 2001
From: Lloyd Konneker boo...@nc.rr.com
Date: Mon, 20 Sep 2010 19:59:46
Announcing a new version of the Make Shortcut plugin, now called
GimpScripter. It lets you point-and-click create a plugin that calls a
sequence of plugins, PDB procedures, or macros. It is a plugin authoring
tool.
Gimpscripter is a Gimp plugin written in Python. It generates Python
code for a
options to remove/insert actions into existed
scripts. Maybe you can reference Michael Terry's recent work on
Adaptable GIMP.
http://adaptablegimp.org/index.php/How_to_Create_a_Task_Set
Thanks for sharing.
Regards,
Tim Chen
http://ht-timchen.org
On Mon, May 9, 2011 at 9:23 PM, lloyd
13 matches
Mail list logo