depau/Purism-Calls
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/calls.git synced 2024-05-13 16:49:29 +00:00
Code Issues Releases Wiki Activity

HACKING: Update and clarify

Browse source
This commit is contained in:
Evangelos Ribeiro Tzaras 2023-01-22 09:49:41 +01:00
parent 4d2f3f0b3b
commit 7dc99aab13
1 changed files with 5 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
HACKING.md
View file

@ -31,8 +31,8 @@ which itself is mostly using [libhandy's Coding Style][3].
These are the differences: These are the differences:
- We're not picky about GTK+ style function argument indentation, that is - We're not picky about GTK+ style function argument indentation, that is
having multiple arguments on one line is also o.k. having multiple arguments on one line is also o.k when there are only two arguments.
- For callbacks we additionally allow for the `on_<action>` pattern e.g. - For callbacks we prefer the `on_<action>` pattern e.g.
`on_feedback_ended ()` since this helps to keep the namespace `on_feedback_ended ()` since this helps to keep the namespace
clean. clean.
- Since we're not a library we usually use `G_DEFINE_TYPE` instead of - Since we're not a library we usually use `G_DEFINE_TYPE` instead of
@ -61,12 +61,14 @@ individual C files should be structured as (top to bottom of file):
``` ```
Usually just the GObject. Usually just the GObject.
- `#include`s: - `#include`s:
Calls ones go first, then glib/gtk, then generic C headers. These blocks Calls configuration (if needed) goes first, then Calls includes, then glib/gtk, then generic C headers. These blocks
are separated by newline and each sorted alphabetically: are separated by newline and each sorted alphabetically:
``` ```
#define G_LOG_DOMAIN "CallsThing" #define G_LOG_DOMAIN "CallsThing"
#include "calls-config.h"
#include "calls-things.h" #include "calls-things.h"
#include "calls-other-things.h" #include "calls-other-things.h"