Re: [MacPerl] MacPerl and inter-application communication

["Alex K Suska" <aksuska@insideflyer.com>]

>Thank you, I didn't know about MacPerl modes. I will look for some
>information. If, however, you can repost that message I would love to read
>it :-) I will try Sandra Silcot's mailing list archive as well.

Unfortuantely, I seem to have lost the email :-(  The "readme" is called
"MacPerl.Frontend" and would probably be cryptic to anyone who is not familiar
with the internal workings of the IAC OSA model.
If you are looking for a construct where FileMaker sends data to a running
script which then does something to that data and perhaps returns data or
otherwise, this continuing indefinitely (until some terminating condition
indicates otherwise), then you are looking at "remote" mode.  This is the most
complicated mode and I have not been able to figure it out.  I am sure that
there are more experienced members who can make this more clear.  The default
mode is called "local", where a script is invoked, runs, and only replies to the
calling AppleScript (AS) if &MacPerl::Reply is used.  "batch" mode redirects
STDOUT and STDERR to the calling AS.  I am unclear on how STDERR is handled, but
I imagine that the uses that reading STDERR affords can be accomplished with
other methods.

>I had read that when you compile a script, that "almost" the entire MacPerl
>application was included. I had hoped to use the "Do Script" command that
>can be found in MacPerl's AppleScript dictionary. I suppose another issue
>would be getting detailed information on what exactly is included when a
>MacPerl application is compiled.

If you mean by "compiling" building a runtime application, then yes, that is
true.  There is not much point in doing this unless you want a double-clickable
application, or would like to have multiple scripts executing simultaneously,
where in effect you actually have multiple MacPerl applications running.  "Do
Script" will give you a one-at-a-time script execution.  Using the remote mode
will probably give you better performance (the script won't have to be loaded,
intrepreted, etc. at each run), but is a much more complicated affair.

Alex

***** Want to unsubscribe from this list?
***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch