
4.
In the MXML compiler configuration file, add configuration information to include metadata for the
Dashboards Default Property Sheet.
For example,
<?xml version="1.0"?>
<flex-config xmlns="http://www.adobe.com/2006/flex-config">
<compiler>
<!-- Add the Dashboards Component SDK framework to the Adobe Flex classpath. -->
<!-- Keep additional metadata needed for use with the Dashboards Default Property Sheet. -->
<keep-as3-metadata>
<name>Inspectable</name>
<name>Style</name>
<name>CxInspectableList</name>
</keep-as3-metadata>
</compiler>
</flex-config>
5.
Open a Command Prompt.
6.
Navigate to the directory that contains your top-level application MXML file.
For example, cd C:\Dashboards\sdk\samples\SalesFunnel\SalesFunnelSource\src
7.
Use the Adobe Flex MXML command-line compiler to compile your top-level application MXML file
into a release SWF.
For example, C:\Program Files (x86)\Adobe\Adobe Flash Builder
4\sdks\4.0.0\bin\mxmlc.exe" SalesFunnelSource.mxml -output
SalesFunnelSource.swf
A release version of the SWF is created and includes the metadata required to use the Dashboards
Default Property Sheet.
9.2 To create Dashboards add-on packages (.xlx files)
Although add-ons can contain multiple visual components, connections, and functions, the Add-on
Manager can only install or remove the entire package at once. It cannot add or remove individual items
within the package. If you expect that users might want to add or remove specific items in the add-on
individually, create an separate package for each item.
Note:
Information fields denoted by an asterisk (*) are mandatory.
1.
Start Dashboards Add-On Packager.
2.
Click the Details tab and enter the following information:
2013-05-0626
Packaging Adobe Flex Projects as Add-Ons
Comentarios a estos manuales