
A couple of days ago Ethan Schoonover released Solarized, a color palette designed for use with terminal and gui applications. Over the last 6 months or so I have been using Notepad++ more and more for my daily coding. The default theme is just to harsh and I have been using the Bespin theme for some time now. While this is a really well designed theme, I always felt that there are some aspects of it that I just did not like but, could never quite pin point it.
When I read about Solarized, I was very exited. Having switched from the default Notepad++ theme to Bespin, I know the difference a good theme can make in terms of the strain placed on your eyes when you spend countless hours staring at the screen. Solarized currently has formats for Vim, Mutt, Xresources, iTerm2, OS X Terminal.app and color palettes for PhotoShop, Apple Color Picker and Gimp.
Unfortunately no support for Notepad++ yet but, on the site for Solarized, Ethan goes into detail about how it was designed and how to use the various colors in the palette. With this, I decided to jump right in and create a theme for Notepad++ using the guidelines and color palette from Solarized.
Below is a screen shot of the Solarize theme displaying a JavaScript file in Notepad++

From the screen shot you can see that it has a soft, low contrast look with the important parts of the interface and code clearly standing out from the rest. I have used this for a while now and find it a joy to use. Currently I have covered the following languages:
- Java
- SQL
- PHP
- HTML
- JavaScript
- CSS
- C
- XML
- Properties File
- Python
There are surely tweaks that can be made and support for more languages will be added. The other aspect of Solarized is that there is the dark palette, that you see here, and then a light palette. Currently I have only completed the dark theme and will be adding a Solarize Light theme soon.
UPDATE: Applied fix for background colors if you do not use a global override.
You can currently grab the theme from my fork on Github, which will hopefully be pulled into the master soon, fork it, improve on it or just send me your thoughts and suggestions on Github or here in the comments. Looking forward to hearing everyone’s thoughts.
