[interfacekit] Re: Course of action for BScrollBar implementation

>> It also occurs to me that allowing something as basic as the 
>> scrollbar 
>> to be modified from one app to the next could contribute to an 
>> inconsistent UI.
>
>Absolutely. Unless unevitable, applications should stick to the 
>standard GUI elements. It will be our task for R2 to improve the 
>existent gadgets and add new ones, so that this case becomes very rare.
>
>CU, Ingo
I agree. It totally screws me up when people, for example, redo all the 
controls for their application just for branding and so it supposedly looks 
cool and stands out from the pack, like, say, RealPlayer One. Unfortunately, 
it is possible for people to do that under BeOS as it stands. It is already 
possible to completely to reskin BeOS, albeit with some classes requiring a 
little more hacking than others. Take a look at CL-Amp. Jace Cavacini (of 
BeUnited) and I have been working on GUI guidelines for the open source BeOS 
projects. If we ensure that people are aware of them and they do the right 
thing and follow them, funny things like what happens in Windows shouldn't 
happen that much.

--DW

Other related posts: