[interfacekit] Re: Course of action for BScrollBar implementation

> I vote for `drop the server-side scrolling'.

The problem of not having server-side scrolling also becomes an issue when
we want to transmit GUIs across networks.  It is far better to have a
protocol for server-side drawing of everything.

The application, which is running on a remote system, would say "draw a
scroll bar", and the local app_server would draw the scroll bar and
transmit messages according to user interface.  If it were not server-side
scrolling, then the drawing instructions would have to travel the network
as well.  This goes for buttons and other GUI components as well.

Having all UI elements being done on the server-side means that
applications run over networks will be consistent on a particular system
(as opposed to potentially having different widgets depending on where
you're running it from), and if you have an API which allows for
modifications (to UI elements on a case-by-case in a particular
application), which are transmitted back to the app_server, then it would
also decrease the necessary bandwith and data throughput, because you
could transmit the necssary data at one shot, on loadup.

Isaac

Other related posts: