I have this working draft of a post explaining how badly broken Applescript is from purely an Apple-owned technology perspective, and imploring Apple to do something about it. It’s a bit long. But, since Adobe’s Creative Cloud has been released and I got my grubby little hands on a copy, I decided to look at the state of Applescript support in my most-used applications. It’s not that I have high hopes of anything improving given support since Creative Suite 5, but this is my bread and butter so it’s worth a look to see what I have to workaround in future upgrades of scripts, if upgrading a script is even worth the time.
Currently, my Applescript “support” of in-house that utilize Adobe applications has been relegated to using one call—
Here is what we have to work with.
- Photoshop: Line 1280.
- InDesign: Does not exist in the header.
- Illustrator: No header could be generated because the sdef (scripting dictionary) file does not exist.
I took a look at some other apps, like Bridge, and things go generally downhill from there. Essentially, any Applescript-related support is rendered useless in Creative Cloud. This is infuriating, back-stabbing bullshit. I would also like to say this is also unacceptable but that would ring hollow since the state of publishing technology is such that I have no choice but to use Adobe software. Nowhere on their site do they formally announce the drop in support in Illustrator, and given the dodgy performance of their Applescript API.
I wish Adobe would do three things:
- Formally announce that Applescript, if not OSA support in general, is going away.
- Pick a date well in advance (like a year) for developers to prepare.
- Turn it off all at once so I can stop having to hunt for the state of their API.
This unannounced erosion in API support by inconsistency is poor form, though I expect nothing less from Adobe these days, and reflects their general customer support as well.