" . . . . . . . Model Top Woman. . "

" The actual implementation of the controller object can vary quite a bit, but the idea of an object to 'transform' events to changes in data and execution of methods is the essence of this pattern. What does "event driven" mean? Was there ever an application which did not respond to user events. . ? Just because an application responds to events does not mean it is "event driven". Event driven means it spends much of its time waiting for an event and then takes action if and when an event occurs. Contrast this with some programs that do not respond to events at all, but simply do their job and terminate. For example, an operating system command to display the current time. Foot Model Woman It displays the time and is done; it does not wait for events. For more information, see: Event-driven_programming Implementations The pattern was first described in 1979 by Trygve Reenskaug, then working on Smalltalk at Xerox research labs. "