omv.xml for CC 2018

[Davide_Barranca]

Hi,

is there a new version of the Object Model Viewer file (omv.xml) for Photoshop CC 2018?

The one that belongs to /Library/Application Support/Adobe/Scripting Dictionaries CC/photoshop/ has what appears to be the correct creation date, but inside it still mentions Photoshop CC 2015.5.

As a side note, is there any documented change in Scripting for CC 2018?

Thank you,

Davide

[Jarda Bereza]

What is the purpose of this file?

[Davide_Barranca]

It's used by ESTK as the source of information in its Object Model Viewer.

If you were asking what do I do with it, I've been asked for it by ID developer Gregor Fellenz, who's compiled a much, much nicer PS Scripting documentation here: https://www.indesignjs.de/extendscriptAPI/photoshop2015.5/#about.html

It was for CC 2015.5, but ever since we've got no updates to omv.xml

[Jarda Bereza]

I asked for documentation update from Adobe devs and I heard something like "january"

And I also would like docs for "Spaces" kind extensions like rich tool tips, learn tooltip, search console ...

[Davide_Barranca]

Are you aware of any update in Scripting? I'm not – for sure there's something, at least some bugfixes.

[JJMack]

Adobe ExtendScript Toolkit is a mess. I been using Windows 10 Preview and the other day  something happent to my windows system.  It was running slow when I tried to reboot Windows 10 did a green screen of death on me and reconery gave me the same error with a blue screen of death.  I had to create a bootable Windows 10 install media and install Window 10  Fall Creative update. 

I had many versions of Photoshop installed but now I had none. I desided now to install the Photoshop versions that I would work well on Windows 10.  I did not install CS2, CS3, CC, cc2015, cc 2015.5 and cc 2017.

I started with installing CS6 using the creative cloud desktop application.  Both the 32bit and 64 bit versions were installed and so was  Bridge CS6, Adobe ExtendScript Toolkit CS6 and Adobe Extension Manager CS6.  CS6 version 13.0 was the level then creative cloud desktop was then able to update that to version  13.1.2.

I then had the desktop application install CC 2014 and the had the desktop application update that.

Then I had the desktop application install CC 2018 using the advance option I keep the other  Photoshop. ersion installed.   Photoshop CC 2018 and Bridge CC 2018 were installed from the desktop application. But they are listed as CC not CC 2018 in the desktop UI.  They are listed as CC 2018 in Windows start button.

Adobe ExtendScript Toolkit CC was not installed.  When I search Adobe.com for it when I click one the link to download it. The page started the Creative desktop application which did not install anything.  It just showed that Adobe ExtendScript Toolkit CC was up to date. 

Lucikly When I installed CC 2014 when it was new  I download the offline installers for CC 2014 including the offlin installer for Adobe ExtendScript Toolkit.  I use the offline to install Adobe ExtendScript Toolkit CC and added it the windows start buttom.  Yoc can not start  Adobe ExtendScript Toolkit  fron the Creative Cloud desktop application. 

The offline installer link no longer has links to download offline installers.

The  latest omv.xml files one my system are for Adobe Bridge CC 2018 and Adobe Photoshop CC 2015.5.

[Davide_Barranca]

JJMack , life is similarly complicated in the Apple side of things, when it comes to installation 🙂

I'm going off-topic, but...

What I still don't get is why when you download old versions (which is OK) you don't get the latest patch (not OK). E.g. you open the CC app, you're shown the list, CC, CC 2014, CC 2015, fine. You click Install for CC 2014, what do they think you want? CC 2014-latest.

No, you're going to download CC 2014.0.0, and when it's there, as soon as the installation process is done, you're prompted to update it and download CC 2014.2.2, which is what eventually you'll get.

Mind you, you're not allowed to choose between intermediate point versions (when available), you either get 2014.0.0 (first release) or 2014.2.2 (latest release).

Logically (or at least from my POV) either you can pick among all the available versions (major.minor.patch – there might be bugs you want to skip, you want to test  scripts on a specific version, etc), or you just get the latest and what the heck who cares about the rest.

End of the rant 😄

Davide

[Tom Ruark]

Looks like this is the only new dom entry: app.toolSupportsBrushPresets(app.currentTool)

However, there are keys that get added that do not make it into the DOM. I use Getter and ScriptListener routines to inspect what is available at the ActionDescriptor level.

[Jarda Bereza]

Tom Ruak:

1) any chance how record actions with "dontRecord: true"? E.g. layers moving, zooming, groups collapsing/expanding You can execute it in Action Manager code, but you can't simply discover it.

2) I assume that everything in DOM uses Action Manager code. Could we see what action manager code is inside specific function? E.g. getting histogram for specific layer. 🙂

3) Does Getter shows more informations or is it same as ScriptListener but only in C++ ?

[Tom Ruark]

1. Yeah. One of our interesting tricks. Run an action but don't record it! Layer moving will record once you do something else right. It is one of our "accumulated (reoccurring) commands"

2. Yes. The ScriptingSupport plug-in is just a bunch of ActionManager code at its heart. There has been talk of just rewritting it in JavaScript but that would be huge effort and we need it for VisualBasic and AppleScript (the plug-in that is). I'll see if I can give away routines. May have some dependancies. The real trick it does is stack based classes that change the target and then reset it.

3. There is Listener (what just happened) and Getter (what can you tell me about current document/app/layer/etc.) They use the same code to "pull apart a descriptor". Listener is much simpler then. Getter has to know a bit about what questions to ask. But yes. ScriptListener IS Listener C/C++ from the SDK and just the output was tweaked to do JavaScript and VisualBasic out.

[paulj56233840]

I am new to scripting and I'm at latest update (Photoshop cc 2018). I have downloaded the Extendscript toolkit and have a similar mess.

1) It appears in creative clouds apps, but there is no way to launch it from there.

2) I can launch it from Windows Start menu, but there is no detail in the Object viewer

3) There are NO OMV files on my system and looking at older posts on this subject the directories mentioned also do not exist

I think Adobe forgot to included this file on the latest update

Regards Paul

[Silly-V]

Anything new for the 2019 version?

[Silly-V]

Well, just a note to self - there's no TiffEncodingType, now it's TIFFEncoding.

Grumble..

Seems like the go-to answer is to run a script listener and copy down the cryptic AM code.

Call me old-fashioned, but I like the old school method of being able to see the documentation and use the contents therein to accomplish my tasks. Last of a dying breed...

[林天60860475]

Hey, I saw you again, teacher, I bought your PS script tutorial book.

Because my English is not good, I am very hard to learn, but it is really very good! thanks again!