3 ms·
>AppleScript because it has so many APIs. You mean the commands you can use on apps like iTunes, Finder, Photos, etc.? Those are not AppleScript-specific per s
by tzahola 8y ago
>AppleScript because it has so many APIs.
You mean the commands you can use on apps like iTunes, Finder, Photos, etc.? Those are not AppleScript-specific per se (AFAIK there used to be an option to write Automator scripts in JS). You'd need the Linux/Gnome/KDE equivalent of the Open Scripting Architecture ( https://developer.apple.com/library/archive/documentation/AppleScript/Conceptual/AppleScriptX/Concepts/osa.html https://developer.apple.com/library/archive/documentation/Ap... ) with active participation from app developers. Sounds like a huge overtaking.
- peterburkimsher 8y agoYes, it would be a huge undertaking. I've already rewritten my own apps for offline maps, calendar, notes, and I plan to write contacts and iTunes too. When there's a standard API comparable to Apple Events/OSA within those core apps, I'd hope to have enough leverage to persuade other app developers to accept pull requests.
- snuxoll 8y agoWe already have D-Bus to cover sending events to applications, what's really missing is a standard way to enable scripting. I've had a similar idea myself but never got around to implementing it, but I think a standard D-Bus interface applications could implement to expose a scripting dictionary along with a Python/Ruby/Whatever library to implement a more OSA-like interaction would go a long way.
- gurkendoktor 8y agoOut of curiosity, what GUI toolkit have you written these apps in/for? Something Mac-like (GNUStep)?
- corv 8y agoYes, you can still write Automator scripts with JavaScript! Unfortunately the documentation is AppleScript only.
- tzahola 8y agoSo, in 2018, at peak JS, it's practically an easter egg that you can write Automator scripts in JavaScript. I guess this is indicative of Apple's commitment to macOS automation...