From: Jon G. <jg...@hi...> - 2002-03-12 16:07:19
|
At 8:12 AM +0100 3/12/02, Andreas Otto wrote: > are examples available ... Generally, look for AppleScripting examples in the app you wish to call. Once you know how it can be scripted, you should be able to call TclAppleScript trivially. There may be reasons, depending on the nature of communication, why you'll want to go to the additional trouble of using my TclAE. One reason is that many apps support AppleEvents for which they have not provided an AppleScript interface. /If/ you can find documentation of those AppleEvents, then TclAE is pretty much your only option for exploiting them. >why does tcl blow away the argv array ? Because it is never meaningful in a Mac application. A Mac application cannot be launched from the command-line because there is no command-line so there can't be any command-line arguments. You can use MPW or tclsh or Alpha or any number of other tools to emulate a command-line on a Mac, but you cannot change the underlying truth that the Mac does not have and does not understand this mode of doing things. > > Sure AppleScript/Tclapplescript is one option. My TclAE > >Is a download path available ? TclAppleScript is included with the standard Mac Tcl distribution: [package require Tclapplescript]. TclAE is presently documented at <http://www.his.com/jguyer/Alpha/TclAE%20Help/>. I don't recommend you download that library, as it's rather old. I should be uploading a current version soon to <http://sourceforge.net/projects/tclae/>. I will post here when that happens. > One help would be not only to cretae the xml files, it should be possible > to call code-warrior to do the compiling and linking themself without > using the user-interface. If this is possible it would be a big step in the > right direction. The CW IDE has extensive support for AppleScript and general AppleEvents. I don't have my CW docs handy, but if you look through the manuals for the IDE, you should find it. Instructing the IDE to compile and link is certainly feasible. -- Jonathan E. Guyer <http://www.his.com/jguyer/> |