Path: utzoo!attcan!uunet!lll-winken!csd4.milw.wisc.edu!cs.utexas.edu!tut.cis.ohio-state.edu!bloom-beacon!STONY-BROOK.SCRC.SYMBOLICS.COM!MMcM
From: MMcM@STONY-BROOK.SCRC.SYMBOLICS.COM (Mike McMahon)
Newsgroups: comp.windows.x
Subject: Event-driven
Message-ID: <19890625211758.5.MMCM@EUPHRATES.SCRC.Symbolics.COM>
Date: 25 Jun 89 21:17:00 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 13

All X *clients* must be event driven.  That does not mean all programs.
Application programs, I think, strive for the highest level of
abstraction that they can get away with.  Part of them can be
declarative rather than procedural, even.  That is what
direct-manipulation interface layout design tools are all about.

The missing link is an application program interface that takes care of
the event-driven bookkeeping associated with the application's semantics
and how it represents them in the interface.

A hopeful interpretation of the separate devolution discussion might be
that such things are on the way, but just a little too immature or not
well enough known.