Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!ames!ncar!boulder!stan!garya!garya
From: garya@garya.Solbourne.COM (Gary Aitken)
Newsgroups: comp.windows.x
Subject: Re: Reverse Engineering to a User Interface Devl Environment
Message-ID: <1989Dec4.232458.8167@Solbourne.COM>
Date: 4 Dec 89 23:24:58 GMT
Sender: news@Solbourne.COM
Organization: Solbourne Computer, Inc.
Lines: 19

We have a crude approach which hasn't really been exercised much,
but it involves a flag you can give any application built with our
toolkit which, upon termination, causes the toolkit to spit out the
appropriate code to set up the application from the prototyper output.

So...  you start up the application with the dump proto config flag on
       rip out all the code which builds the object tree
       insert a call to build the object tree from the proto output
You're supposed to be done.

I think the principle is sound, and it works in the few test cases I've done.

You'd have to modify the toolkit so objects know about prototyper output for
this to work, unless your toolkit already knows about it.
--
Gary Aitken

Solbourne Computer Inc.    ARPA: garya@Solbourne.COM
Longmont, CO               UUCP: !{boulder,nbires,sun}!stan!garya