• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Migrating scripting addition...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Migrating scripting addition...


  • Subject: Re: Migrating scripting addition...
  • From: JJ <email@hidden>
  • Date: Tue, 26 Jun 2001 19:54:21 +0200

> Here is your script written more sensibly, referencing Akua Sweets and Jon's
> Commands as applications:

> Let's see what happens when we change back to referencing Akua Sweets and
> Jon's Commands as scripting additions:
>
> Surprisingly little has changed. Thanks for helping to prove my point.

Launching two additional apps Jon's & Akua prove your point?

Suppose I download a script from, i.e., macscripter.

<Where is application "QuarkXPress"?>
<Where is application "Jon's Commands"?>
<Where is application "7Akua Sweets"?>

Now, suppose my *mother* downloaded that script.
____________

Of course, there are good reasons to scripting additions become
applications, but my newbie applescripter mind says that move could be done
yet. Why SA are SA? Why aren't apps yet?
&
Weren't easy-developing and quick-execution two basic applescript's
features?
&
Certainly, when I use X, I'd prefer:
tell app "Akua Sweets" to munge from "x" to "y"
than
tell nothing to nobody

JJ


  • Prev by Date: Re: Help using dialog.
  • Next by Date: Re: Error geetting offset of char in errMsg
  • Previous by thread: Re: Migrating scripting additions to Mac OS X
  • Next by thread: applescript codewarrier examples
  • Index(es):
    • Date
    • Thread