[Geany-devel] Porting themes (Was: Re: Request: multithreaded tag generation?)

[Matthew Brush]

On 01/03/2012 06:18 AM, Harold Aling wrote:
> On Tue, Jan 3, 2012 at 15:16, Matthew Brush<mbrush at codebrainz.ca>  wrote:
>> On 01/03/2012 05:50 AM, Harold Aling wrote:
>>>
>>> On Tue, Jan 3, 2012 at 13:44, Matthew Brush<mbrush at codebrainz.ca>    wrote:
>>>>
>>>> I already ported all of the existing old-style color schemes to work with
>>>> the new filedefs, see the geany-themes[1] project on Github to get them.
>>>> Some might need a little tweaking, but should for the most part be quite
>>>> similar to the original ones.
>>>
>>>
>>> Nice!
>>>
>>> Unfortunately, the 'dark' scheme needs some serious tweaking to make
>>> it look like I'm used to (it's very brownish dull right now), but I
>>> guess some well-placed copy/paste actions will solve that for me! ;)
>>>
>>> Armed with a screenshot of the old scheme, dark.conf, an old
>>> filetypes.* file and the documentation[1] I'll try to recreate the old
>>> dark theme.
>>>
>>
>> It'd be great if you could send me your changes after so I could update the
>> one in geany-themes!
>
> I will. Unfortunately, it's quite a trial and error process as the
> documentation isn't very helpful in where a definition is used. For
> example: 'string_1', 'keyword_3', and lots of others aren't mentioned
> anywhere.
>
> It also would have been nice if there's a old>  new name list.
>

See the [styling] section in each filedef to see where they map to the 
old language-specific styles. For example, here's an extract of the PHP 
style mappings from filetypes.xml::

   php_default=default
   php_simplestring=string_1
   php_hstring=string_1
   php_number=number_1
   php_word=keyword_1
   php_variable=preprocessor
   php_comment=comment
   php_commentline=comment
   php_operator=operator
   php_hstring_variable=string_2
   php_complex_variable=keyword_2

The only reason there's ones with like keyword_3 and keyword_4 is that 
some languages have that many sets of different keywords, and if they 
all mapped to keyword_1 in the filedefs, it'd mean you'd have to edit 
the filedefs to change the scheme. This way though, you can just change 
the style for keyword_4 to be a different one right in the color 
schemes, for example, in the color scheme::

   keyword_4=keyword_1

Changes to::

   keyword_4=0xff0000;0x0000ff;false;true

And then whatever languages have a 4th set of keywords would have them 
highlighted differently from the other sets.

Cheers,
Matthew Brush