Sven Neumann wrote:

Hi,

just wanted to point the people subscribed here to this thread over at the gimp-developer list:

http://lists.xcf.berkeley.edu/lists/gimp-developer/2006-March/015323.html

Since not much coding skills (if any) are needed to be able to help with this, I thought it would be appropriate to include the gimp-user list.

Sven

Hi Sven,

I have no possibility for CVS access (no internet at home, and filtered access at work). Is there a bug# where such text blobs could be posted/discussed ? If not, is posting to the mailing-list acceptable ?

Regards,

Olivier.

Sven Neumann wrote:

Hi,

Olivier Ripoll writes:

I have no possibility for CVS access (no internet at home, and filtered access at work). Is there a bug# where such text blobs could be posted/discussed ? If not, is posting to the mailing-list acceptable ?

I don't have the resources to prepare such a list nor to merge the changes back into the source tree. For a review process it would perhaps be possible to somehow extract a list of the strings. But it should be a lot easier to just do these changes in the source code.

Sven

PS: CVS can be tunneled. But I don't want to get you into trouble...

Is there a possibility to use the latest tar.gz (2.3.7) and diff patches from it ?

Looking at the web cvs interface for gnome (this I can access, it is http), I can for instance see this recent change you did to the blur plugin: http://cvs.gnome.org/viewcvs/gimp/plug-ins/common/blur.c?r1=1.67&r2=1.68

You added a const gchar string const gchar *help =
"This plug-in blurs the specified drawable, using a 3x3 blur. " "Indexed images are not supported.";

So all is needed is to find a string to best describe the plugin, and store it in this help pointer, isn't it ?

It seems the help string can be multiline, am I correct on this ?

Best regards,

Olivier

Olivier Ripoll wrote:

Sven Neumann wrote:

Hi,

Olivier Ripoll writes:

I have no possibility for CVS access (no internet at home, and filtered access at work). Is there a bug# where such text blobs could be posted/discussed ? If not, is posting to the mailing-list acceptable ?

I don't have the resources to prepare such a list nor to merge the changes back into the source tree. For a review process it would perhaps be possible to somehow extract a list of the strings. But it should be a lot easier to just do these changes in the source code.

Sven

PS: CVS can be tunneled. But I don't want to get you into trouble...

Is there a possibility to use the latest tar.gz (2.3.7) and diff patches from it ?

Looking at the web cvs interface for gnome (this I can access, it is http), I can for instance see this recent change you did to the blur plugin:
http://cvs.gnome.org/viewcvs/gimp/plug-ins/common/blur.c?r1=1.67&r2=1.68

You added a const gchar string const gchar *help =
"This plug-in blurs the specified drawable, using a 3x3 blur. " "Indexed images are not supported.";

So all is needed is to find a string to best describe the plugin, and store it in this help pointer, isn't it ?

It seems the help string can be multiline, am I correct on this ?

Best regards,

Olivier

small correction: you also changed the call to gimp_install_procedure() to use the constant strings.

Olivier.

Olivier Ripoll wrote:

small correction: you also changed the call to gimp_install_procedure() to use the constant strings.

Olivier.

correction:
It is the other way around. You removed the strings. I had read the diff the wrong way.
So the tooltip is put in the N_(), correct ?

N_("Apply a 3x3 blurring convolution kernel"), (blur)
or
N_("Simulate movement by applying a blur effect"), (motion blur)

Best regards,

Olivier