Man 1 ch12s02

From Bluefish Wiki
Revision as of 16:51, 19 August 2009 by Fal7i (talk | contribs) (Created page with '__NOTOC__ __NOEDITSECTION__ {{Man1top |lang=en |rev=1.0.6 |Title=2. Naming |prev=Man 1 ch12 |Subtitle=Chapter XII. Development guidelines |next=Man 1 ch12s03 }} ==…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


Please consider to upgrade to Bluefish 2!

Please consider to edit the Manual 2!

How To edit the Wiki Manual
{{#if:2. Naming|
2. Naming
}}
Prev }}
Chapter XII. Development guidelines
}}
 Next
}}

2. Naming

For non-local functions, the name should preferably include a prefix that shows the part of bluefish it is used for. There are, furthermore, many often used abbreviations in the bluefish code, such as:

Abbreviations used in the Bluefish code

doc

A function for handling a specific document

bfwin

A function for handling a specific Bluefish window

cb

Callback, a function called after a button click or some other event

lcb

Local callback, a function called after an event, only used in this .c file

Here are such function names that show where they are from, what they handle, and/or what they do

Examples of function names in Bluefish

bmark_set_for_doc

Bookmark code, sets bookmarks for a document

spell_check_cb

Spell check code, this is a callback function (for a button)

project_open_from_file

Project code, opens a new project from a given file name


Prev }}
Up
}}
 Next
}}
Chapter XII. Development guidelines}}
Home | ToC
 3. Declaring procedures
}}