Re: Control center and capplet merging

[Bill Haneman <Bill Haneman Sun COM>]

I think that trying to deal with theme-related (i.e. visual style) 
accessibility issues in the Accessibility capplet is a bad idea.  M$ did 
it in XP but let's not copy that bad example, they ended up with two 
different 'Theme' dialogs that are quite disjoint and confusing.  Also - 
big surprise - the 'Accessibility' one is the uglier, more confusing one.

I agree that Font and Theme belong together - instead of fragmenting the 
'Display' capplets, why not try to find a better combination of 
visual-attribute-related settings?  The merge idea seems good to me, but 
Font and Theme seem like ideal candidates for such a merger.

regards

Bill

> On 27 Jun 2005, at 10:07, Luca Ferretti wrote:
>
>  
>
> > I did have no time to add comment on wiki page or open relevant bugs,
> > but IMHO merging Theme and Fonts capplets is not a so good idea.
> >
> >    
> One advantage it would have would be for accessibility... it's pretty  
> common to want to change both together if you need a High Contrast  
> Large Print theme, for example.  (And personally, the first thing I  
> do when I install a Linux machine is to change both the font and the  
> theme, and then I pretty much never touch either of them again, so  
> I've always wanted them in the same dialog anyway...)
>
> We argued this to death a few years ago, and the current loose  
> coupling between the two capplets was the compromise.  But IMHO it's  
> never really worked very well, because (for example) you can't easily  
> revert any font changes you made using the 'Apply Font' button in the  
> Theme dialog, partly because there's no Revert button, and partly  
> because if you work out that you have to open the Font dialog to do  
> it, you've no way of knowing what your previous font setting was.
>
> I see that a separate Accessibility capplet is proposed as well,  
> though, so perhaps this wouldn't be an issue any more anyway,  
> depending on its precise contents.  (Although I'm not sure if  
> capplets that affect values in other capplets are such a great idea  
> either, but that's probably a separate argument...)
>
> Cheeri,
> Calum.
>
>