Well, I saw that, but really only got into it with the white and blue of DOS EDIT. Now, this all crazy coloring scheme is killing me though and all I was wondering is what you "pros" have set. I really don't see a value in highlighting library calls,since although defined by the standard are technically extensions to the language in the pure sense. I do see a teaching an "glance debugging" value in the VS default red - green - blue coloring scheme.Originally Posted by Salem
Warning: Some or all of my posted code may be non-standard and as such should not be used and in no case looked at.
Over the years I've been reducing more and more the scope and intensity of my code coloring scheme. Today it mostly boils down to keywords, user-defined objects and strings (I don't even color code symbols anymore). Each live on a different color, but always washed out colors with little visual impact. Admittedly because of the rules and semantics of certain programming language I may feel inclined to add a few elements to that short list. On C# for instance, it could be useful to separate classes from structs so you know exactly what kind of memory management the object you are working with uses.
Overall though I've been finding more value in less color scheming. I do still believe in it though. Make no mistake. But I just think that, at least for me, it works best as subliminal hint system and as an anti-bug precautionary measure. And I'm not anymore after the aesthetics.
Also, very recently I finally dropped the black background for good. I couldn't find a justification for it anymore. Non emissive, non flick, LCD screens just don't make white so tiring to the eyes anymore. But also, with a black background is harder to go for a suave color scheme: Black background tends to increase contrast with the overall text color, which is a fatigue factor in itself (although, of course, not so tiring as white was on CRT screens). At the same time it reduces the contrast between similar colors, making it harder to produce suave color schemes without increasing contrast with the background. White background (or slightly grey, as I personally use it) makes it much easier to produce text that stands out, that is clear, and that doesn't tire your eyes or brain.
Or at least that's how it has been working for me.
Last edited by Mario F.; 09-28-2011 at 06:42 AM.
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
Y'know what... I often find mistakes because something is "the wrong color"... Spelling, open ended quotes, etc. I won't say I couldn't do without it, but syntax highlighting has been a real help. The value in highlighting library calls is you can see your typos when they fail to color coordinate with Quzah's latest dance ensemble.
I just have been using the intelli-sense feature in the IDE to quickly identify the typos and mismatched braces / arguments. I can see the value in it for those who don't like that feature / don't use an IDE with it.
LOL....he has become quite dazzling lately. Are we invited to your "coming out" party quzah?
Warning: Some or all of my posted code may be non-standard and as such should not be used and in no case looked at.
Just, Please... no show tunes.
Yeah like I'd waste coming out on a bunch of ugly old programmers.
Quzah.
Hope is the first step on the road to disappointment.
Careful, my friend... I resemble that characterization!
