The (sometimes "very much") less straightforward part of Applescript is that each supported application has its own dialect and to fully make use of it, you need to know what it is capable of. The straightforward part of Applescript is that you know it is here to help you automate your work with the applications that run on your Mac (or at least most of them). Second, with the current massive and ongoing corporate takeover of the internet, if you have energy to be annoyed about a message that's relevant to the 2 lists it is sent to, you probably just had a bad day, and you should take a deep breath before hitting the Send button, or even before thinking of replying at all (especially if the relevant part of the reply is, well, irrelevant). It's kind of like replying "RTFM" when there is only a technical specification and no manual around. a vocabulary list is not documentation."įirst, as Neuburg wrote, the dictionary is specifically not the place where you're supposed to find the answer to such questions.
Pfiddlesoft ui browser alternatives how to#
The problem is how to do things with words. I was not disapointed when the first answer I got turned out to be roughly "check the dictionary, and don't crosspost because it's annoying".Īs Matt Neuburg states in his wonderful and always relevant "Applescript: The definite Guide" (O'Reilly, 2003) ", p344: "Is there a place that describes what System Events is, how it works, why it is necessary for some sorts of scripting, etc.?" As I'm willing to know more about what I'm actually doing with Applescript, I decided to bite the bullet and ask the question on both the official AS user list that Apple seems to be ready to dump any time now, and the new, user based AS list hosted on groups.io: Ok, so you know you can do black magic with that " application" but you don't know the extent of the magic.
This one comes from one of my test scripts, but in all honesty I can't remember what it's doing by just taking a look at it ( always put comments in your code).
0 kommentar(er)
