Newsgroups: rec.arts.int-fiction
From: matt@dekard.demon.co.uk (Matt Mower)
Path: nntp.gmd.de!news.rwth-aachen.de!uni-paderborn.de!golden-gate.owl.de!fu-berlin.de!zrz.TU-Berlin.DE!netmbx.de!Germany.EU.net!EU.net!news.sprintlink.net!cs.utexas.edu!swrinde!pipex!peernews.demon.co.uk!dekard.demon.co.uk!matt
Subject: Re: Actor Talk
References:  <3ieemk$i19@ixnews3.ix.netcom.com>
X-Mailer: cppnews $Revision: 1.41 $
Organization: Coyote Ltd.
Lines: 20
X-Posting-Host: dekard.demon.co.uk
Date: Wed, 22 Feb 1995 20:35:02 +0000
Message-ID: <793510502snx@dekard.demon.co.uk>
Sender: usenet@demon.co.uk

In article <3ieemk$i19@ixnews3.ix.netcom.com> baker-j@ix.netcom.com (John Baker) writes:
> Another way I thought of would be this:  I'm thinking of writing a 
> program that would parse through all of the .t files in the current 
> directory and build a list of all items that have the 'noun' property 
> defined and then prompt you for dialog on each.  You would leave blank 
> any item that you plan on producing special effects for (this would be 
> hand-coded later).  The program would then generate code for a 
> bare-bones actor that you could either flesh-out or cut & paste into an 
> already defined actor.
> 
> Would any of you TADS authors use such a tool?
>

There is an intermediate to high probability...

Cheers,

Matt.

"flows like water, reflects like a mirror, and responds like an echo."
