dnrops
/
gimp
mirror of https://github.com/GNOME/gimp.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update various places with old git repository URIs.

This commit is contained in:
Jehan 2018-05-27 04:18:15 +02:00
parent 0034bd44b3
commit c6a1b9bcde
5 changed files with 18 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
HACKING
View File

@ -79,7 +79,7 @@ Git
GIMP is available from GNOME Git. You can use the following commands GIMP is available from GNOME Git. You can use the following commands
to get GIMP from the the git server: to get GIMP from the the git server:
$ git clone git://git.gnome.org/gimp $ git clone https://gitlab.gnome.org/GNOME/gimp.git
You can read more on using GNOME's git service at these URLs: You can read more on using GNOME's git service at these URLs:

4
INSTALL.in
View File

@ -42,8 +42,8 @@ header files installed.
@BABL_REQUIRED_VERSION@ or newer. You can get them from http://gegl.org/ or clone @BABL_REQUIRED_VERSION@ or newer. You can get them from http://gegl.org/ or clone
them from the GNOME git repository: them from the GNOME git repository:
git://git.gnome.org/babl https://gitlab.gnome.org/GNOME/babl.git
git://git.gnome.org/gegl https://gitlab.gnome.org/GNOME/gegl.git
4. You need to have installed GTK+ version @GTK_REQUIRED_VERSION@ or newer. 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 GIMP also needs a recent version of GLib (>= @GLIB_REQUIRED_VERSION@), GDK-Pixbuf

2
build/flatpak/flathub

@ -1 +1 @@
Subproject commit bf7aff31ff6875dbab3cc53b300414ed01444c78 Subproject commit b6030b22367300babf82d5ed3b9158d25c9902f0

4
build/windows/jhbuild/gimp.moduleset
View File

@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<moduleset> <moduleset>
<repository type="git" name="git.gnome.org" default="yes" <repository type="git" name="gitlab.gnome.org" default="yes"
href="git://git.gnome.org/"/> href="https://gitlab.gnome.org/GNOME/"/>
<include href="gtk+.moduleset"/> <include href="gtk+.moduleset"/>
<include href="webkitgtk.moduleset"/> <include href="webkitgtk.moduleset"/>

24
pdb/README_NEW_PDB_PROC
View File

@ -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 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 developed to add functions to the PDB by writing them once. To see how
function are implemented in the PDB, take a look in function are implemented in the PDB, take a look in
http://git.gnome.org/browse/gimp/tree/pdb/groups[pdb/groups]. https://gitlab.gnome.org/GNOME/gimp/tree/master/pdb/groups[pdb/groups].
You can see many files with the .pdb suffix - these are special template 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 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 quick look at one of these - text_layer_get_text in
http://git.gnome.org/browse/gimp/tree/pdb/groups/text_layer.pdb[pdb/groups/text_layer.pdb]. https://gitlab.gnome.org/GNOME/gimp/tree/master/pdb/groups/text_layer.pdb[pdb/groups/text_layer.pdb].
[source,perl] [source,perl]
---- ----
@ -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. meaningful and be a valid name for a variable in C.
The type is one of the types listed in The type is one of the types listed in
http://git.gnome.org/browse/gimp/tree/pdb/pdb.pl[pdb/pdb.pl] https://gitlab.gnome.org/GNOME/gimp/tree/master/pdb/pdb.pl[pdb/pdb.pl]
inside the +%arg_types+ array. In inside the +%arg_types+ array. In
http://git.gnome.org/browse/gimp/tree/pdb/pdb.pl[pdb/pdb.pl] https://gitlab.gnome.org/GNOME/gimp/tree/master/pdb/pdb.pl[pdb/pdb.pl]
you can see the corresponding C type for each of the types we specify. 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 For example, +layer+ type (inside the .pdb file) becomes a variable with
the C type of +GimpLayer *+, and +string+ becomes +gchar *+. 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. enums which are already used by GIMP.
To make it clearer, let's take a look at +layer_get_mode+ in To make it clearer, let's take a look at +layer_get_mode+ in
http://git.gnome.org/browse/gimp/tree/pdb/groups/layer.pdb[pdb/groups/layer.pdb]: https://gitlab.gnome.org/GNOME/gimp/tree/master/pdb/groups/layer.pdb[pdb/groups/layer.pdb]:
[source,perl] [source,perl]
---- ----
@ -367,7 +367,7 @@ ANTI-ERASE-MODE (25) }
As you can see, all the values of the enum were listed (the source file As you can see, all the values of the enum were listed (the source file
containing this enum is containing this enum is
http://git.gnome.org/browse/gimp/tree/app/base/base-enums.h[app/base/base-enums.h]) https://gitlab.gnome.org/GNOME/gimp/tree/master/app/base/base-enums.h[app/base/base-enums.h])
in it's description, and the type for this argument was declared as an 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 integer value (reminder: enumeration values in C are actually mapped to
numbers, unlike languages such as Java where enumeration values are 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 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 range before it calls our function). To see an example, let's take look
at the procedure image_new from at the procedure image_new from
http://git.gnome.org/browse/gimp/tree/pdb/groups/image.pdb[pdb/groups/image.pdb]: https://gitlab.gnome.org/GNOME/gimp/tree/master/pdb/groups/image.pdb[pdb/groups/image.pdb]:
[source,perl] [source,perl]
---- ----
@ -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 we added a limitation on the range of the parameter. The lower
limitation is a simple number, and the upper limitation is a constant limitation is a simple number, and the upper limitation is a constant
macro (+GIMP_MAX_IMAGE_SIZE+) defined in macro (+GIMP_MAX_IMAGE_SIZE+) defined in
http://git.gnome.org/browse/gimp/tree/libgimpbase/gimplimits.h[libgimpbase/gimplimits.h]. https://gitlab.gnome.org/GNOME/gimp/tree/master/libgimpbase/gimplimits.h[libgimpbase/gimplimits.h].
In order to make sure this constand will indeed be defined when parsing In order to make sure this constand will indeed be defined when parsing
this function, the file this function, the file
http://git.gnome.org/browse/gimp/tree/libgimpbase/gimpbase.h[libgimpbase/gimpbase.h] https://gitlab.gnome.org/GNOME/gimp/tree/master/libgimpbase/gimpbase.h[libgimpbase/gimpbase.h]
(which includes (which includes
http://git.gnome.org/browse/gimp/tree/libgimpbase/gimplimits.h[libgimpbase/gimplimits.h]) https://gitlab.gnome.org/GNOME/gimp/tree/master/libgimpbase/gimplimits.h[libgimpbase/gimplimits.h])
was added to the +@headers+ section of the pdb file. 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 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 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+ how array arguments are specified, let's take a look at the +@outargs+
of +vectors_stroke_get_points+ from of +vectors_stroke_get_points+ from
http://git.gnome.org/browse/gimp/tree/pdb/groups/vectors.pdb[pdb/groups/vectors.pdb]: https://gitlab.gnome.org/GNOME/gimp/tree/master/pdb/groups/vectors.pdb[pdb/groups/vectors.pdb]:
[source,perl] [source,perl]
---- ----
@ -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!). developers agree that it's needed!).
Don't forget to include the functions inside the right files! Under Don't forget to include the functions inside the right files! Under
http://git.gnome.org/browse/gimp/tree/pdb/groups[pdb/groups] https://gitlab.gnome.org/GNOME/gimp/tree/master/pdb/groups[pdb/groups]
you can see many files (fonts.pdb, brush.pdb, layer.pdb, etc.) - *make 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!* sure you add your function in the place which logically suites it!*