Bug 270813

Summary:	please ship a usable accesibility colour scheme
Product:	[Applications] kdevelop	Reporter:	Alin M Elena <alinm.elena>
Component:	general	Assignee:	kdevelop-bugs-null
Status:	RESOLVED DUPLICATE
Severity:	wishlist
Priority:	NOR
Version First Reported In:	git master
Target Milestone:	4.2.0
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	snapshot

Description Alin M Elena 2011-04-13 10:13:06 UTC

Version:           git master (using Devel) 
OS:                Linux

Hi there,
I am using kdevelop using for application appearance oxygen as a style and zion reversed for colours from kde accessibility package.

Some elements from kdevelop unfortunately crash with the theme making it unreadable...
I could fix myself some pretty easy, adjusting the colours for the editor, but I still have the issue with the tooltip
which seems totally washout.

It would be great if a consistent usable theme for accessibility issues can be shiped.

Alin

Reproducible: Didn't try




OS: Linux (x86_64) release 2.6.38-27-desktop
Compiler: gcc

Comment 1 Milian Wolff 2011-04-13 22:12:09 UTC

please show a screenshot of how it looks like in comparison to your usual theme so we get an idea on what to work on

Comment 2 Alin M Elena 2011-04-13 22:57:05 UTC

Created attachment 58929 [details]
snapshot

Comment 3 Alin M Elena 2011-04-13 23:00:36 UTC

you can see the whiteish background for the tooltip.. .which makes things difficult to read

the same for the doxygen comments (dark blue) which I could not find a way to customize the colour.

Alin

Comment 4 Milian Wolff 2011-04-15 11:46:52 UTC

ah ok. how does this work in html browsers for you? as the tooltip can embed arbitrary HTML we/I decided against using the system color scheme here. Most websites simply hardcode white as background (or expect the browser to have a white background by default), and become unusable when this is not the case...

Probably we just need to follow the suggestions in 270813 to make it somehow configurable...

*** This bug has been marked as a duplicate of bug 257378 ***