Basic CEP functionality needed prior to migration to UXP

[danh]

Ingo Eichel asked me to post here the CEP features that UXP must support prior to E-Spec migrating to UXP.

1. Single code base for Illustrator, Photoshop and InDesign; we currently maintain a single code base for all 3 apps; we will not begin a migration until UXP supports a single code base for all three.
2. API to access the document’s XMP; XMP is the life blood of our extensions; UXP currently has No support for XMP.
3. Equal ability to create dialogs (panels); currently only a subset of HTML is supported in UXP.
4. Common support for event listeners (particularly Save and Save As)

[aschrader]

Hi Dan,
we have the same problem:

Activate plug-in when Photoshop is launched

We are currently working on a replacement of a CEP extension, that is part of our DAM Platform vjoon seven. This new UXP plug-in will listen to the document open and close events. Upon close, it will bring up modal dialogs to control the check-in process. We do not need a panel or command in any menu. To do so, we need our UXP plug-in to be started automatically when Photoshop is launched. With CEP this is no problem. Looking at your UXP reference for entry points, there are life cycle hooks …