[interfacekit] Re: Course of action for BScrollBar implementation

I agree with Ingo. I have quite a number of reasons why I think we should at 
least hold off on the server-side scrollbar. A special case adds time. I 
don't want to sound indignant or anything (please don't take it as such), but 
right now, Gabe and I have more than enough to do on the server without 
adding to its complexity in another way. BScrollbar is also the only class 
AFAIK which is handled by the server in any way except for displaying and 
allocation. 

Processor power is also quite cheap right now. While I do want the 
possibility of running OBOS on an old166, I doubt that it will be the norm 
with the way that Micro$oft's bloatware is forcing higher hardware 
requirements. I doubt that the additional messaging overhead will be 
significant, but if it is, it will likely be easier to go from client to 
server than the other way around. 

Minor customization is acceptable provided that it does not prove a 
hinderance to the user. Alan made a good point in saying that the user should 
not be restricted to a particular font, font size, or set of colors. One of 
Microsoft's good ideas (there are so few!) was high contrast color schemes 
for those who have visual disabilities of some sort. Localization support 
will require different fonts, such as for Hebrew and other Middle East 
languages or for C/J/K. As long as we are conservative about it, there 
shouldn't be many problems.

--DW

Other related posts: