SF.net SVN: geany:[4255] trunk/HACKING

[ntrel at users.sourceforge.net]

Revision: 4255
          http://geany.svn.sourceforge.net/geany/?rev=4255&view=rev
Author:   ntrel
Date:     2009-09-28 15:28:25 +0000 (Mon, 28 Sep 2009)

Log Message:
-----------
Update notes about data/filetypes.foo configuration file [styling] section.

Modified Paths:
--------------
    trunk/HACKING

Modified: trunk/HACKING
===================================================================
--- trunk/HACKING	2009-09-28 15:17:16 UTC (rev 4254)
+++ trunk/HACKING	2009-09-28 15:28:25 UTC (rev 4255)
@@ -302,18 +302,11 @@
 For syntax highlighting, you will need to edit highlighting.c and add
 the following things:
 
-1. Write styleset_foo_init() to setup default styles and load style
+1. Write styleset_foo_init() to setup lexer styles and load style
    settings from the filetypes.foo configuration file. You should probably
    start by copying and adapting another filetype's initialization, such
    as styleset_tcl_init(). Another way is to use load_style_entries()
    to make style initialization simpler - see styleset_c_like_init().
-
-.. note::
-    Please try to make your styles fit in with the other filetypes' default
-    colors, and to use named styles where possible. Filetypes that share a
-    lexer should have the same colors. Normally, styles should leave the
-    background color empty to match the default color.
-
 2. Write styleset_foo() to apply styles when a new scintilla widget
    is created. Again you could copy and adapt a function like
    styleset_tcl().
@@ -321,7 +314,16 @@
    ``init_styleset_case(GEANY_FILETYPES_FOO, styleset_foo_init);``.
 4. In highlighting_set_styles(), add
    ``styleset_case(GEANY_FILETYPES_FOO, styleset_foo);``.
+5. Write data/filetypes.foo configuration file [styling] section. See
+   the manual and see data/filetypes.d for a named style example.
 
+.. note::
+    Please try to make your styles fit in with the other filetypes'
+    default colors, and to use named styles where possible (e.g.
+    "commentline=comment"). Filetypes that share a lexer should have
+    the same colors. If not using named styles, leave the background color
+    empty to match the default color.
+
 Error message parsing
 ^^^^^^^^^^^^^^^^^^^^^
 New-style error message parsing is done with an extended GNU-style regex


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.