Automator isn't AppleScript. Honestly... it isn't. They're totally separate things. No, there isn't even a little bit of a shared anything between the two. They're similar in concept, sure, but when you're using Automator, you're using Automator's infrastructure. When you're using AppleScript, you're using AppleScript's infrastructure. What? No! Automator isn't intended to replace AppleScript! Who told you that?! Tiger's only just out and yet I've already had this exact conversation about Automator a dozen times or more. Every time it's like talking to a fussy five year old and having to convince them that nope, there aren't any Brussels sprouts in a hot dog. And nor did I sneak any in there while he wasn't looking. It's an important point, but dangit, just try convincing somebody of that, too. Tiger ships with two wonderful technologies that can reduce nearly any procedure, process or function from an entire afternoon's worth of tedious steps to one or two mouse clicks. Automator is Tiger-only, and lets you assemble a linear process by dragging together a sequence of pre-fabricated actions. AppleScript is more like a conventional programming language, where you have to a lot of doing this. (Oh, sorry: at this point, I'm miming the act of typing in lots and lots of lines of code. Again, I've had this discussion so many times that I go by rote.).
展开▼
