Magical presentations. Fast. Easy. Beautiful

View Original

Microsoft VBA versus Applescript

I am dusting of my coding skills that were pretty much put on hold in the early 1990s and have started to program macros to automate the mechanics of the template store: creating individual slides and thumbnails for PowerPoint and Keynote in different aspect ratios of these design.

Things in the Microsoft Office ecosystem run smoothly ("VBA"), for Mac, a lot less so. Applescript is a language that aims to automate pretty much everything you can do in Mac OS. It has been around for a very long time, but it is falling short.

At first sight, the language looks very friendly, almost human-like. And here is a problem: human language is ambiguous. It is incredibly hard to use it to program computers. When I look at example Applescript code, it looks very easy to adjust and re-use, but it is an incredibly pain to get it actually working and iron out the last bugs. Writing macro scripts will never be something that the average Apple user will do, so you might as well stick to a programming language that an engineer can work with.

The second problem is the what Applescript can actually do. As Apple put development of Mac OS on the back burner and gave priority to its iOS devices, the functional power of Applescript has been watered down. Old tutorials online show functionality that has been removed in later versions of Keynote.

Now, I am not saying that all esoteric features should be supported in a scripting language, but I am struggling to get the most obvious and basic one that anyone wants to use a Keynote script for: batch conversion of PowerPoint files into Keynote.

I am not giving up, and will look for a solution. Let me know if you have any recent experience with Applescript and Keynote.


Cover image by Boris Stefanik on Unsplash