Good job. Perfect fit for a programmer with slight designer tendencies :)
Found a new theme to use, changed a few colors and got a result I was happy with.
However, probably not your fault, after changing one background color, and resetting it to opaque, the theme is no longer valid. Any idea how I can get a more descriptive error message besides: Error loading colour scheme Packages/Color Scheme - Default/Notebook.tmtheme: Unrecognised plist element key
This is really excellent. It's nice even just to use it to compare a few themes I like but could never really tell what the difference was between them, and hence why I liked one over the other.
I was reading about this the other day, I cloned it locally but never got around to changing it. I think the biggest problem is the rendering engine. Some magic has to happen to match the scope name to the sample code, that can't be easy to do, but you've managed it, how does it work with complex scopes etc?
Hopefully I'll get the chance to try it when it goes back up. Editing the theme manually kinda sucks.
Currently, in Sublime Text 2, when I edit a theme and saves, it starts to add a lot of weird redundant codes inside the theme file. I'm not sure whether it's a bug or I shouldn't edit the theme file live.
With all the Sublime/Textmate theme tools lately, where are the gvim <--> Sublime Text conversion tools. There are a few one-way options, but none that work both ways. Are there significant technical challenges in pulling this off, or is it a matter of interest in the tool?
Very nice. It would be useful to have light and dark background themes indicated somehow in the list, possibly with some way to filter them, or even just splitting the list in two sections.
Why do people use color schemes when programming, is it cause it looks cool, do they think it makes them more productive, is it cause some people insist on it makes it easier to read code? None of these statements have been proved as far I know, so why?
Some people (or even a lot of people, I don't know) think it helps them read code if different syntactic elements have different visual appearances.
You seem to argue that they "shouldn't" feel that, since it hasn't been "proved".
Sure, you can do a study and somehow try to measure if some dimension of understanding is more easily acquired with or without syntax highlighting, but what would be the point? To then force those who like it, to not use it anymore? Why?
In other words, if you like Cubist art, or hamburgers, or tofu, do you require all of those to be somehow "proven" before you're allowed to like them?
If you are spending a significant portion of your work day staring at a code editor, surely optimising it somewhat is worth it.
I only code a little in my free time, but have a dark background makes it easier to stare at the screen, and having, say, variables a particular colour makes them stand out when scanning through code.
It's like a professional cook having all his kitchen utensils laid out in a particular manner that's efficient for his work routine. I'm sure there's plenty other analogies from different professions you could apply.
Very few things have been "proven" in the sense you are talking about. People still have to make judgments about them anyway. By and large, most developers seem to have concluded that syntax highlighting helps them in some way.
Possible reasons why:
1. Distinguishing different types of operators/primitives/objects from each other at a glance.
2. Aesthetic enjoyment.
3. An appropriate color scheme may be "easier on the eyes".
I began using a darker background in my text editor last year due to a sudden increase of eye floaters that was distracting when I stared at bright backgrounds. While now I can ignore them on my own most of the time, I still prefer to use darker themes when applicable.
Is the message I receive using Chrome 25.