Use new colors for passed and failed tests

[ccordoba12]

@jitseniesen, I think we could use:

1. A softer shade of red for failed tests. The current color is too strong for my eyes :-)
2. A stronger shade of green for passed tests. The current color seems to me too light for me.

@goanpeca, what do you think?

[goanpeca]

Agreed. But we should provide these colors from somewhere in spyder so that each plugin can rely on this.

[goanpeca]

We could have, danger warning information (at least)

[ccordoba12]

Right. We already have danger and warning colors defined for the find/replace widget (not exposed as global constants though), so we could use them here too.

[goanpeca]

Right. We already have danger and warning colors defined for the find/replace widget (not exposed as global constants though), so we could use them here too.

Yep something like that :-)

Since the idea was to use maybe breeze to define the new theme for spyder, we could base it from that:

From https://community.kde.org/KDE_Visual_Design_Group/HIG/IconDesign

[ccordoba12]

Good call! @jitseniesen, what do you think?

[jitseniesen]

Using the same colour throughout Spyder is obviously a good thing. The colours from breeze look quite okay. I will make some mock-ups and we can see.

[jitseniesen]

Currently, the colours are #C1FFBA, #FF0000 and #C5C5C5 (cool how github adds the small colour boxes!). This looks as follows (there are more passing than failing tests, since I expect this to happen in practice):

The find/replace widget uses #FF5050 for "regexp error" and #FFAF5A for "pattern not found". This is a paler red. If we use #FF5050 in the unittest widget, it looks as follows:

CodeEditor.error_color is used to indicate errors in the panel to the right of the editor and is set to #EA2B0E. This looks like:

The KDE icon colours for Breeze include #DA4453 (icon red) and #2ECC71 (icon green), which looks like:

Any suggestions? To me the second picture seems perhaps the most readable.

[ccordoba12]

To me the second picture seems perhaps the most readable.

Agreed. I think you should implement that.