• 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: Why is copying a file so hard?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why is copying a file so hard?


  • Subject: Re: Why is copying a file so hard?
  • From: Doug McNutt <email@hidden>
  • Date: Thu, 23 Jun 2005 10:42:38 -0600

At 16:10 +0100 6/23/05, has wrote:
>Doug McNutt wrote:
> >Developers would NOT mind a prohibition on spaces in names of commands and variables which would greatly simplify both scripting and reading of other's scripts..
>
>Again, there are plenty of other languages that do this. Why not use one of those?

Again. . .  I do use a few of them. It doesn't make reading AppleScript source easier.

AppleScript is a must-know language for interfacing with existing applications. The only information available for most is the AppleScript dictionary which makes sense only in the linguistics of AppleScript under Script Editor.

In fact I do use another language for my scripting. It's usually perl or tcsh scripts on OS neXt but it remains MPW scripting on this 8500.  I have been known to use C and even FORTRAN.

osascript << ENDSCRIPT
	tell someone
		do something
	end tell
ENDSCRIPT

Begin
  Echo 'tell application "iCab"'
  Echo ' activate'
  Echo ' GetURL "https://www.usbank.com/LoginPage";'
  Echo 'end tell'
End | RunApplescript >> Dev:Null

are ways to avoid most of the language nonsense of AppleScript. Stay out of AppleScript as much as possible and use it only when commanding an application.  MacGlue, by another Chris (Nandor), is also available but for that one still has to navigate the dictionaries to somehow discover the commands allowed by an application. There are examples of applications that publish their underlying Apple Events so that one can create high level events manually but they are few and far between. Did you ever try decoding a aevt resource with ResEdit?

And while I'm at it. . .

A "Developer" was one who was accepted by Apple after making a proposal and submitting a business plan to Apple for approval. I was D1715 and that was my AppleLink address. I really don't think this list, very much in the realm of Apple jargon, should be redefining the term.

--

Applescript syntax is like English spelling:
Roughly, but not thoroughly, thought through.
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Why is copying a file so hard?
      • From: "John C. Welch" <email@hidden>
References: 
 >Re: Why is copying a file so hard? (From: has <email@hidden>)

  • Prev by Date: Re: Why is copying a file so hard?
  • Next by Date: Re: Not as bad as thought (Was: Major Tiger AppleScript security hole?)
  • Previous by thread: Re: Why is copying a file so hard?
  • Next by thread: Re: Why is copying a file so hard?
  • Index(es):
    • Date
    • Thread