How to invoke JavaScript/ExtendScript for Premiere Pro CC in Mac OS

[Premiopolis]

Looking for a way to run JavaScript aka ExtendScript in Premiere Pro CC

Here's what I've got for other Adobe Apps, using AppleScript:

tell application "Adobe After Effects CC 2015"
  activate
  set SomeExtendScript to "ThisVariable='Runs This Js Code';"
  DoScript SomeExtendScript
end tell
tell application "Adobe Photoshop CC 2015.5"
  activate
  set SomeExtendScript to "ThisVariable='Runs This Js Code';"
  do javascript SomeExtendScript
end tell
tell application "Adobe Illustrator"
  activate
  set SomeExtendScript to "ThisVariable='Runs This Js Code';"
  do javascript SomeExtendScript
end tell

But so far nothing for Premiere.

tell application "Adobe Premiere Pro CC 2015"
  activate
  set SomeExtendScript to "ThisVariable='Runs This Js Code';"
  -- Does not work: DoScript SomeExtendScript
  -- Does not work: do javascript SomeExtendScript
  -- Does not work: do script SomeExtendScript
end tell

[Premiopolis]

Great, so the only step I'm aware of having skipped was signing the .zxp bundle, under the assumption the PlayerDebugMode CLI command would be sufficient.  Any other things that might keep your PProPanel from appearing under menu Window > Extensions?

[Bruce Bullis]

Sure; send me your panel directory. [b b b at adobe dot com]

[Bruce Bullis]

I see the problem; documentation ambiguity!

Put /PProPanel directly into /extensions, not into a /PanelDir subdirectory. I meant /PanelDir to imply "your panel's directory", but you're not the first to run into that doc bug...

[Premiopolis]

I love an easy fix.  Extensions now active, and I'm able to run the panel, but I'm getting a bunch of undefined alerts when I launch it.

[Bruce Bullis]

<sigh> that shows you're up to date; that's a typo in the current repo version. I sent you a slightly older version (which loads and runs) via email, and will try to fix the typo tomorrow...

[Premiopolis]

Ok, no worries.  I didn't get the email yet, but all told this is all looking great.  Most important from here is just to build something from scratch that can send an API call to Premiere.  Thanks again.

[Premiopolis]

If you get a chance and can explain the typo, that would be great.

[Bruce Bullis]

I can explain the failure, though haven't hunted down the typo.

In /PProPanel/jsx/Premiere.jsx, the sample defines a big ol' blob of ExtendScript functions, in a structure called "$._PPP_".

Somewhere between testing and posting the most recent updates, we (probably I) introduced an errant brace, comma, or semi-colon, somewhere in that blob.

I haven't yet gone through the file and diff'd it against previous, looking for the problem.