{"id":35797,"date":"2022-05-07T15:43:33","date_gmt":"2022-05-07T19:43:33","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=35797"},"modified":"2022-06-10T16:25:23","modified_gmt":"2022-06-10T20:25:23","slug":"jxas-parenthesis-paradox","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2022\/05\/07\/jxas-parenthesis-paradox\/","title":{"rendered":"JXA’s Parenthesis Paradox"},"content":{"rendered":"

Dr. Drang<\/a>:<\/p>\n

Because the name of the process is what we want to return, name<\/code> has to go last in the chain of calls, and it’s the one that gets the parentheses. We’re applying the whose<\/code> filter to the processes, so it has to go after processes<\/code>. The properties we’re filtering on (just visible<\/code> in this case) are set up as a JavaScript object that’s passed as an argument to whose<\/code>.<\/p>

Suppose we had two criteria for our filter? Let’s say we want all the visible processes that start with the letter M<\/em> (which will return just Mail and Messages). In AppleScript, it’s easy to add an extra clause:<\/p>

tell application \"System Events\" to get the name of every process ¬\n    whose visible is true and name begins with \"M\"\n<\/pre>
In JXA, the syntax gets nasty:<\/p>
Application('System Events').processes.whose(\n    {visible: true, name: {_beginsWith: \"M\"}}).name();<\/code><\/pre><\/blockquote>\n
JavaScript is nicer for basic programming and data manipulation, but Apple event stuff is much nicer in AppleScript.<\/p>\n
Update (2022-05-10): See also: JavaScript vs. AppleScript<\/a>.<\/p>\n\n
Update (2022-06-10): Dr. Drang<\/a>:<\/p>\n
\n
Next, we move on to whether JavaScript for Automation<\/a> (JXA) is worth getting into at all. Do AppleScript concepts really translate well to JavaScript? The same day my last post<\/a> was published, Rosemary and David released their Automators episode with Daniel Jalkut<\/a>. While discussing Daniel’s FastScripts app<\/a>, they had a little sidebar about JXA. Daniel doesn’t think much of it. “It just shouldn’t be there” was his most pithy comment, but he also mentioned an “impedance mismatch” between the JavaScript language and the AppleScript infrastructure underneath it. Exactly.<\/p>\n
[…]<\/p>\n
Finally, let’s talk about the reason I’ve used JXA for some scripts: JavaScript has a good regex engine and AppleScript has none.<\/p>\n<\/blockquote>\n
Previously:<\/p>\n