Development - Indenting and Formatting

From Bluefish Wiki
Revision as of 11:13, 9 July 2010 by Bill Valaski (talk | contribs) (moved Man 2 ch12 to Development - Indenting and Formatting: Title updates (BV))
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Man2 warning.png This page is a copy from Manual 1. It needs to be modified to match Bluefish version 2.0.0!
Once you have verified this page (and corrected if necessary),

please modify the status to u (updated), i.e. st=u (see Guidelines for Writing this Manual)

Man2 icon 48.png
Part 3. Developing Bluefish
Chapter XII. Development guidelines

Work hard but have fun!

1. Indenting and formating style

Indenting can be done with the indent command line tool. Bluefish uses tabs - not spaces, and I'll explain why.

Some programmers prefer a lot of indenting, 8 characters, some prefer less, 3 characters. If Bluefish code was indented with spaces, these programmers had a problem, they would have to change the files to view it in their favourite layout. But because we use tabs, these programmers can simply set the tab width to a different value, and without changing the files it looks good for both programmers!

To indent properly with indent, issue this command:

$ indent --line-length 100 --k-and-r-style --tab-size 4 \
-bbo --ignore-newlines bluefishcode.c

Comment all public functions like it is done in bf_lib.c and gtk_easy.c (javadoc style, with some small differences), this can be used to create a function reference.

5. Options in the Images Tab
Home | ToC
 2. Naming