Object Model 11 and using JetBrains Webstorm for ExtendScript

[loyal_operator154A]

Hi,

There is great help docs on Object Model v10: InDesign ExtendScript API (10.0)‌ so I'm wandering, if there is updated version for CC 2015 release?

I have found project on GitHub: yearbook/extendscript-api-documentation · GitHub that should generate new help docs, that can be used later in 3rd party IDE, like JetBrains WebStorm,

but unfortunately I'm not able to generate new docs files - it just gives me bunch of errors, I tried at Windows and Mac (I have node.js installed, as well as all required modules)

So if you have, or know how to get new help docs and then use them with WebStorm - please share!

[grefel]

I just updated the Object Model 11 a few hours ago, but had no time to test yet. Anyway it should work, and I share the link:

http://www.indesignjs.de/extendscriptAPI/indesign11/

There are not that many changes, because there not that many changes in CC 2015 😞

By the way you'll find the XSLT transformation on github as well, might be useful for a webstorm integration.

https://github.com/grefel/extendscriptApiDoc

[loyal_operator154A]

Great! Thanks for online help docs!

Unfortunately I'm not familiar with XML and currently can't figure out how to generate this docs by myself once adobe release next update... Is it possible to have some automation script, that will automatically find those xml-files, depends on OS version, and generate help docs, using shell command or something?

Am I the only one at this forum who wants to use WebStorm as IDE for Adobe scripts? It would be awesome to have plugin for WebStorm that supports ExtendScript, can generate docs and use them as autocomplete, combine multiple files to one file, do minification, etc., have standard basic libraries for UI (to make scripts look like native panels and dialogs), basic lib for GREP replace (so we don't have to write same code everytime we write new script), etc, GUI, Shell (where you can write something like app.activeDocument.marginPreferences.top and get it's value directly in IDE) - is it at least possible? or I'm just a dreamer?))

It would be awesome if we could standardise our workflow and scripts!

There are not that many changes, because there not that many changes in CC 2015 😞

yeah, that's why scripters have to make some innovations, making new useful scripts))

[Laubender]

Is it possible to have some automation script, that will automatically find those xml-files, depends on OS version, and generate help docs, using shell command or something?

You cannot simply "find" those xml-files.

The ESTK will have to create these for you.

It could do this "automatically", if the ESTK's target is set to the latest version of InDesign and you are about to run a script. It could also go wrong (once I had this case) and you have to remove the old XML files, restart InDesign, restart the ESTK and connect the ESTK again. Then I had to run a simple script. The ESTK now created the XML files (that took its time, so be patient).

Uwe

[loyal_operator154A]

I was talking about finding those files:

https://github.com/grefel/extendscriptApiDoc

XML file locations

The XML source files can be found in the following locations on Mac OS X.

• /Library/Application Support/Adobe/Scripting Dictionaries CC/CommonFiles
• ~/Library/Preferences/ExtendScript Toolkit/4.0/omv$indesign-9.064$9.0.xml

On Windows the Files are located at:

• \Users\[Username]\AppData\Roaming\Adobe\ExtendScript Toolkit\4.0\omv$indesign-10.064$10.0.xml
• C:\Program Files (x86)\Common Files\Adobe\Scripting Dictionaries CC\CommonFiles\

And I'm more then sure that those files can be found automatically, using OS detection, and some RegExp magic (so we don't have to find and copy/paste them manually)

[Laubender]

Yes, I know what you are talking about.

The ESTK not only has to create new versions of the omv$indesign(…).xml files when a new version of InDesign is installed, but also, if new plug-ins are installed or removed, that are scriptable. So this is a dynamic process creating omv$indesign(…).xml files on the fly.

Uwe

[loyal_operator154A]

sorry, I still don't understand what's the problem? ESTK is generating new xml files, but if I can manually find those files and copy/paste them to special xml folder and then run 3 scripts that will generate dock, then why we can't make only one script, that automatically find those xml file, copy them to desired location, and do all necessary transformations running only one shell command?

instead of:

1) find xml files

2) copy them to xml folder

3) run mergeFiles.xslt

4) run fixDom.xsl

5) run dom2dita.xsl

why we cannot simply have one command line:

$ docs update

that will do all necessary work at once - that's what I was talking about

[grefel]

The creation process can be automated with a shell or batch script (the generation of the xml files will probably still be manually). Everyone can jump in and fork the github soruces or send me a push request. For me; I'm totally happy with pressing 5 buttons once a year (i'll use oXygen XML Editor for the creation).

All the best,

Gregor

[loyal_operator154A]

One button solution is necessary for people like me, who are not familiar with all that XSLT things... and those people probably will not be able to make those batch / shell / whatever by themselves...

I will try to do something with that using Node.js (since CC2014 node is shipped with CC programs), but not sure if I will able to make it right...

Anyway thanks a lot Gregor!

[Another1984]

Hi,

Could you please explain how to use WebStorm/PhpStorm for this stuff?

Thank you

[loyal_operator154A]

The same way as any other IDE: I just expected to get autocomplete / properties names spell check in JetBrains products...

But since nobody could help me with this, and personally I don't have enough skills and time to figure it out, I'm keep using Adobe's ExtendScript Toolkit CC

[Another1984]

Thank you for reply!

I'll try to solve this.

[Another1984]

Hi, I'll try this (last post - October 13, 2015 18:22)

Adobe ExtendScript – JetBrains Support