Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news.dfci.harvard.edu!camelot.ccs.neu.edu!nntp.neu.edu!news.eecs.umich.edu!news.mathworks.com!news.sprintlink.net!news-peer.sprintlink.net!news.sprintlink.net!news-hub.sprintlink.net!news.sprintlink.net!news-dc-9.sprintlink.net!news.gdbnet.ad.jp!news
From: Kevin Clark <kevin@objsoft.com>
Subject: Using VW with C/DLL connect
Content-Type: text/plain; charset=us-ascii
Message-ID: <331B14FB.4C0D@objsoft.com>
Sender: news@ns.gdbnet.ad.jp
Nntp-Posting-Host: 206.126.243.86
Reply-To: kevin@objsoft.com
Content-Transfer-Encoding: 7bit
Organization: Objectsoft, Inc.
Mime-Version: 1.0
Date: Mon, 3 Mar 1997 18:14:19 GMT
X-Mailer: Mozilla 3.01Gold (Win95; I)
Lines: 46

All:

Has anyone been able to start a Windows process and have it return the
text output back to VisualWorks?

In UNIX we use

	result := UNIXProcess cshOne: 'some process script'

In Windows we have used the C/DLL connect to create a WindowsAPI similar
to the one on PPDs page.

	status := WindowsAPI exec: 'some DOS command' newWindowState: 16

Note: the 16 represents the flag for no new DOS window.

-------

The issues with windows, is that it does not return the result of the
DOS command back to VisualWorks.

Solution 1:
We have a workarounds solution as such

	status := WindowsAPI exec: 'some .BAT file' newWindowState: 16.

The .BAT file pipes output to some .txt file which we read. With this
approach we do not know when the .txt file is complete. 

Solution 2: 

Emulate the UNIXProcess method. This solution must return the output
from the DOS shell command back to VisualWorks. WE ARE LOOKING FOR THIS
SOLUTION.


Any help?

-- 
Kevin Clark
Objectsoft, Inc
350 West Erie, 2nd floor
Chicago, IL 60611
312-266-7887 x 105
http://www.objsoft.com

