I’ve never done any Applescript but I thought I would give it a try. I still had some work to do to finish off my migration work that Applescript sounded like the perfect tool for (the migration for my blog history from Ecto/Wordpress to my new blog tool MacJournal).
In looking at Applescript, I’ve discovered the dictionary portion which may be useful but for a beginner the language is very “archaic” and hard to understand. I’ve written specifications for API’s and know what they look like (I’ve mentioned in the past that I worked for Microsoft) so what I’m getting at is that there are often subtleties that are in using an API that need to be described that specifications don’t give a programmer. The dictionary seems to be nothing more than a regurgitation of the API specification so is useful to a small degree but not to the uninitiated.
In my case, a sample winds up being immensely more useful followed by the dictionary. Unfortunately, samples are very hard to come by and essentially non-existent for MacJournal uses. I’ve gotten one or two of the interfaces to work but not the key ones I wanted and need for my purposes.
That means I’m dead in the water and will proceed manually which will take a long time to get the material cleaned up.