1 # Coding and Documentation Style
3 [Error Logging](#error-logging)
4 [GPL header](#gpl-header)
5 [Git change log](#git-change-log)
6 [Source Code Style](#source-code-style)
7 [Shell Script Style](#shell-script-style)
8 [External Software Tools](#external-software-tools)
9 [Geeqie Software Tools](#geeqie-software-tools)
10 [Documentation](#documentation)
11 [Documentation - C code](#c-code)
12 [Documentation - Script files](#script-files)
13 [Documentation - Markdown](#markdown)
22 Use `DEBUG_0()` only for temporary debugging i.e. not in code in the repository.
23 The user will then not see irrelevant debug output when the default
24 `debug level = 0` is used.
28 If the first word of the message is "error" or "warning" (case insensitive) the message will be color-coded appropriately.
30 - Note that these messages are output in the idle loop.
34 `print_term(gboolean err, const gchar *text_utf8)`
36 - If `err` is TRUE output is to STDERR, otherwise to STDOUT
38 ### DEBUG_NAME(widget)
40 For use with the [GTKInspector](https://wiki.gnome.org/action/show/Projects/GTK/Inspector?action=show&redirect=Projects%2FGTK%2B%2FInspector) to provide a visual indication of where objects are declared.
42 Sample command line call:
43 `GTK_DEBUG=interactive src/geeqie`
49 Include a header in every file, like this:
53 * Copyright (C) <year> The Geeqie Team
58 * This program is free software; you can redistribute it and/or modify
59 * it under the terms of the GNU General Public License as published by
60 * the Free Software Foundation; either version 2 of the License, or
61 * (at your option) any later version.
63 * This program is distributed in the hope that it will be useful,
64 * but WITHOUT ANY WARRANTY; without even the implied warranty of
65 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
66 * GNU General Public License for more details.
68 * You should have received a copy of the GNU General Public License along
69 * with this program; if not, write to the Free Software Foundation, Inc.,
70 * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
73 * Optional description of purpose of file.
82 If referencing a Geeqie GitHub issue, include the issue number in the summary line and a hyperlink to the GitHub issue webpage in the message body. Start with a short summary in the first line (without a dot at the end) followed by a empty line.
84 Use whole sentences beginning with Capital letter. For each modification use a new line. Or you can write the theme, colon and then every change on new line, begin with "- ".
86 See also [A Note About Git Commit Messages](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
93 There was the bug that something was wrong. I fixed it.
96 - the interface was modified
97 - new functions were added`
100 Also please use your full name and a working e-mail address as author for any contribution.
106 Indentation: tabs at 4 spaces
110 - of variables & functions: small\_letters
111 - of defines: CAPITAL\_LETTERS
113 Try to use explicit variable and function names.
114 Try not to use macros.
115 Use **either** "struct foo" OR "foo"; never both
133 if (<cond_very_very_very_very_very_very_very_very_very_long> &&
134 <cond2very_very_very_very_very_very_very_very_very_long>)
147 for (i = 0; i <= 10; i++)
158 gint bar(<var_def>, <var_def>, <var_def>)
164 return 0; // i.e. SUCCESS; if error, you must return minus <err_no> @FIXME
175 Pragma: (Indentation 2 spaces)
180 # define _(String) (String)
181 #endif /* ENABLE_NLS */
190 Use spaces around every operator (except `.`, `->`, `++` and `--`).
191 Unary operator `*` and `&` are missing the space from right, (and also unary `-`).
193 As you can see above, parentheses are closed to inside, i.e. ` (blah blah) `
194 In `function(<var>)` there is no space before the `(`.
195 You *may* use more tabs/spaces than you *ought to* (according to this CodingStyle), if it makes your code nicer in being vertically indented.
196 Variables declarations should be followed by a blank line and should always be at the start of the block.
198 Use glib types when possible (ie. gint and gchar instead of int and char).
199 Use glib functions when possible (i.e. `g_ascii_isspace()` instead of `isspace()`).
200 Check if used functions are not deprecated.
204 ## Shell Script Style
206 Use `/bin/sh` as the interpreter directive.
207 Ensure the script is POSIX compliant.
208 Use `printf` rather than `echo` except for plain text.
209 There are several versions of `mktemp`. Using the following definition helps portability (note that `template` is not optional):
212 mktemp [-d] [-q] template ...
215 and use for example this style:
218 mktemp "${TMPDIR:-/tmp}/geeqie.XXXXXXXXXX"
222 ## External Software Tools
226 There is no code format program that exactly matches the above style, but if you are writing new code the following command line program formats code to a fairly close level:
229 astyle --options=<options file>
232 Where the options file might contain:
246 A lint-style program may be used, e.g.
249 cppcheck --language=c --library=gtk --enable=all --force -USA_SIGINFO -UZD_EXPORT -Ugettext_noop -DG_KEY_FILE_DESKTOP_GROUP --template=gcc -I .. --quiet --suppressions-list=<suppressions file>
252 Where the suppressions file might contain:
263 Markdown documents may be validated with e.g. [markdownlint](https://github.com/markdownlint/markdownlint).
266 mdl --style <style file>`
269 Where the style file might contain:
273 rule 'MD007', :indent => 4
274 rule 'MD009', :br_spaces => 2
275 rule 'MD010', :code_blocks => true
281 Shell scripts may also be validated, e.g.
284 shellcheck --enable=add-default-case,avoid-nullary-conditions,check-unassigned-uppercase,deprecate-which,quote-safe-variables
289 Shell scripts may formatted to some extent with [shfmt](https://github.com/mvdan/sh). At the time of writing it does not format `if`, `for` or `while` statements in the style used by Geeqie.
290 However the following script can be used to achieve that:
295 shfmt -s -p -ci -sr -fn | awk '
299 printf('%s\n', substr($0, 0, length($0) - 6));
300 printf('%s, substr("\t\t\t\t\t\t\t\t\t\t", 1, RLENGTH))
303 else if ($0 ~ /; do/)
306 printf('%s\n', substr($0, 0, length($0) - 4));
307 printf('%s', substr("\t\t\t\t\t\t\t\t\t\t", 1, RLENGTH))
319 The .xml Help files may be validated with e.g. `xmllint`.
323 ## Geeqie Software Tools
325 See the shell scripts section in the Doxygen documentation (`File List`, `detail level 3`, except the `src` sublist).
331 Use American, rather than British English, spelling. This will facilitate consistent
332 text searches. User text may be translated via the en_GB.po file.
334 To document the code use the following rules to allow extraction with Doxygen.
335 Not all comments have to be Doxygen comments.
339 - Use C comments in plain C files and use C++ comments in C++ files for one line comments.
340 - Use `/**` (note the two asterisks) to start comments to be extracted by Doxygen and start every following line with ` *` as shown below.
341 - Use `@` to indicate Doxygen keywords/commands (see below).
342 - Use the `@deprecated` command to indicate the function is subject to be deleted or to a complete rewrite.
344 To document functions or big structures:
348 * @brief This is a short description of the function.
350 * This function does ...
352 * @param x1 This is the first parameter named x1
353 * @param y1 This is the second parameter named y1
354 * @return What the function returns
355 * You can extend that return description (or anything else) by indenting the
356 * following lines until the next empty line or the next keyword/command.
357 * @see Cross reference
361 To document members of a structure that have to be documented (use it at least
362 for big structures) use the `/**<` format:
365 gint counter; /**< This counter counts images */
369 Document TODO or FIXME comments as:
385 Script files such as .sh, .pl, and .awk should have the file relevant file extension or be symlinked as so.
387 Doxygen comments should start each line with `##`, and each file should contain:
391 ## @brief <one line description>
392 ## <contents description>
398 For a newline use two spaces (a backslash is not interpreted correctly by Doxygen).
402 For further documentation about Doxygen see the [Doxygen Manual](https://www.doxygen.nl/index.html).
403 For the possible commands you may use, see [Doxygen Special Commands](https://www.doxygen.nl/manual/commands.html).
405 The file `./scripts/doxygen-help.sh` may be used to integrate access to the Doxygen files into a code editor.
407 The following environment variables may be set to personalize the Doxygen output:
410 DOCDIR=<output folder>
411 SRCDIR=<the top level directory of the project>
415 INLINE_SOURCES=<YES|NO>
416 STRIP_CODE_COMMENTS=<YES|NO>
419 Ref: [INLINE\_SOURCES](https://www.doxygen.nl/manual/config.html#cfg_inline_sources)
420 Ref: [STRIP\_CODE\_COMMENTS](https://www.doxygen.nl/manual/config.html#cfg_strip_code_comments)
422 For shell scripts to be documented, the file `doxygen-bash.sed` must be in the `$PATH` environment variable.
423 It can be download from here:
426 wget https://raw.githubusercontent.com/Anvil/bash-doxygen/master/doxygen-bash.sed
427 chmod +x doxygen-bash.sed
430 To include diagrams in the Doxygen output, the following are required to be installed. The installation process will vary between distributions:
432 [The PlantUML jar](https://plantuml.com/download)
435 sudo apt install default-jre
436 sudo apt install texlive-font-utils
441 But in case just think about that the documentation is for other developers not
442 for the end user. So keep the focus.