Chris, I'd love to see your do-it to change the Shout colors to ones you find satisfying. A big problem is when you are in the middle of modifying a method. As you type, it does not make sense to Shout, and the next 20 lines turn bright red. That is annoying. I feel like saying, "I'm not done yet. Don't get on my case!". Perhaps if there are more than 2 lines in red after the insertion point, just turn the rest of the method black. That would keep things much calmer. The lack of any other colors would signal that something is not complete.
--Ted.
At 5:36 PM -0600 2/23/13, Chris Muller wrote:
Wow, I'm surprised -- the human eye discerns color contrast much more easily than patterns. While I don't care for the standard Shout colors, by changing them to be more intuitive and constrasting, particularly for longer methods, the colors _really_ enhance the readability. For example, I'm able to instantly see references to instVars with just a glance because they're gold (dark yellow); or references to self and super because they're bolded, which quickly tells me whether this is a "utility" method. Further, by making comments a light-gray, they are just barely visible, so they're not cluttering the code, but still easily readable if I decide to focus on them for a clarification. Kind of like simply changing eye-focus "reveals" different aspects of the code -- what a powerful "gesture"!..