Didn’t realize how insane/intriguing Yosemite’s JavaScript automation is. Scripts have access to the ObjC runtime: https://developer.apple.com/library/prerelease/mac/releasenotes/interapplicationcommunication/rn-javascriptforautomation/index.html#//apple_ref/doc/uid/TP40014508-CH109-SW17 …
@mjtsai Nope. It seems like a weird bifurcation. Surprised that they would open it up this much in JS, frankly.
-
-
@danielpunkass Yeah, I assumed that there was some principled reason for not doing it in AppleScript long ago. Anyway, I like the idea. -
@mjtsai It will certainly open up a lot of new automation possibilities.
-
-
-
@danielpunkass@mjtsai the hard part is just deciding what heuristic to use to convert selectors into function names -
@etrepum@mjtsai They could have opened AppleScript access using the same convention they adopted for JS: "JSExport" http://opensource.apple.com/source/JavaScriptCore/JavaScriptCore-7537.65/API/JSExport.h … -
@danielpunkass@mjtsai AppleScript syntax isn't really dynamic enough to make that work (needs static dictionaries). Hard to explain in 140… -
@etrepum@danielpunkass It already works (with somewhat awkward syntax) in AppleScriptObjC. They just haven't enabled it for normal scripts. -
@mjtsai@danielpunkass I see, wasn't aware of that. Looks like a different language, like Objective-C++ / Objective-C
-
-
@danielpunkass@mjtsai it was already possible to do that with js, so it was easier to add in. Also, look at how forward looking I was :)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Daniel Jalkut
Michael Tsai
Bob Ippolito
Gus Mueller