Hi Javi,

javi palau wrote:

Two questions:
1º When i execute my plug-in for 2nd time, i'd like to configure the parameters like the user introduce the first time. Is there any "gimp memory" to save the values introduced by the user?

You can tell when a plug-in is re-run by testing the run mode (parameter 0 of the input parameters of every plug-in). If it is GIMP_RUN_WITH_LAST_VALS, the plug-in has been run with that menu item, if it's run GIMP_RUN_INTERRACTIVE it has been run through a menu entry.

The usual way that you get back last used values is to call gimp_set_data(plug_in_name, pointer_to_option_struct, sizeof(option_struct));

So the first thing that you can do after starting the plug-in is to call
gimp_get_data(plug_in_name, pointer_to_option_struct);

2ºHow i can know the language used by GIMP?. I've been searching in the "gimprc" file, but i haven't found anything.

The GIMP is written in C, primarily, but you can write plug-ins in any language which wraps libgimp (if it wraps gtk+ as well, all the better). That currently includes perl, python and scheme (script-fu), but there is no reason not to have others.

The gimprc file format is a readable serialisation of internal configuration stuff, I don't think you could call it a language.

Cheers, Dave.

javi palau (javipalau@hotmail.com) wrote:

2ºHow i can know the language used by GIMP?. I've been searching in the "gimprc" file, but i haven't found anything.

We use the gettext library to determine what language the text in our user interface should be. In fact gettext does all the hard work for us.

You can also use it for your plugin and you'll automatically have the same language as the rest of the GIMP.

Bye, Simon

On 22.07.2004, at 23:19, Simon Budig wrote:

We use the gettext library to determine what language the text in our user interface should be. In fact gettext does all the hard work for us.

Not quite but almost. :) The choice of language is expressed by setting environment variables. Those are picked up by the i18n environment which is hosted either by the libc or in a on some systems in freestanding library called libintl. What is called gettext is on one hand the library call which will do the translation[1] and on the other hand a set of userland tools[2] to extract strings from the sourcecode, convert human readable text into machine optimized binary form and do other manipulations on catalogs.

[1] iff the language is set, differs from the default English and a catalog in one of the choosen languages with a matching translation string is available [2] also the name of one particular tool within the set

Servus, Daniel

Hi,

"javi palau" writes:

Hi, I'm a student who's developing a GIMP plug-in. I've been reading the API's documents but i haven't found the solution.

I strongly suggest you look at some of the plug-ins distributed with GIMP and also get your hands on the gimp-plugin-template [1]. That should answer your questions.

Sven

[1] http://developer.gimp.org/plug-in-template.html