Below is a table that lists the colors available as constants in SWT. Because these colors are frequently used in SWT development, I put this together as a quick color reference - all of the colors listed can be accessed by calling display.getSystemColor( SWT.COLOR NAME).

Much to my dismay, I couldn't find a rendered version like this anywhere in Eclipse's documentation; if you know of one, let me know by adding a comment.

In a previous job, I had a trainer for a CASE tool who gave me a phrase that has stuck with me for the past 15 years: "A fool with a tool is just a faster fool."  The truth of this is obvious on the surface, of course, but many times we developers don't see it happening to us as it happens - the onset is too gradual.  I am beginning to see an emergent anti-pattern, particularly among my less experienced colleagues, which has cropped up as a result of Eclipse usage - something I call "Squiggly-Driven Development". 

I do not have to be a melodramatic to say that Eclipse has taken the
Java development landscape by storm. Certainly during the last couple
of years Eclipse has captured the lion’s share of the Java IDE market.
Eclipse was designed from the outset to be a sort of universal tool
platform – an open, extensible integrated development environment - in
which vendors and individual tool writers could contribute various
pieces that would seamlessly integrate with other pieces. Along the way
came another thought – why not reuse the functionality provided by the
Eclipse IDE platform to create stand-alone end-user applications.

Once a project starts many programmers get into a “project rut” where we only deal with the technologies we really need to get the current battle over with. However, if we pull the camera back sometimes a plugin or utility appears that would help quite a bit. I recently had that experience and hopefully have something that could make your next project even better!

The Mylar Technology Project is a plugin for the Eclipse Development Environment thats main purpose is to keep the user focused on one task at a time. These tasks can be set by a project manager and shared to other developers before development begins or most likely created in real time while coding. Here is where the magic starts. Once the user activates a task, the plugin keeps track of what files are being manipulated and starts narrowing down the different Eclipse views so the user does not get distracted by other files that would currently be of no use to the current task. At this point the user may mark the file as important to the current task and Mylar will remember it for the duration of the current task. For example, some classes contain more methods than you would like to admit, but by using Mylar only those methods you are currently editing will appear in the outline view, package explorer,… With just a click the user can return to viewing all of the packages, files, and pure chaos that could be the current project’s real workspace. Do not fear, one more click will return to the focused task oriented view which will make the user a much more focused worker.