Dear GIMP Contributors,
I seek help from designers, developers, testers,defect fixers,project
managers or playing any other key role in Free/Open Source software
development or maintenence
in carrying out a study on practices and problems of defect management in
various Free/Open Source
I am hereforth asking you to apologise, if possible, both in private
and on the list for this message. We are runing a project needing
I cannot sincerely do so, in this instance. I do not apologize for
expressing my amusement, unless I judge that the situation was genuinely
worsened by my
On Mon, 12 Mar 2007 00:54:56 +0100, D. Stimits [EMAIL PROTECTED] wrote:
Speculating about why it claimed it was out of memory, I'm wondering if
the hard drive simply was too slow responding. It's a laptop, running
with core duo, entirely in ram. The drive is thus much slower than the
ability
Von: David Gowers [EMAIL PROTECTED]
I am hereforth asking you to apologise, if possible, both in private
and on the list for this message. We are runing a project needing
I cannot sincerely do so, in this instance. I do not apologize for
expressing my amusement, unless I judge that the
guys + gals,
thanks to Sven, the GIMP UI redesign team has now a wiki
where everybody can follow our progress:
http://gui.gimp.org
Right now we are filling it with our raw evaluation notes.
Some of the latest added stuff is so raw that you can track
us clarifying it a couple of days afterwards.
Pals,
I realized that gimp 2.3.15 (and some versions before) comes with
zoom for previews. A very useful feature for what I want to develop
(a noise reduction plugin).
I added a line 'gimp_zoom_preview_new (drawable);' that I got from
I think you have hit an actual bug, and that it doesn't have anything
to do with python, because I have encountered a similar thing in a
modified version of gimpressionist that I worked up, written purely
in C. I believe that there is some sort of memory leak that causes
gimp in some situations
On Mon, 12 Mar 2007 15:22:49 +0100, Luis A. Florit
[EMAIL PROTECTED] wrote:
(gimp-2.3:21083): Gimp-Plug-In-WARNING **: gimp-2.3:
plug_in_flush(): error: Broken pipe
This is nothing to do with the zoom preview mate, you've got a blocked
toilet !! I should call out a plumber , this
Hi,
On Mon, 2007-03-12 at 11:22 -0300, Luis A. Florit wrote:
I added a line 'gimp_zoom_preview_new (drawable);' that I got from
http://developer.gimp.org/api/2.0/libgimp/GimpZoomPreview.html
The plugin complies just fine, but when trying to run it in
gimp 2.3.15 the plugin crashes with a
On Mon, 12 Mar 2007 15:22:49 +0100, Luis A. Florit
[EMAIL PROTECTED] wrote:
(gimp-2.3:21083): Gimp-Plug-In-WARNING **: gimp-2.3:
plug_in_flush(): error: Broken pipe
This is nothing to do with the zoom preview mate, you've got a
blocked toilet!! I should call out a plumber, this
Hi,
On Fri, 2007-02-02 at 03:56 -0800, Saul Goode wrote:
I have a rough draft of some of the differences between SIOD-fu. It is
not yet comprehensive but perhaps it might be useful as a starting point.
I've been on this mailing list for two days and this is the second
time I've seen someone arrogantly laughing at someone's very
reasonable questions.
Chris Seaton
On 12 Mar 2007, at 17:16, [EMAIL PROTECTED] wrote:
On Mon, 12 Mar 2007 15:22:49 +0100, Luis A. Florit
[EMAIL PROTECTED] wrote:
Hi,
On Mon, 2007-03-12 at 11:22 -0300, Luis A. Florit wrote:
I added a line 'gimp_zoom_preview_new (drawable);' that I got from
http://developer.gimp.org/api/2.0/libgimp/GimpZoomPreview.html
The plugin complies just fine, but when trying to run it in
gimp 2.3.15 the plugin crashes
Hi,
On Mon, 2007-03-12 at 19:11 -0300, Luis A. Florit wrote:
I compiled gimp with './configure --prefix=/opt/gimp'
for it not to touch my stable gimp 2.2 RPM install.
I am compiling the plug-in with
/opt/gimp/bin/gimptool-2.0 --install plugin
You will probably have to set
Chris Seaton wrote:
I've been on this mailing list for two days and this is the second
time I've seen someone arrogantly laughing at someone's very
reasonable questions.
Took me some time to get the joke, but it is one, IMO:
On 12 Mar 2007, at 17:16, [EMAIL PROTECTED] wrote:
On Mon,
Hi,
On Mon, 2007-03-12 at 23:13 +0100, Sven Neumann wrote:
You will probably have to set PKG_CONFIG_PATH to get this right.
Thinking about it, perhaps gimptool-2.0 should do this for you. We could
add something like
PKG_CONFIG_PATH=$libdir/pkgconfig:$PKG_CONFIG_PATH
to gimptool-2.0.in.
Hi Sven,
On Mon, 2007-03-12 at 19:11 -0300, Luis A. Florit wrote:
I compiled gimp with './configure --prefix=/opt/gimp'
for it not to touch my stable gimp 2.2 RPM install.
I am compiling the plug-in with
/opt/gimp/bin/gimptool-2.0 --install plugin
You will probably have to set
On Mon, 12 Mar 2007 19:36:42 -0300, Luis A. Florit
[EMAIL PROTECTED] said:
I am doing something wrong... I tried with this command:
Yes, yes you are.
export PKG_CONFIG_PATH=/opt/gimp/lib/pkgconfig ; /opt/gimp/bin/gimp-2.3
and I still having the same error.
PKG_CONFIG_PATH only affects
gg,
I didn't get your joke at a first sight.
English is not my language...
BTW, it was funny. :)
L.
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Hi Ori,
* El 12/03/07 a las 19:55, Ori Bernstein chamullaba:
On Mon, 12 Mar 2007 19:36:42 -0300, Luis A. Florit
[EMAIL PROTECTED] said:
I am doing something wrong... I tried with this command:
Yes, yes you are.
export PKG_CONFIG_PATH=/opt/gimp/lib/pkgconfig ; /opt/gimp/bin/gimp-2.3
20 matches
Mail list logo
