> as an example Uwe wants to kill graphics background color because he
> has no idea what it does, which is just irresponsible. in such case
> you need to associate it with one fixed color, so all my png images
> with alpha channel are going to have fixed background. if it merges
> with the foreground then what?

Thanks for this info. As this is not yet documented should we add this to the Customization manual or to sec. C.1.3 "Colors" of the UserGuide?

> moreover if you dont use your own styles its hard to imagine all the
> consequences of some colors settings. e.g. i'm not able to read
> branch-inset 'outdated' in customization manual because - well nobody
> got the idea that you can have black-bg grey-fg theme.

Hmm, I fear that we cannot avoid this with our current framework. We whould have to check what the current font and background color is used and then forbid this color in all color setting dialogs. I assume that this is impossible since we inherit Qt's color dialog and one cannot prevent that a user selects a certain color from the color-selector widget.

> so please be very careful of the consequences.

OK. But what should we do now?

I propose

- not to use the option "using system colors" by default. Users can activate it if they like
- remove the caption frame color
- remove math corners (The default is already the default background and is most probably never changed by users.) - added space markers, appendix marker and end of line marker can be removed and we use the current color value for it (the dark reddish one).
- new page and page break can be reduced to one color
- top/bottom line should be changed to black because these lines also appear
black in the output
- contact Stefan and reduce the macro colors

I agree with JMarc that we should try to reduce the colors.
To what points in my list do you agree?

regards Uwe

Reply via email to