BONJOUR , et MERCI le problème pour moi est L'ANGLAIS .Gerard leseniorprovencal .

2012/4/4

Send gimp-developer-list mailing list submissions to gimp-developer-list@gnome.org

To subscribe or unsubscribe via the World Wide Web, visit http://mail.gnome.org/mailman/listinfo/gimp-developer-list or, via email, send a message with subject or body 'help' to gimp-developer-list-request@gnome.org

You can reach the person managing the list at gimp-developer-list-owner@gnome.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of gimp-developer-list digest..."

Today's Topics:

1. Re: Get currently active image in python (Jon Decker) 2. Plugin registration question (Jon Decker) 3. Python plugin debugging and workflow (Jon Decker) 4. Re: bug with Overlay (Paul Geraskin) 5. Re: Python plugin debugging and workflow (Joao S. O. Bueno) 6. Re: Python plugin debugging and workflow (Ragnar Brynj?lfsson)

----------------------------------------------------------------------

Message: 1 Date: Tue, 3 Apr 2012 05:50:23 -0400 From: Jon Decker
To: "Joao S. O. Bueno"
Cc: gimp-developer
Subject: Re: [Gimp-developer] Get currently active image in python Message-ID:

Content-Type: text/plain; charset="iso-8859-1"

Ok thanks for the information. I think I'll file a feature request as well - I think this would be a great addition to the API

On Mon, Apr 2, 2012 at 10:06 AM, Joao S. O. Bueno

wrote:

On 23 March 2012 15:06, Chris Mohler wrote:

On Fri, Mar 23, 2012 at 12:51 PM, Jon Decker

wrote:

Thanks for the reply. I do realize that the current image and

drawable

is

passed to the plugin when first opened. Perhaps I should explain

further.

I'm trying to build more of an extension that is opened just once, and updates as you move from image to image. (Its a time tracking window

which

stays open along side gimp). I wanted to make it so that a new

instance of

the plugin doesn't have to run for each image - just open it once, and

it

"knows" which image is currently active so that it can populate my

sqlite

database.

Is there a way to do this at in in gimp?

No, there is not - at least no clean ways that I can think of. There is nothing on the GIMP's API that marks an image as the currently active image.(The "unclean way" I can think of would mean to use GTK+ instrumentation for GUI debugging to be able to introspect active
windows, and infere the active image from its title)

Another "unclean", but tidier, way would be to create a very simple script, with no parameters but "image and drawable" that would just signal your main plug-in when called - and you could bind it to a shortcut key and press it everytime you switch the active image.

To notify your mainplug-in you could use some file-system signaling mechanism, xmlrpc, or some gtk+ mechanism..

I'd use this second approach.

I'm not sure (reposting to list - be sure to 'reply-all' vs just

'reply').

Chris
_______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-developer-list

-------------- next part -------------- An HTML attachment was scrubbed...
URL: <
http://mail.gnome.org/archives/gimp-developer-list/attachments/20120403/ca5746ec/attachment.html

------------------------------

Message: 2 Date: Tue, 3 Apr 2012 05:54:44 -0400 From: Jon Decker
To: gimp-developer-list@gnome.org
Subject: [Gimp-developer] Plugin registration question Message-ID:

Content-Type: text/plain; charset="iso-8859-1"

Hello

The plugin I have been developing doesn't really relate to individual images (its more of an extension). In my registration call, how do I make it so that the listing in the menu is never grayed out? Currently I just open any image to make the entry active, but I'm sure there is a way to make certain entries always active. I'm using the gimpplugin module. Thanks
-------------- next part -------------- An HTML attachment was scrubbed...
URL: <
http://mail.gnome.org/archives/gimp-developer-list/attachments/20120403/d1f9c0d1/attachment.html

------------------------------

Message: 3 Date: Tue, 3 Apr 2012 07:01:40 -0400 From: Jon Decker
To: gimp-developer
Subject: [Gimp-developer] Python plugin debugging and workflow Message-ID:

Content-Type: text/plain; charset="iso-8859-1"

Hello

I have a lot of work into my first large plugin. One thing that really slows my progress is the lack of any kind of debugging or work flow. For example, if I make a syntax error, the plugin will just silently fail, or fail to appear in the menu. I receive no erros or hints as to where the error occured. I normally have to commentoput code line-by-line and rerun the plugin until I find the offending line of code. I've wasted hours at a time finding small little bugs like this.

Is there a way to have gimp relay python errors?

I have also noticed that the python plugins will not run outside of gimp with the standard python interpreter (can't find the gimp imports).

Is there something I'm missing? Is this the workflow that everybody uses? Any hints or tips?

thanks!
-------------- next part -------------- An HTML attachment was scrubbed...
URL: <
http://mail.gnome.org/archives/gimp-developer-list/attachments/20120403/d6d9b88d/attachment.html

------------------------------

Message: 4 Date: Wed, 04 Apr 2012 16:47:11 +0400 From: Paul Geraskin
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] bug with Overlay Message-ID:
Content-Type: text/plain; charset=KOI8-R; format=flowed

I also made my post to bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=673501

------------------------------

Message: 5 Date: Wed, 4 Apr 2012 09:53:52 -0300 From: "Joao S. O. Bueno"
To: Jon Decker
Cc: gimp-developer
Subject: Re: [Gimp-developer] Python plugin debugging and workflow Message-ID:

Content-Type: text/plain; charset=UTF-8

On 3 April 2012 08:01, Jon Decker wrote:

Hello

I have a lot of work into my first large plugin.? One thing that really slows my progress is the lack of any kind of debugging or work flow.? For example, if I make a syntax error, the plugin will just silently fail, or fail to appear in the menu.? I receive no erros or hints as to where the error occured.? I normally have to commentoput code line-by-line and

rerun

the plugin until I find the offending line of code.? I've wasted hours

at a

time finding small little bugs like this.

to detect syntax errors, just try to run your plug-ina s a normal Python program -
Syntax errors will be flagged normally - i the program is well formed, it will fail with an import error
when trying to import gimp or gimpfu

As fro runtime erros, just watch the normal error output of GIMP on the terminal.
(the good news is taht for fixing these errors, you just have to re-run the plugin from inside GIMP<
no need to reinstall or relaod anything).

js ->

Is there a way to have gimp relay python errors?

I have also noticed that the python plugins will not run outside of gimp with the standard python interpreter (can't find the gimp imports).

Is there something I'm missing?? Is this the workflow that everybody

uses?

Any hints or tips?

thanks!

_______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-developer-list

------------------------------

Message: 6 Date: Wed, 4 Apr 2012 15:01:34 +0200 From: Ragnar Brynj?lfsson
To: "Joao S. O. Bueno"
Cc: Jon Decker , gimp-developer

Subject: Re: [Gimp-developer] Python plugin debugging and workflow Message-ID:

Content-Type: text/plain; charset=ISO-8859-1

I'm assuming Jon is working on Windows. On Linux you can just start gimp from a terminal and get all the output you need, but when I was porting a plug-in I wrote to Windows, there was no info in the command line, and I had to resort to printing stuff to the gimp error console. Anyone know how to do this on windows.

One solution is, of course, to just install Linux (on a physical or virtual machine) and do the development on that.

Ragnar

On Wed, Apr 4, 2012 at 2:53 PM, Joao S. O. Bueno wrote:

On 3 April 2012 08:01, Jon Decker wrote:

Hello

I have a lot of work into my first large plugin.? One thing that really slows my progress is the lack of any kind of debugging or work flow.?

For

example, if I make a syntax error, the plugin will just silently fail,

or

fail to appear in the menu.? I receive no erros or hints as to where the error occured.? I normally have to commentoput code line-by-line and

rerun

the plugin until I find the offending line of code.? I've wasted hours

at a

time finding small little bugs like this.

to detect syntax errors, just try to run your plug-ina s a normal Python program -
Syntax errors will be flagged normally - i the program is well formed, it will fail with an import error
when trying to import gimp or gimpfu

As fro runtime erros, just watch the normal error output of GIMP on the terminal.
(the good news is taht for fixing these errors, you just have to re-run the plugin from inside GIMP<
no need to reinstall or relaod anything).

?js ?->

Is there a way to have gimp relay python errors?

I have also noticed that the python plugins will not run outside of gimp with the standard python interpreter (can't find the gimp imports).

Is there something I'm missing?? Is this the workflow that everybody

uses?

Any hints or tips?

thanks!

_______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-developer-list

_______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-developer-list

------------------------------

_______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gimp-developer-list

End of gimp-developer-list Digest, Vol 7, Issue 6 *************************************************

BONSOIR , J'ai eu un gros BUG informatique à savoir que toutes mes données
ne sont plus enregistrer ,de ce fait je doit tout recommencer ( + de 3 ans
de travail ) ENFIN ,je ne baisse pas les bras et je vais tout recommencer ,
MERCI de me comprendre Gerard le senior provencal . à très bientôt .