Hi.
I’ve just come across this UXP scripting, which seems to be the new way of writing scripts or plugins for Photoshop.
I have almost no experience with writing scripts for Photoshop, but we have an old script written in ExtendScript, similar to one of the scripts that come with Photoshop, which, in my case, can be found at /Applications/Adobe Photoshop 2024/Presets/Scripts/, which could be written using new JavaScript and UXP in order to take benefit from the new JavaScript features (like consts, let, classes, etc.), which would improve the code.
From what I’ve been reading, apparently, UXP still doesn’t support all features that ExtendScript supports, but I don’t know what the missing features are. What are they? For example, is it possible to rewrite the scripts at /Applications/Adobe Photoshop 2024/Presets/Scripts/ using the new UXP approach? Has anyone tried to do this?
If UXP is the future and it’s been around for a while, then why doesn’t the 2024 Photoshop application come with UXP scripts and instead still comes with old scripts? I’ve looked at some repositories and they have not been updated for a couple of years, which is a bit worrying.
I also was looking at the samples GitHub - AdobeDocs/uxp-photoshop-plugin-samples: UXP Plugin samples for Photoshop 22 and higher., but it’s still unclear what can’t be done with UXP scripting that can be done with old school scripting in JS (ECMA script 3).
Finally, I’d like to ask about something that is written in the documentation.
Scripts can be executed in a headless manner or with minimal UI, without the need for any manifest setup.
Does this mean that it’s possible to execute scripts that act on .psd files without opening the Photoshop app? So, could these scripts run in a CI pipeline? If yes, can you provide an example, if there’s? If not, then what does it mean to be headless? Ideally, our script should be run in a headless manner maybe in the cloud, so that’s why I’m asking this.