Capítulo 13. Automatizar tareas en GIMP

Tabla de contenidos

1. Complementos
1.1. Introducción
1.2. Usar los complementos
1.3. Instalación de nuevos complementos
1.4. Escribir complementos
2. Uso de guiones Script-Fu
2.1. ¿Qué es Script-Fu?
2.2. Installing Script-Fu scripts
2.3. Qué hacer y qué no hacer
2.4. Diferentes tipos de Scripts-Fu
3. Un tutorial de Script-Fu
3.1. Conociendo el Scheme
3.2. Variables y funciones
3.3. Listas, listas y más listas
3.4. Su primer código de Script-Fu
3.5. Dar algo de sustancia a nuestro script
3.6. Extender el script «Text Box»
3.7. Su script y su trabajo

1. Complementos

1.1. Introducción

Una de las principales bondades de GIMP es la facilidad con que se puede extender su funcionalidad, por medio de complementos. Los complementos de GIMP son programas externos que corren bajo el control de la aplicación GIMP, e interactúan con ella. Los complementos pueden modificar las imágenes casi de la misma manera en que pueden hacerlo los usuarios. Su ventaja es que es mucho más fácil añadir una capacidad a GIMP escribiendo un pequeño complemento que modificar la gran masa de código complejo que forma el núcleo de GIMP. Muchos de los complementos más valorados están hechos en sólo unas cien o doscientas líneas de código fuente en C.

Several dozen plugins are included in the main GIMP distribution, and installed automatically along with GIMP. Most of them can be accessed through the Filters menu (in fact, everything in that menu is a plugin), but a number are located in other menus. In many cases you can use one without ever realizing that it is a plugin: for example, the "Normalize" function for automatic color correction is actually a plugin, although there is nothing about the way it works that would tell you this. Even importing and exporting of images is done by plugins.

Everyone can write a GIMP plugin and make it available online. There are many useful plugins that can be obtained this way. Some of them are described elsewhere in the User's Manual.

With this free availability comes a certain degree of risk. The fact that anyone can release plugins means that there is no effective quality control. The plugins distributed with GIMP have all been tested and tuned by the developers. Additional plugins available online, may have been hacked together in a few hours and then abandoned. Some plugin creators don't care about robustness, and even for those who do, their ability to test on a variety of systems in a variety of situations is often quite limited. Basically, when you download a plugin, you are getting something for free, and sometimes you get exactly what you pay for. This is not to discourage you, just to make sure you understand that not all plugins available online will deliver what you expect from them.

[Aviso] Aviso

Plugins, being full-fledged executable programs, can do all of the things that any other program can do. This includes installing back-doors on your system or otherwise compromise its security. Don't install a plugin unless it comes from a trusted source.

[Nota] Nota

Plugins written for a certain version of GIMP may not always work well in other versions. Though in general the GIMP team tries to minimize changes that affect plugins. Usually the only time you can expect serious problems with plugins, is when the major version of GIMP changes. When a plugin made for an older version doesn't work correctly anymore, it needs to be ported. Sometimes this is easy, sometimes not. Bottom line: before trying to install a plugin, make sure that it is compatible with your version of GIMP.

1.2. Usar los complementos

En general se hace uso de un complemento sin ni siquiera notarlo, como con otras herramientas de GIMP. Pero hay algunos detalles sobre los complementos que es útil conocerlos.

One is that plugins are generally not as robust as the GIMP core. When GIMP crashes, it is considered a very serious thing: it can cost the user a lot of trouble and headache. When a plugin crashes, the consequences are usually not as serious. In most cases you can continue working without worrying about it too much.

[Nota] Nota

Because plugins are separate programs, they communicate with GIMP in a special way: The GIMP developers call it talking over a wire. When a plugin crashes, the communication breaks down, and you may see an error message about a wire read error.

[Sugerencia] Sugerencia

Cuando un complemento se rompe, GIMP le proporciona un mensaje diciendo que un complemento puede haber dejado a GIMP en un estado corrupto, y que debería considerar guardar las imágenes y salir. Estrictamente hablando, esto es correcto, porque los complementos tienen la capacidad de modificar casi todo en GIMP, pero en la práctica, la experiencia ha demostrado que dicha corrupción ocurre muy raramente, y muchos usuarios continúan trabajando sin preocuparse. El consejo es que considere los problemas que se provocarían si algo fuera mal, y lo compare con lo incómodo que es salir y volver a iniciar.

Because of the way plugins communicate with GIMP, they do not have any mechanism for being informed about changes you make to an image after the plugin has been started. If you start a plugin, and then alter the image using some other tool, the plugin may crash. Even if it doesn't, doing this may cause incorrect results. You should avoid running more than one plugin at a time on an image, and avoid doing anything to the image until the plugin has finished working on it. If you ignore this advice, not only could you screw up the image, you may also screw up the undo system, so that you won't be able to recover from your mistake.

1.3. Instalación de nuevos complementos

The plugins that are distributed with GIMP don't require installation. Plugins that you download yourself do. Usually the default location is in GIMP's user directory in a folder under /plug-ins, where the folder name needs to be the same as the plugin filename. You can find the default locations where GIMP searches for plugins in GIMP's folder preferences. There you can also add new locations where GIMP should look for plug-ins. There are several scenarios, depending on what OS you are using and how the plugin is structured.

1.3.1. Sistemas similares a Linux o Unix

La mayoría de los complementos encajan en dos categorías: lo pequeños, cuyo código fuente se distribuye en un único archivo «.c», y los grandes cuyo código fuente se distribuye como una carpeta que contiene varios archivos, incluyendo un archivo Makefile.

For a simple one-file plugin, call it borker.c, installing it is just a matter of running the command gimptool-2.0 --install borker.c. This command compiles the plugin and installs it in your personal plugin directory, ~/gimp-2.10/plug-ins unless you have changed it. This will cause it to be loaded automatically the next time you start GIMP. You don't need to be root to do these things; in fact, you shouldn't be. If the plugin fails to compile, well, be creative.

1.3.2. Windows

Most GIMP plugins available on Windows supply either an installer, or can be downloaded in a pre-compiled binary format ready to copy to a folder of your choice that is recognized by GIMP.

If an installer is available, that should do all the work for you selecting an appropriate folder and copying all relevant files. If not, you may have to check in GIMP's folder preferences where the plugins should be copied to. Remember, each plugin needs to be in its own folder with the same name as the plugin.

1.3.3. Apple Mac OS X

How you install plugins on OS X mostly depends on how you installed GIMP itself. If you were one of the brave and installed GIMP through one of the package managers like fink [FINK] or darwinports [DARWINPORTS], the plugin installation works exactly the way it is described for the Linux platform already. The only difference is, that a couple of plugins might be even available in the repository of your package manager, so give it a try.

If, on the other hand, you prefer to grab a prebuilt GIMP package like, you most likely want to a prebuilt plugin too. You can try to get a prebuilt version of the plugin of your dreams from the author of the plugin. Building your own binaries unfortunately involves installing GIMP.

1.3.4. Running the installed plugin

Once you have installed the plugin, how do you activate it? The menu path is determined by the plugin itself, so to answer this you need to either look at the documentation for the plugin (if there is any), explore the menus, or use GIMP's command search function by pressing / and then entering the name of the plugin. If you know how to read source code you could also check that to see in what menu it registers itself.

For more complex plugins, organized as a directory with multiple files, there usually is a file inside called either INSTALL or README, with instructions. If not, the best advice is to toss the plugin in the trash and spend your time on something else: any code written with so little concern for the user is likely to be frustrating in myriad ways.

If you install a plugin in your personal plugin directory that has the same name as one in the system plugin directory, only one can be loaded, and it will be the one in your home directory. You will receive messages telling you this each time you start GIMP. This is probably a situation best avoided.

1.4. Escribir complementos

Si desea aprender a escribir complementos, puede hallar mucha ayuda en el sitio web de los desarrolladores de GIMP [GIMP-DEV-PLUGIN]. GIMP es un programa complejo, pero los desarrolladores han hecho un gran esfuerzo para que la curva de aprendizaje sea suave, especialmente para la codificación de complementos. Hay muy buenas instrucciones y ejemplos, y la biblioteca principal que emplean los complementos como interfaz con GIMP (llamada libgimp) cuenta con una API muy bien documentada. Los buenos programadores, que aprenden modificando los complementos existentes, llegan a lograr cosas interesantes en unos pocos días de trabajo.