Remove gsd_* default styles, use named styles instead.

Note: this relies on filetypes.common being installed.
Add load_style_entries(), which makes style initialization
simpler, used in styleset_c_like_init().



git-svn-id: https://geany.svn.sourceforge.net/svnroot/geany/trunk@3873 ea778897-0a13-0410-b9d1-a72fbfd435f5

ChangeLog

+2009-06-18  Nick Treleaven  <nick(dot)treleaven(at)btinternet(dot)com>
+
+ * src/highlighting.c, README.Packagers, HACKING:
+   Remove gsd_* default styles, use named styles instead.
+   Note: this relies on filetypes.common being installed.
+   Add load_style_entries(), which makes style initialization
+   simpler, used in styleset_c_like_init().
+
+
 2009-06-17  Enrico Tröger  <enrico(dot)troeger(at)uvena(dot)de>
 
  * src/win32.c:

HACKING

@@ -236,19 +236,23 @@ the following things:
 1. Write styleset_foo_init() to setup default 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_asm_init().
+   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_asm().
+   is created. Again you could copy and adapt a function like
+   styleset_tcl().
 3. In highlighting_init_styles(), add
    ``init_styleset_case(GEANY_FILETYPES_FOO, foo);``.
 4. In highlighting_set_styles(), add
    ``styleset_case(GEANY_FILETYPES_FOO, foo);``.
 
-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.
-
 Error message parsing
 ^^^^^^^^^^^^^^^^^^^^^
 New-style error message parsing is done with an extended GNU-style regex

README.Packagers

@@ -26,8 +26,9 @@ images. But if you do so, please include at least the text form of the
 manual.
 What you shouldn't skip in your package: the filetype.* files in the
 data/ subdirectory, these files are important. If they are missing,
-Geany has still a fallback mechanism for syntax highlighting but several
-other features for certain filetypes will fail (mainly build support).
+Geany still has a fallback mechanism for syntax highlighting (if
+filetypes.common is installed) but several other features for certain
+filetypes will fail (mainly build support).
 
 
 Testing your package