boba@iscuva.UUCP (02/18/87)
In response to my questions about running MPW tools as stand alone programs, I've gotten some helpful advice. MPW tools can be launched on their own and are capable of console input/output. And as far as passing parameters, the 'tool' can detect that it is running stand alone and present dialog boxes, use the Finder's parameters, etc. Great! Thanks -- I'll give it a try. But there is still a problem, and I'm soliciting suggestions. My questions are all regarding an implementation of a programming language (Icon) which consists of a translator, linker, and interpreter, all of which are separate MPW 'tool' programs. Under the MPW Shell, the program building process is controlled by command files (shell scripts) which run the necessary tools in sequence. Running stand-alone under the Finder, the process seems that it would be a bit unwieldly. Double-click the translator, identify the file(s) to be translated, then do the same for the linker, and then run the program. Using Icon under UNIX or MPW, all this is done pretty much automatically by a "control" program called "icont" (similar to "cc"). Under UNIX, icont actually runs the needed tools as necessary. Under MPW, it creates a script file and then executes it. Could something similar to this be done under the Finder? I'd imagine the answer is no, but I haven't given up hope. In general, I know of no way that Mac programs can execute other programs and still maintain control themselves. Although the MPW Shell does it, I expect it uses tricks that are difficult for ordinary mortals to duplicate. (I don't want to spend lots and lots of time on this). Obviously, I'm not the first to look at this problem; it is a problem faced by anyone attempting to create a development environment using the Macintosh User Interface. I'm not terribly familiar with other solutions to this problem (e.g. Mac C), since I've mostly used Aztec and MPW, which are shell-oriented. By the way, the early draft documentation for MPW made references to writing your MPW tool to run also as stand-alone, with those areas marked "to be supplied". I was sorry to see all of those references totally disappear in the V 1.0 draft documentation. Did anyone else notice that? -- Bob Alexander ISC Systems Corp. Spokane, WA (509)927-5445 UUCP: ihnp4!tektronix!reed!iscuva!boba