
Submitting patches:
~~~~~~~~~~~~~~~~~~~
diff -Nur OroboROX.original OroboROX.patched >OroboROX-$VERSION-SOME_DESCRIPTIVE_PATCHNAME.diff
When your patch affects only a single file you may create a level 0 patch, but level 1 as above
is still preferred, except its only a handfull of lines which can be applied manually with ease.

make sure your patch applies cleanly and doesn't produce compiler warnings. Release code most
not triggger compiler warnings. except the maintainer my decide to add "FIXME" warnings.
Contributed code is supposed to fix problems, not create them.

Codying style:
~~~~~~~~~~~~~~
* tabsize = 4
* use TRUE/FALSE (from glib) instead True/False
* use gboolean where apropriate
* use of glib names for standard types (gint, gchar...) is in order, but optional
* do NOT! gratiously wrap statements over multiple lines.
  Make use of those 80 char lines! Sometimes 100 char lines are in order as well.
  (disable horizontal scrolling in your editor!)
* match indentation style with existing code or use the following options with GNU indent:

--blank-lines-after-declarations
--blank-lines-after-procedures
--brace-indent0
--braces-after-if-line
--braces-on-struct-decl-line
--cuddle-do-while
--continuation-indentation4
--case-indentation4
--space-after-cast
--indent-level4
--line-length100
--comment-line-length100
--continue-at-parentheses
--break-after-boolean-operator
--no-space-after-function-call-names
--dont-break-procedure-type
--paren-indentation4
--space-after-for
--space-after-if
--space-after-while
--struct-brace-indentation4
--tab-size4
--use-tabs


