Bug 148276 - Support for a dark color schema
Summary: Support for a dark color schema
Status: RESOLVED FIXED
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: Rafał Rzepecki
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-28 00:16 UTC by greatbunzinni
Modified: 2008-07-30 21:24 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description greatbunzinni 2007-07-28 00:16:37 UTC
Version:            (using KDE KDE 3.5.7)
Installed from:    Ubuntu RPMs

A dark colour schema (black background, dark fonts) is easier on the eyes and therefore makes the whole experience of spending countless hours in front of a monitor a whole lot better. It would be nice if kate implemented such a schema.

I've tweaked a custom schema of my own. It isn't perfect but does the job. I could post it here if anyone finds it to be of some use.
Comment 1 Philip Rodrigues 2007-07-29 22:32:07 UTC
Patches are always welcomed, so yes, please attach your schema. (I can't guarantee that the kate developers will include it, but they're more likely to include an existing one than create a new schema from scratch :-)
Comment 2 Matthew Woehlke 2007-07-30 18:25:03 UTC
This won't be as needed in KDE4 since kate will by default use the system color scheme (for *everything*, i.e. bugs like Bug 143606 will be fixed), so if you use a dark system color scheme, kate will also use dark colors.
Comment 3 greatbunzinni 2007-07-30 21:40:47 UTC
That sounds a bit as a step backwards. The support for custom color schemes is one of kate's strong points. I don't believe that the idea to tweak the entire system colour scheme just to fulfill a single purpose will be gladly accepted by anyone.

About the colour scheme, the following was extracted from my ~/.kde/share/config/kateschemarc

<schema>
[kdevelop - dark]
Color Background=0,0,0
Color Highlighted Bracket=216,0,4
Color Highlighted Line=1,16,0
Color Icon Bar=0,0,0
Color Line Number=85,85,85
Color MarkType1=0,0,255
Color MarkType2=255,0,0
Color MarkType3=255,255,0
Color MarkType4=255,0,255
Color MarkType5=160,160,164
Color MarkType6=0,255,0
Color MarkType7=255,0,0
Color Selection=96,96,96
Color Tab Marker=0,38,255
Color Word Wrap Marker=109,114,124
Font=Monospace,8,-1,5,50,0,0,0,0,0
</schema>
Comment 4 Matthew Woehlke 2007-07-31 17:40:36 UTC
I think you missed the word "default" in my last comment. You can still make your own schemes; nothing has changed there. What *has* changed is that if (on a pristine system) you change your system color scheme to something dark, kate will fully use your system color scheme, instead of something unhelpful like dark red (hard-coded) on dark gray (from the system color scheme).

IOW, every system color scheme in KDE4 will also (in a way) be a kate color scheme. So there is less reason to have a bunch of kate-only color schemes.

Now, that doesn't me we *shouldn't* consider offering a selection of color schemes in kate at some point. :-) But I'm not going to make that call one way or another.
Comment 5 Matthew Woehlke 2008-04-01 23:44:08 UTC
Since I can see that this works nicely with e.g. Obsidian Coast in KDE4, I think this can be closed now.
Comment 6 Rafał Rzepecki 2008-07-30 17:53:24 UTC
Reopening since the colorful code folding marks work really awfully on a dark schema.
Comment 7 Matthew Woehlke 2008-07-30 19:57:19 UTC
> Reopening since the colorful code folding marks work really awfully on a dark schema.

Please fix bug 167774 (just created) instead :-). This is different enough to deserve its own bug IMO.
Comment 8 Rafał Rzepecki 2008-07-30 21:24:16 UTC
True, but it's not necessary for folding colors to be configurable to work with a dark scheme -- they just need to be alpha blended. Please reopen if you kindly agree.

Configurability is of course a valid and important bug, too; but alpha-blending can be done without touching strings and UI, so I think it's useful to fix separately.