Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!uwm.edu!lll-winken!elroy.jpl.nasa.gov!jpl-devvax!david
From: david@jpl-devvax.JPL.NASA.GOV (David E. Smyth)
Newsgroups: comp.windows.x
Subject: Driving a User Interface From a File
Message-ID: <7064@jpl-devvax.JPL.NASA.GOV>
Date: 13 Feb 90 19:50:18 GMT
Reply-To: david@jpl-devvax.JPL.NASA.GOV (David E. Smyth)
Organization: Jet Propulsion Laboratory, Pasadena, CA
Lines: 20
References:

Why?  For regression testing, but also for "batch" processing
(oh no!), for defining macros, for feeding "commands" into
a user interface by a text selection...

Ideally, such a mechanism would work sorta like the "programming by
example" research done at Xerox about a decade ago (see Programming by
Example, Daniel C. Halbert, Xerox Office Systems Division for a 1984
description.  He wrote other internal memos as far back as 1980).  Or
Juno.

I.e., the user does something, and a file "magically" devlops which
mimics the user's actions.  This file is a script which can then
be read in by that application.  The syntax should support arguments to
be really useful.

My guess is this could be done with a hacked XtMainLoop.  Starting
and stopping the collection of events from the user, as well as the
parameterization bells-and-whistles, would be handled therein.

Ideas, anyone???