This article guides the plug-in developers on how to create Animate plug-ins to support custom platforms using Animate.
To build a custom platform support plug-in, developers require the Custom Platform Support Development Kit. Click here to download.
Click here to download a sample plug-in and use it as a reference for building a custom support platform support plug-in.
A plug-in consists of the following elements:
For an overview of the Custom Platform Support feature, see Custom Platform Support.
You can develop a custom platform support plug-in using one of the following methods:
Custom Platform Support plug-ins are packaged as .zxp files that can be installed with Animate. You can host the plug-in on the Adobe Add-ons page for users to download and install using the Creative Cloud application or distribute the plug-ins as .zxp packages to install them using the Manage Extensions utility.
A developer needs the following software to build a plug-in using the custom platform support development kit:
The custom platform support development kit contains the following elements:
For complete information about the APIs in the custom platform support and examples of how to use them to build your plug-in, see Custom Platform Support API Reference.
You can create a custom platform support plug-in as follows:
For example, the SampleCreateJS plug-in files are at SampleCreateJSPlatform\Plugin\SampleCreateJS\project\
You can generate a distributable package of the custom platform support plug-in as follows:
A typical ExtensionList tag looks as below:
<ExtensionList> <Extension Id="PluginID" Version="1.0" /> <Extension Id="PublishSettingsID" Version-"1.0" /> </ExtensionList>
This tag contains the list of extensions in the final ZXP package in which each extension has a unique string as its ID. In this case, the .dll or .plugin file created in the previous section is included in an extension. Then, the other extension is used for configuring the Publish Settings UI of the Publisher. In the sample, ExtensionList tag the extension with the extension ID PluginID contains the .dll/.plugin file and the extension with the ID PublishSettingsID configures the publish pettings UI of the publisher.
<DispatchInfoList> <Extension Id="PluginID"> <DispatchInfo > <Resources> <MainPath>./plugin/fcm.xml</MainPath> </Resources> <Lifecycle> <AutoVisible>true</AutoVisible> </Lifecycle> <UI> <Type>ModalDialog</Type> <Menu>CreateJS</Menu> <Geometry> <Size> <Height>200</Height> <Width>200</Width> </Size> </Geometry> </UI> </DispatchInfo> </Extension> <Extension Id="PublishSettingsID"> <DispatchInfo > <Resources> <MainPath>./index.html</MainPath> </Resources> <Lifecycle> <AutoVisible>true</AutoVisible> </Lifecycle> <UI> <Type>ModalDialog</Type> <Menu>Publish Settings</Menu> <Geometry> <Size> <Height>170</Height> <Width>486</Width> </Size> </Geometry> </UI> </DispatchInfo> </Extension> </DispatchInfoList>
<ExecutionEnvironment> <HostList> <Host Name="FLPR" Version="15.1" /> </HostList>. . . </ExecutionEnvironment>
You can distribute the custom platform support plug-in by hosting it on the Adobe Add-ons page and monetize it. Your plug-in package goes through an Adobe review and approval process before it is listed on the page. You can host a plug-in as follows:
Fill the following form if you want to send any questions, concerns, product bugs, or feature requests to the Animate product team: