On Mon, 11 Mar 2002 15:15:46 -0800, Crook, Richard W wrote:
>Just a quick question/survey. I'm taking over an system written mostly in
>AppleScript and some MacPerl. Is it worth sticking with the AppleScript or
>should I port it over to MacPerl. I suppose the answer will be obvious
>considering the list I'm spamming but I thought it might be interesting to
>hear some opions about the topic.
It depends on what you want to do. AppleScript is extremely slow as a
generic programming language, but OTOH, in order to control external
apps, calling an Applescript embedded in a Perl script takes a very long
time to compile -- which will have to happen every single time. The
alternative is raw AppleEvents, but it's very hard to write stuff in,
compared to plain AppleScript. Check out the modules Mac::AppleEvents,
Mac::AppleEvents::Simple, Mac::Glue. (They appear to come with the new
MacPerl 5.6.)
OK, silly question from me... has anybody written a tool, or a part of a
tool to convert Applescript source code into code directly usable by one
of these modules? Something along the lines of the B::Deparse, but for
Applescript... I guess not...
--
Bart.
