🚀 go-pugleaf

In article <13489@cbmvax.commodore.com> dale@cbmvax (Dale Luck - Amiga) writes:
> Most X implementations do support SMARTREFRESH like capabilities.
  ^^^^              vvvvvvvvvvvvvvvvvv           ^^^^   <--- important words
> MIT only says you can't depend on it being there if you want your
> product to be completely transportable to all other servers.

Or even reliably on a given server, since it is legal for any server to
ignore the backing-store hint if it starts getting low on RAM.

SO, your program has to redundantly include all the simple-refresh-style
code to handle expose events anyway. And that is really dumb: a window
should be able to be treated as a virtual screen.

Expecting a program to handle its own expose events is like expecting
it to handle its own page faults. It's a nice option to have available,
but it sure adds a lot of un-needed complexity.

Expecting a program to handle its own menus is like expecting it to handle
erase and kill. Important to have available, but do you want to put all
that code in "cat"? X requires this as well.
-- 
Peter da Silva.   `-_-'
<peter@sugar.hackercorp.com>.