Path: utzoo!attcan!utgpu!watmath!iuvax!mailrus!uflorida!beach.cis.ufl.edu!mfi
From: mfi@beach.cis.ufl.edu (Mark Interrante)
Newsgroups: comp.sys.mac
Subject: Re: Real Multifinder
Message-ID: <20748@uflorida.cis.ufl.EDU>
Date: 17 Aug 89 11:56:56 GMT
References: <46100321@uxe.cso.uiuc.edu> <1989Aug15.001507.14552@sj.ate.slb.com> <24626@iuvax.cs.indiana.edu> <3576@internal.Apple.COM> <1989Aug16.175351.24310@sj.ate.slb.com>
Reply-To: mfi@beach.cis.ufl.edu ()
Organization: UF CIS Department
Lines: 21

In article <1989Aug16.175351.24310@sj.ate.slb.com> enk@slcs.slb.com (Edan Kabatchnik) writes:
>     Granted, (parts of) UNIX should be done away with.  But, there is a
>superior form to the main event loop: callbacks (found in X and Xerox
>Artificial Intelligence Workstations from which the Macintosh developed its
>user interface.)  Instead of having to dispatch on every possible event in the
>main event loop, one establishes a hook that is automatically called when an
>event takes place.
>
>	Example: when creating a menu, each item that can be selected
>	in the menu is given the address of the function which should
>	be called when that item is selected.

This is exactly the method used in Apples CommonLISP.  The definitiion
of a menu item consists of its name and the function it calls.  I find
this a very intuitive way to implement menus and dialogboxes.  

-----------------------------------------------------------------------------
Mark Interrante   		  Software Engineering Research Center
mfi@beach.cis.ufl.edu		  CIS Department, University of Florida 32611
-----------------------------------------------------------------------------
"X is just raster-op on wheels" - Bill Joy, January 1987