![]() Can use Script Debugger 7, a huge point in its favor:.Here are the pros and cons, IMO: AppleScript The hard decision is whether to learn AppleScript or JXA. If you need to do a lot of web page scraping/manipulation, then you will need to learn JavaScript (separate from JXA). So, IMO, you need to learn KM, and then either AppleScript or JXA. And, believe it or not, Apple often provides a poor scripting model for its apps. Let me just add here that both AppleScript and JXA are completely dependent on the App developer to provide a good scripting model. KM can not really talk to the Apps scripting model, only its UI. Sometimes I need to interface with the scripting model of an App (like you did with Pages), so then I turn to AppleScript or JXA. Many times KM can do everything I need, so I stop there. So, I approach almost all workflow automation tasks by starting with KM. It can also use Swift, and there have been a few attempts to maximize the use of Swift, but I have not seen any real of Swift to benefit workflow automation. However, some things are still best done by script, but KM can easily use most any scripting language, especially AppleScript, JXA, and shell scripts. KM can easily do many automation tasks that it used to require a script to do, and is, in general, much easier to use. They are both based on the same core Apple Event model, that just have two different languages sitting on top. My primary Mac automation tools are: KM, AppleScript and JXA, JavaScript in Browser, Shell Scriptsįor the moment, I am going to use AppleScript and JXA interchangeably. What's are the possible downsides to just using KM (along with calling shell scripts from it)? Is there a better choice?Īnd after looking over KM, I've found that it has a very robust integration with MacOS apps that I found so appealing in AS. What are your opinions on all this? Should I bother with AS over KM? Or bother with having to build MacOS App support with Swift? ![]() And I've heard that the downside of Swift is that it doesn't have the existing integration into MacOS apps that AS has. I've been told that AS is going away and that Swift is taking over. And after looking over KM, I've found that it has a very robust integration with MacOS apps that I found so appealing in AS. Yesterday, I pulled out Keyboard Maestro and was able to get a script to do the same thing in about a half hour. After several months, with my more than 40 years of programming, I've been quite disappointed with Applescript. The example I lifted from the web to update fields in a document works fine for the example text, but often breaks and is very cumbersome for the single-page Pages documents. I put together a script to update fields in MacOS Pages documents. For simple programming examples, it seems to work fine. I've heard the English-like syntax is supposed to be a big strong point. Applescript seems like a very powerful scripting tool because of its strong integration into the MacOS system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |