What is this? A command line tool written in node.js for creating, compiling, packaging, debugging, and deploying extensions for Adobe® Creative Suite®. It's easy as to use and as it is powerful.
It is designed to solve workflow problems and constraints that come from using Flash Builder. As an added bonus, projects created with this tool contain boilerplate to resolve strange platform bugs we've encountered.
We used to it to build our Creative Market Photoshop Extension.
curl http://npmjs.org/install.sh | sh
npm install -g csxs
To create a new project, make an empty folder and use the "create" target to set up an empty project that's ready to go for development. To compile a debug version and add it to Photoshop, use the "debug" target.
# create a folder for a project$ mkdir my-extension$ cd my-extension# create the project & start it$ csxs create$ csxs debug --launch
More information about building and publishing the extension will be listed in the "README.md" created with the project.
All project settings live in "csxs.json" (guide). The settings in this file are synthesized to various XML files needed by the Flex Compiler and Signing Tool during the build process.
|assets/||Icons for the panel and Adobe Extension Manager.|
|changes/||A directory containing individual changelog files, by version.|
|src/||Extension source code.|
|README.md||Getting started guide.|
|HISTORY.md||An aggregated list of changes generated by the "changelogs" target.|
|csxs.json||All project settings (in lieu of *.xml files).|
The following conditional compilation variables are automatically provided:
Custom variables can be set by adding them to the "properties" object in "csxs.json". The values must be scalar. The one exception to this is if you want different values for debug builds and release builds. In this case, provide an object with two properties: "debug" and "release".
XML and MXI files in the project are populated by the properties in "csxs.json" at build time. For complicated extensions, it might be necessary to make changes in these files. Any of the files in the "src/" folder can be safely edited. Template variables should follow handlebars syntax.
Automated deployment of releases is done with the "publish" target. The build tool will compile a release build,
package it as a *.zxp installer, and place it on S3 (along with a history of changes).
All that's needed is an S3 account. See the documentation on the
"s3" property to see how to
add S3 configuration.
$ csxs publish
|changes/||Contains changelogs by version and a "master.txt" file (an aggregated list).|
|update.xml||Update info read by Adobe Extension Manager.|
|update.json||Update info in JSON format.|
When running "publish", HEAD will be tagged with the version being deployed for reference. It is the equivalent of running:
$ git tag vX.X.X$ git push origin --tags
In the rare case that a project needs multiple configurations (i.e. multiple "csxs.json" files), you can specify the configuration file to use from the command line with the
$ csxs target --config=csxs_free.json$ csxs target --config=csxs_paid.json
If this option is not provided, "csxs.json" will be read by default.
Copyright © 2013 Creative Market
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at: http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.