Uwe Stöhr wrote:
> So I'm still not happy that the option "using system colors" is now the 
> default. Many developers are currently in vacation - let's see what they 
> think about this.

while understanding JMarc point about inheriting system-wide colors, i'm more
on Uwe's side to let by default the background as it was. inheritance would
make some sense if there was some system system-wide color called 'background
for reading' for which is clear that ergonomic(=!white) setting is generally
used on the system and was properly thought about. imho the system-wide
'background' is used for semantically different things, thats why the problems.
its absurd to mimic office behaviour when every dev around acknowledges that
(implicit) white setting for longer sessions impair your eyes. 

but no hard opinions until users are able to keep their own color settings which
they use for years (i became accustomed to terminals so much that even my lyx 
looks
as the black-bg gray-fg session...), which leads me to the second discussed
point: please be very gentle about removing colors just because in _your_ eyes 
they have only little meaning. over-abundance of options should be fought
when the feature is introduced, having regression once you get accustomed to
some feature is much more frustrating...

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?
if you choose the same background color as i have for text background so i dont
see the border of the image(s) then what?

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. the fg inside branch inset is set on grey and
bg of branch inset is not document setting so all you see is nice grey
rectangle :) for similar reasons i'm forced to keep my own version of
stdinset.inc - some backgrounds can be cutomized and some foregrounds are fixed
for 'foreground' which you again recognize only when custom theme is used...
so please be very careful of the consequences.

pavel

Reply via email to