[SVN] Code Themes (was Re: Indenting style in snippets)

Allan Odgaard allan at macromates.com
Sat Apr 16 06:26:02 UTC 2005


On Apr 13, 2005, at 10:34, Mats Persson wrote:

>>> ... create/edit [TM] style sheets (which btw desperately need a 
>>> better name)...
>> But seriously, what about "code theme"?
> I would strongly, but humbly suggest "Style Themes", as "it does what 
> it says on the tin" so to speak.
>
> Having 2 or 4 spaces per tab, is a style issue rather than a code 
> issue.
> Having all functions/strings/whatever highlighted red/blue/whatever is 
> a style issue rather than a code issue.

There are however a few things which I don't think are style issues. 
What I've done so far is to name individual files for 'settings' 
(placed in ~/Library/Application Support/TextMate/Settings) and then a 
collection of 'settings' is the theme. I have committed two settings 
files as examples.

There is the “Basic settings” which isn't really about style (except 
maybe the incr. indent patterns) and then there is the “Grey 
background” which is about color and font styles.

The Amiga theme (i.e. grey background) then consists of both the Basic 
settings and the Grey background. A DOS theme (i.e. black background ;) 
) would most likely re-use the Basic settings, but contain a new Black 
background settings file.

The View menu has a Theme submenu from where the user can select the 
active theme and also Edit Themes…, this brings up the theme editor 
which can edit both the themes (i.e. just which settings files are 
enabled for a given theme) and the actual settings file -- so the word 
'theme' is the one dominating the UI, and most users will probably see 
the theme editor as making changes to a theme when they edit a settings 
file (which they sort of also are, but that settings file could be 
shared among several themes).

I still have a few unresolved issues, though mainly in relation to the 
distribution of themes/settings and/or bundles that have new 
“requirements” with regard to styling. But this can probably be handled 
as requirements/desires become more evident.




More information about the textmate-dev mailing list