Porting a 3-line AppleScript hack to Swift 3 in Xcode is not hard. But there’s always a but…
What more is needed if Swift is going to realise its promise as a scripting language for macOS?
Why does writing a simple app in Swift keep turning into an esoteric guessing game? More hurdles for re-scripting in Swift.
How easy is it to build a real ‘scripted’-type app in Xcode? Here I start to re-implement an AppleScript app using Swift.
There’s no point trying to script in Swift if you can’t deploy it to a user’s Mac. Here are two solutions available now.
Running shell scripts from Swift playgrounds is easy, but there’s more work needed to support droplets and folder actions.
A success at last: scripting file operations works now. But don’t trust much of the documentation; it just frustrates.
A frustrating first day trying to get Xcode’s Swift playgrounds to display simple dialogs and alerts.
Can this app really offer a “modern alternative to AppleScript”? Probably not yet, but it is young, and still an excellent Swift playground.
I’m heartbroken that AppleScript is going, and grieving at the departure of Sal Soghoian, but I’m looking forward to getting to grips with the scripting tools of the future.