Hardcoded Colors in KDevelop

Matt Rogers mattr at kde.org
Thu Dec 21 01:16:36 UTC 2006

On Wednesday 20 December 2006 19:02, Andreas Pakulat wrote:
> Hi,
> Matthew Woelke started out on the quest to remove hard-coded colors
> within the KDevelop sources. I just did a quick thing on the debugger
> and went on to find any occurences for QColor in kdevelop. The outcome
> is really bad. There are quite some parts that use hardcoded colors for
> their Ui, namely:
> FileTreeView, integrated designer (quite many herer), ruby debugger and
> the cpp configuration widget.

I would prefer if we didn't touch the integrated designer. It's basically a 
copy of Qt 3's designer and I don't want to be messing around in there if it 
mostly works.

> Now, some of them like the filetreeview use many colors for special
> highlighting (in that case state of version controlled files) and I'm
> not sure how to make that work with the "limited" color roles we have in
> KDE3/Qt3.

Those colors are customizable in the file tree view. IIRC

> One way might be to use the blend() function Matthew implemented for the
> ProcessWidget, which if I understood correctly blends 1 color into
> another by a certain factor. That way we could just blend the custom
> colors into the standard text color (or button, background whatever) to
> a certain amount.
> But somebody with more knowledge about styles needs to speak up and
> "tell" what the proper way would be. I'm willing to do the coding part,
> I just need to know what I should do.
> In the meantime I'll see that the configuration widget for C++ is
> changed, it seems the colors are mainly used for highlighting purposes
> there, i.e. using red for errors.

And we should still keep using red there IMHO.

More information about the KDevelop-devel mailing list