4 ms·
If I understand it correctly it's actually from 1992. As for Applescript: how precise can we get with it actually? I think when applications use native toolkit
by afraca 8y ago
If I understand it correctly it's actually from 1992.
As for Applescript: how precise can we get with it actually? I think when applications use native toolkits Applescript can figure quite much out on its own, but with custom elements (an Electron application), is this still the case?
- saagarjha 8y ago> If I understand it correctly it's actually from 1992. I think you're right–the 1998 is the date it was forwarded, or something like that. > As for Applescript: how precise can we get with it actually? I think when applications use native toolkits Applescript can figure quite much out on its own, but with custom elements (an Electron application), is this still the case? AppleScript can do everything you, the GUI user can do, at least for native applications. There is an API for adding functionality that doesn't map cleanly to a user interface through scripting dictionaries, so from a certain perspective it can actually do more. With regards to Electron, all bets are off: the application only has this functionality if it writes it itself. This is one of the reasons I generally have a distaste for Electron; it really breaks a lot of nice things that the system provides that are nonobvious if you don't use them but really hurt if you do.
- danenania 8y agoWhile they might not work well with Applescript, Electron apps can be scripted with a tool like https://electronjs.org/spectron https://electronjs.org/spectron.