for Windows GNU Image Manipulation Program Skip to page contents [ News | Screenshots | Features | Downloads | Documentation | Get Involved ][ Plug-in Registry | GIMP Development ] [ Donations ] [ GIMP for Microsoft Windows This page is obsolete, please see the downloads page. Raster Images versus Vector Images These two formats are quite different from one another, yet they contrast and complement one another when used appropriately for the desired final output method. Raster images are created through the process of scanning source artwork or "painting" with a photo editing or paint program such as Corel PhotoPAINT or Adobe PhotoShop. Vector images are created through the process of drawing with vector illustration programs such as CorelDRAW or Adobe Illustrator. The word "vector" is a synonym for line. Raster Images A raster image is a collection of dots called pixels. Resolution The resolution of a raster image or scanned image is expressed in terms of the dots per inch or dpi. Take a 300 dpi bitmap and increase the size in a graphics program, and presto - you have created a bad case of the "jaggies". Color With any scanned color image, a large number of colors will be required to render a raster image reproduction of the original source artwork accurately. -----> Continued below
Mailing Lists If you want to discuss features, tips, tricks or contribute to the development of GIMP, then we have several useful mailing lists and IRC channels for you. GIMP User The original (mostly unix based) user list. GIMP Developer The GIMP developer list. GEGL Developer The GEGL developer list. GIMP Web The GIMP web list. GIMP Docs The GIMP documentation list. Mailing lists are an important communication channel between contributors and users of GIMP. Be considerate and respectful. The code may change in the future, followed by a notification to subscribers. Please use these sources to check for information on the project, roadmap, feature requests, bug reports etc Bug tracker. We also suggest checking archives of the mailing lists for existing discussions.
IRC Channels Several IRC channels and mailing lists are available for discussing GIMP-related topics. IRC offers real-time communication, but be aware that there may be long periods of silence in the channels when other users are busy or away from their keyboards. When you join the GIMP IRC channels, please do not ask if somebody can help you. If you have a question, ask directly and then wait patiently to see if someone answers. Other recommendations can be found at the bottom of this page. The official GIMP IRC channels are on GIMPNet (irc.gimp.org) and have existed for more than 10 years. The main support channel for GIMP users. This is the main GIMP channel, created in early 1997. A channel devoted to this web site and related GIMP sites. Being an abbreviation of "gimp social", this channel is for the GIMP people, and anything but GIMP is ontopic here.
GIMP Script-Fu changes in GIMP 2.4 (migration guide) - Script-Fu Migration Guide Since version 1.0 of GIMP, it has included a powerful scripting language which permits extending the program's capabilities and simplifying repetitive tasks. This scripting language, called "Script-fu", was based upon the Scheme programming language and implemented the SIOD interpreter written by George J. Carrette while he was a professor at Boston University in the late 80s. This Script-fu interpreter based upon Carrette's SIOD has served GIMP extremely well over the last decade -- thousands of scripts have been written and shared by GIMP users -- but it is starting to show its age and therefore the GIMP development team has decided to replace it with a more modern Scheme interpreter called TinyScheme. Though this switch has required an extensive effort on the part of GIMP developers (particularly Kevin Cozens) and some significant changes to the internals of the GIMP code, there should be very little visible change to GIMP users. Setting an undeclared variable Constructing a pair
GIMP Script-Fu documentation - Script-Fu and plug-ins for The GIMP Simon Budig One of the big advantages of The GIMP is the fact that it can be easily extended with new functionality. However, it is not easy to find documentation about this. I will cover the default scripting extension Script-Fu and some details for programming plug-ins in C. The PDB (Procedural DataBase) is the most important interface to access the image manipulation functions of The GIMP. Each plug-in enters its functionality into the PDB, which enables it to be used by other plug-ins or scripts. Writing a binding for a programming language – for example Scheme or Perl – just requires mapping the PDB onto the syntax of the target language and providing access to the various parameter types. A typical PDB entry contains this information (this is a screenshot of ): You can see that a function can have different types of input and output parameters.
GIMP Python module documentation This document outlines the interfaces to GIMP-Python, which is a set of Python modules that act as a wrapper to libgimp allowing the writing of plug-ins for GIMP. In this way, GIMP-Python is similar to Script-Fu, except that you can use the full set of Python extension modules from the plug-in. Introduction What is it? GIMP-Python is a scripting extension for GIMP, similar to Script-Fu. In fact, you will find that the GIMP-Python scripts start with the line ! Another point of difference between GIMP-Python and Script-Fu is that GIMP-Python stores images, layers, channels and other types as objects rather than just storing their ID. Also, GIMP-Python is not limited to just calling procedures from the PDB. Installation GIMP-python consists of a Python module written in C and some native python support modules. . This will build and install gimpmodule and its supporting modules, and install the sample plug-ins in GIMP's plug-in directory. The Structure Of A Plug-in An Example Plugin #! proc_name
GIMP Manual Pages - gimprc (5) - RC(5) manual page Comments are introduced by a hash sign (#), and continue until the end of the line. Blank lines are ignored. The gimprc file associates values with properties. These properties may be set by lisp-like assignments of the form: Either spaces or tabs may be used to separate the name from the value. (temp-path "${gimp_dir}/tmp") Sets the folder for temporary storage. (swap-path "${gimp_dir}") Sets the swap file location. (num-processors 1) Sets how many processors GIMP should try to use simultaneously. (tile-cache-size 1024M) When the amount of pixel data exceeds this limit, GIMP will start to swap tiles to disk. (interpolation-type cubic) Sets the level of interpolation used for scaling and other transformations. Sets the plug-in search path. Sets the module search path. Sets the interpreter search path. Sets the environ search path. Sets the brush search path. (brush-path-writable "${gimp_dir}/brushes") This is a colon-separated list of folders to search. Sets the pattern search path.
GIMP Manual Pages - gimp (1) - 1) manual page Table of Contents Name gimp - an image manipulation and paint program. Synopsis gimp [-h] [--help] [--help-all] [--help-gtk] [-v] [--version] [--license] [--verbose] [-n] [--new-instance] [-a] [--as-new] [-i] [--no-interface] [-d] [--no-data] [-f] [--no-fonts] [-s] [--no-splash] [--no-shm] [--no-cpu-accel] [--display display] [--session <name>] [-g] [--gimprc <gimprc>] [--system-gimprc <gimprc>] [--dump-gimprc] [--console-messages] [--debug-handlers] [--stack-trace-mode <mode>] [--pdb-compat-mode <mode>] [--batch-interpreter <procedure>] [-b] [--batch <command>] [filename] ... Description GIMP is the GNU Image Manipulation Program. GIMP can also be used as a paint program. GIMP offers a variety of plug-ins that perform a variety of image manipulations. GIMP ships with a second binary called gimp-console. On platforms with the D-Bus message bus system, GIMP will by default check if an instance is already running in this user session. Options GIMP accepts the following options: -h, --help Files