Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!umich!yale!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!mips!pacbell.com!pacbell!osc!tma
From: tma@osc.COM (Tim Atkins)
Newsgroups: comp.windows.ms
Subject: Re: Advice wanted on Windows prototyping tools
Keywords: CASE, Actor, Smalltalk
Message-ID: <2939@osc.COM>
Date: 17 Jun 90 06:56:29 GMT
References: <965@ashton.UUCP> <1990Jun7.202442.2687@chinet.chi.il.us>
Reply-To: tma@osc.UUCP (Tim Atkins)
Distribution: usa
Organization: Object Sciences Corp., Menlo Park, CA
Lines: 21

In article <1990Jun7.202442.2687@chinet.chi.il.us> patrickd@chinet.chi.il.us (Patrick Deupree) writes:

>
>Don't forget about ToolBook.  If you want to create screens quickly this will
>do it for you.  You can then use something like Actor to create the code
>that will run in the background or that will integrate ToolBook screens.
>Patrick Deupree ->	patrickd@chinet.chi.il.us

 As I understand it, Toolbook can integrate DLLs into itself.  However, I've
heard that Actor can not create DLLs but only use them.  So I'm a bit confused
as to what you mean about running actor code in the background.  As for 
integrating ToolBook screens,  I don't see how Actor or any external language
could possibly manage to deal with the ToolBook scripts.  I'm flying blind here
but I assume that some run-time ToolBook support must be present for a TB 
screen to operate properly.

 Forgive me if I'm simply misinformed.  Thank you for any clarification of
these questions.


- Tim