Commit c6a1b9bc authored by Jehan's avatar Jehan
Browse files

Update various places with old git repository URIs.

parent 0034bd44
......@@ -79,7 +79,7 @@ Git
GIMP is available from GNOME Git. You can use the following commands
to get GIMP from the the git server:
$ git clone git://
$ git clone
You can read more on using GNOME's git service at these URLs:
......@@ -42,8 +42,8 @@ header files installed.
@BABL_REQUIRED_VERSION@ or newer. You can get them from or clone
them from the GNOME git repository:
4. You need to have installed GTK+ version @GTK_REQUIRED_VERSION@ or newer.
GIMP also needs a recent version of GLib (>= @GLIB_REQUIRED_VERSION@), GDK-Pixbuf
Subproject commit bf7aff31ff6875dbab3cc53b300414ed01444c78
Subproject commit b6030b22367300babf82d5ed3b9158d25c9902f0
<?xml version="1.0" encoding="UTF-8"?>
<repository type="git" name="" default="yes"
<repository type="git" name="" default="yes"
<include href="gtk+.moduleset"/>
<include href="webkitgtk.moduleset"/>
......@@ -58,12 +58,12 @@ Since adding a function to the PDB can be tedious (you would need to
modify 3 or more different source files), a scripting framework was
developed to add functions to the PDB by writing them once. To see how
function are implemented in the PDB, take a look in[pdb/groups].[pdb/groups].
You can see many files with the .pdb suffix - these are special template
files which include the actual source of the PDB functions. Let's take a
quick look at one of these - text_layer_get_text in[pdb/groups/text_layer.pdb].[pdb/groups/text_layer.pdb].
......@@ -207,9 +207,9 @@ a description. The name will be used later in our code and it should be
meaningful and be a valid name for a variable in C.
The type is one of the types listed in[pdb/][pdb/]
inside the +%arg_types+ array. In[pdb/][pdb/]
you can see the corresponding C type for each of the types we specify.
For example, +layer+ type (inside the .pdb file) becomes a variable with
the C type of +GimpLayer *+, and +string+ becomes +gchar *+.
......@@ -337,7 +337,7 @@ this can be done automatically for you if the desired enum is one of the
enums which are already used by GIMP.
To make it clearer, let's take a look at +layer_get_mode+ in[pdb/groups/layer.pdb]:[pdb/groups/layer.pdb]:
......@@ -367,7 +367,7 @@ ANTI-ERASE-MODE (25) }
As you can see, all the values of the enum were listed (the source file
containing this enum is[app/base/base-enums.h])[app/base/base-enums.h])
in it's description, and the type for this argument was declared as an
integer value (reminder: enumeration values in C are actually mapped to
numbers, unlike languages such as Java where enumeration values are
......@@ -388,7 +388,7 @@ function, and by that we can make sure it won't be called with values
out of range (GIMP will make sure the values are inside the specified
range before it calls our function). To see an example, let's take look
at the procedure image_new from[pdb/groups/image.pdb]:[pdb/groups/image.pdb]:
......@@ -406,12 +406,12 @@ As you can see, inside the +*type*+ field of the first two parameters,
we added a limitation on the range of the parameter. The lower
limitation is a simple number, and the upper limitation is a constant
macro (+GIMP_MAX_IMAGE_SIZE+) defined in[libgimpbase/gimplimits.h].[libgimpbase/gimplimits.h].
In order to make sure this constand will indeed be defined when parsing
this function, the file[libgimpbase/gimpbase.h][libgimpbase/gimpbase.h]
(which includes[libgimpbase/gimplimits.h])[libgimpbase/gimplimits.h])
was added to the +@headers+ section of the pdb file.
Now, if you take a look at the code part of this function you won't see
......@@ -435,7 +435,7 @@ function which receives an array. Array arguments are specified in a
special way which is a bit different than the other arguments. To see
how array arguments are specified, let's take a look at the +@outargs+
of +vectors_stroke_get_points+ from[pdb/groups/vectors.pdb]:[pdb/groups/vectors.pdb]:
......@@ -502,6 +502,6 @@ before working on a new function like this, since you need to see if the
developers agree that it's needed!).
Don't forget to include the functions inside the right files! Under[pdb/groups][pdb/groups]
you can see many files (fonts.pdb, brush.pdb, layer.pdb, etc.) - *make
sure you add your function in the place which logically suites it!*
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment