3 ms·
I had to automate transforming some Excel data for a friend recently and I did it using AppleScript. Turns out it’s not as bad as the prevailing HN narrative.
by alwillis 5y ago
I had to automate transforming some Excel data for a friend recently and I did it using AppleScript.
Turns out it’s not as bad as the prevailing HN narrative. It does require a change in mindset but once you get there, it’s actually quite nice, especially when using an app with a nicely designed dictionary.
Like a lot of Apple’s technology from the 90’s, it was a technology before its time. It certainly was pretty important during Apple’s near death experience in the late 90’s due to the publishing workflows that could only be done (at that time) using AppleScript and Quark XPress, etc.
- fzumstein 5y agoHave a look at xlwings (I am the creator), it’s a Python wrapper around AppleScript that follows closely the original VBA object model, so won’t require a change in mindset.
- hhas02 5y agoHi Felix! Sorry I’m a jerk who never responds to PRs, although I know py3-appscript* is in its best hands with you so just keep rolling as you see fit. (*I am currently dragging nodeautomation back up to operational status so I can use it in new customer work, but that’s as much appscript-ing as my poor brain can cope with now.)
- fzumstein 5y agoHey has! I should have mentioned that xlwings is a wrapper around your excellent appscript package that does all the heavy lifting with AppleScript :) Thanks for reviving the project on GitHub :)
- hhas02 5y ago“I should have mentioned” Not at all. Results are what matters, not the technical gubbins under the hood. I’m happy appscript helps you to empower your users.