[interfacekit] Re: Course of action for BScrollBar implementation

I disagree with the statement that people should not be able to change
fonts and colors.

I can't stand the standard black text on white. White backgrounds are just
too bright.

Also, if I have a 15" laptop monitor that does 1600x1200, I should not be
subject to an 8 pt font size because that's what looks good on someone who
has a 19" CRT and runs it at 1024x768.

It's always at least been possible to change the font with BeOS, so going
backwards there would seem like it's against the OpenBeOS charter.

Alan


> On 2003-01-16 at 16:40:25 [+0100], you wrote:
>
>> As for customization and overriding Draw() of BScrollBar. I don't think
>> developers should change the look of controls (and not only because I
>> spent
>> hours to get the drawing code good ^_^). People should stick with the
>> default look, not try to brand their application by making it look
>> completely out of place. I think the direction Apple took for the MacOSX
>> gui
>> is perfect, for users and developers. They have clear guidelines so that
>> apps look consistent, and once you can use one, you can use them all,
>> and
>> they all fit nicely together. They don't let users change colors or
>> fonts,
>> which makes it much easier for developers. I know theming is popular,
>> but I
>> don't think it's something that is necesary/usefull, it doesn't make
>> users
>> work faster (especially not if you they tweaking everything the whole
>> time
>> or browsing for themes), and developer resources are much better spend
>> elsewhere.
>
>
> Here I completely agree with Marc.
> If we want to drop server-side scrolling just to make possible for
> developers
> to customize the appearance of scrollbars, I don't think we are doing the
> right thing.
>
> I don't think we want to have a million different GUI controls which do
> the
> same thing.
>
>

Other related posts: