"sends mostly the same sized two messages sent every mouse move. Modeled after
TAvatarUser >> laserControl:redButton: Together, these two messages are 302
bytes over the wire. Moving the mouse constantly, from my experiment, sends
60-70 messages per second, so this update happens about 32 times per second,
for an expected total of 9664 bytes per second sent due to mouse updates"

"Because waking up more often than 30 times per second seems to be unreliable
on my VM, I send 8 messages per tick, and should be called about 10 times per
second. This comes out to about the same data rate on my machine as a regular
mouse drag update, after scheduling overhead. See
http://bugs.squeak.org/view.php?id=7652"

"the message names use annoying aLt CaPs because they need to be the same
string length as the original commands sent on mouse move (to preserve wire
size), but I wanted to make it clear they are dummy methods, both in the
debugger and the statistics logs"