The User interface and front end for Adobe Creative Cloud Extensions and plug-ins.
Adobe’s Common Extensibility Platform, or CEP, is a suite of technologies embedded in Adobe’s Creative Cloud (CC) desktop applications. CEP was originally known as CSXS—it first appeared as part of Adobe Creative Suite 4 in 2008.
CEP delivers a runtime environment that is integrated with the ExtendScript scripting support of the host application. CEP is implemented in Creative Cloud applications, including InDesign, Photoshop, Illustrator, Premiere Pro, and Dreamweaver.
Finally, CEP integrates the Adobe IPC Toolkit, an interprocess communications system for Adobe CC applications. Like CEP, the Adobe IPC Toolkit is enabled by PlugPlug. With the IPC Toolkit, you can, for example, control Photoshop or Illustrator from an InDesign extension.
It should be noted that CEP and ExtendScript are two distinct technologies that cannot be combined in the same source file. CEP and ExtendScript operate in distinct environments, with distinct APIs and use cases. ExtendScript is typically used for back-end automation and batch processing that runs in the context of a specific Adobe application, whereas CEP is typically used to create custom UI elements and front-end functionality that runs in a browser-like environment. However, ExtendScript can be called from a CEP extension using the evalScript method provided by the CEP extension APIs. This method allows you to run ExtendScript code within the Adobe application in which the CEP extension is running. The evalScript method takes two arguments: the script to run and a callback function to be called when the script has finished executing. A typical CEP extension directory structure would include the following main folders:
It is important to note that the <HostList> element is optional; if not provided, the extension will be compatible with all versions of the host application supported by the CEP version of the extension.