Created
March 25, 2012 07:10
-
-
Save ispern/2192058 to your computer and use it in GitHub Desktop.
WebStorm/PHPStormのCommand Line ToolsでSencha SDK Toolsを使うための設定ファイル
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| <?xml version="1.0" encoding="UTF-8"?> | |
| <framework xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | |
| xsi:noNamespaceSchemaLocation="schemas/frameworkDescriptionVersion1.1.xsd" name="sencha" | |
| invoke="/usr/local/sencha-sdk-tools/bin/sencha" alias="sencha" enabled="true" version="1"> | |
| <command> | |
| <name>app</name> | |
| <help><![CDATA[<div>Usage:</div><div> sencha app [action] [arguments...]</div><div><br></div><div>Description:</div><div> Resolve application dependencies and build for production</div><div><br></div><div>Available actions: (*) denotes required parameter</div><div><br></div><div> create (Alias to 'sencha generate app') Generate a new project with the recommended structure</div><div> </div><div> -n, --name * The namespace of the application to create. This will be used as the prefix for all your classes</div><div> -p, --path * The directory path to generate this application to.</div><div> -l, --library The library's build to develop your application with, either 'core' or 'all'. Defaults to 'core'</div><div> </div><div> resolve Generate a list of dependencies in the exact loading order for the given application. Note that the resolved paths are relative to the given application's HTML document</div><div> </div><div> -u, --uri * The URI to the application's HTML document</div><div> -o, --output * The file path to write the results to in JSON format.</div><div> </div><div> build Build the application at the current working directory to the given path</div><div> </div><div> -e, --environment * The build environment, either 'testing', 'package', 'production', or 'native'</div><div> + 'testing' is meant for QA prior to production. All JavaScript and CSS Files are bundled, but not minified</div><div> + 'package' creates a self-contained, re-distributable production build that </div><div> normally runs from local file system without the need for a web server</div><div> + 'production' creates a production build that is normally hosted on a web server and </div><div> serve multiple clients (devices). The build is offline-capable and has built-in </div><div> OTA delta updating feature</div><div> + 'native' first generates a 'package' build, then packages it as a native </div><div> application, ready to be deployed to native platforms</div><div> -d, --destination The directory path to build this application to. </div><div> If none given, the default path specified inside 'app.json' is used</div><div> -a, --archive The directory path where all previous builds were stored,</div><div> needed to generate deltas between updates (for production only). </div><div> If none given, the default path specified inside 'app.json' is used</div><div> </div><div> </div><div>For more information on a specific action, simply type:</div><div> sencha app [action]</div><div><br></div><div>For example:</div><div> sencha app create</div>]]></help> | |
| <params>action[=create|resolve|build] arguments[=null]</params> | |
| </command> | |
| <command> | |
| <name>fs</name> | |
| <help><![CDATA[<div>Usage:</div><div> sencha fs [action] [arguments...]</div><div><br></div><div>Description:</div><div> A set of useful utility actions to work with files. Most commonly used actions are: concat, minify, delta</div><div><br></div><div>Available actions: (*) denotes required parameter</div><div><br></div><div> concat Concatenate multiple files into one</div><div> </div><div> -f, --from * List of files to concatenate, comma-separated</div><div> -t, --to * The destination file to write concatenated content</div><div> </div><div> minify Minify a JavaScript file, currently support YUICompressor (default), Closure Compiler and UglifyJS</div><div> </div><div> -f, --from * Path to the file to minify</div><div> -t, --to * Path to the destination file to write minified content to.</div><div> -c, --compressor The name of the compressor to use, can be either: "yuicompressor", "uglifyjs" or "closurecompiler". Defaults to "yuicompressor"</div><div> </div><div> delta Generates deltas between two files in JSON format</div><div> </div><div> -f, --from * Path to the dictionary file</div><div> -t, --to * Path to the target file to compare to</div><div> -d, --delta * Path to a JSON file to write the delta content to</div><div> </div><div> </div><div>For more information on a specific action, simply type:</div><div> sencha fs [action]</div><div><br></div><div>For example:</div><div> sencha fs concat</div>]]></help> | |
| <params>action[=concat|minify|delta] arguments[=null]</params> | |
| </command> | |
| <command> | |
| <name>manifest</name> | |
| <help><![CDATA[<div>Usage:</div><div> sencha manifest [action] [arguments...]</div><div><br></div><div>Description:</div><div> Extract class metadata</div><div><br></div><div>Available actions: (*) denotes required parameter</div><div><br></div><div> create Generate a list of metadata for all classes found in the given directories</div><div> </div><div> -p, --path * The directory path(s) that contains all classes</div><div> -o, --output * The file path to write the results to in JSON format.</div><div> </div><div> </div><div>For more information on a specific action, simply type:</div><div> sencha manifest [action]</div><div><br></div><div>For example:</div><div> sencha manifest create</div>]]></help> | |
| <params>action[=create] arguments[=null]</params> | |
| </command> | |
| <command> | |
| <name>test</name> | |
| <help><![CDATA[<div>Usage:</div><div> sencha test [action] [arguments...]</div><div><br></div><div>Description:</div><div> Unit testing using Jasmine</div><div><br></div><div>Available actions: (*) denotes required parameter</div><div><br></div><div> run Run Jasmine's unit tests</div><div> </div><div> -p, --path * The *absolute* path to the directory that contains all spec files</div><div> -v, --verbose Whether to print extra information per each test run</div><div> -c, --color Whether to use color coding for output</div><div> </div><div> </div><div>For more information on a specific action, simply type:</div><div> sencha test [action]</div><div><br></div><div>For example:</div><div> sencha test run</div>]]></help> | |
| <params>action[=run] arguments[=null]</params> | |
| </command> | |
| <command> | |
| <name>generate</name> | |
| <help><![CDATA[<div>Usage:</div><div> sencha generate [action] [arguments...]</div><div><br></div><div>Description:</div><div> Automates the generation of projects and files</div><div><br></div><div>Available actions: (*) denotes required parameter</div><div><br></div><div> app Generate a new project with the recommended structure</div><div> </div><div> -n, --name * The namespace of the application to create. This will be used as the prefix for all your classes</div><div> -p, --path * The directory path to generate this application to.</div><div> -l, --library The library's build to develop your application with, either 'core' or 'all'. Defaults to 'core'.</div><div> + Use 'all' if your application make use of almost every class available in the whole framework</div><div> + Use 'core' if your application only make use of a portion of the framework. </div><div> When you deploy the application, it only includes exactly what it needs.</div><div> </div><div> model Generate a Model for an existing project</div><div> </div><div> -n, --name * The name of the Model to create</div><div> -f, --fields * The set of fields to add to the Model</div><div> </div><div> controller Generate a Controller for an existing project</div><div> </div><div> -n, --name * The name of the Controller to create</div><div> </div><div> profile Generate a Profile for an existing project</div><div> </div><div> -n, --name * The name of the Profile to create</div><div> </div><div> </div><div>For more information on a specific action, simply type:</div><div> sencha generate [action]</div><div><br></div><div>For example:</div><div> sencha generate app</div>]]></help> | |
| <params>action[=app|model|controller|profile] arguments[=null]</params> | |
| </command> | |
| <command> | |
| <name>package</name> | |
| <help><![CDATA[<div>Usage:</div><div> sencha package [action] [arguments...]</div><div><br></div><div>Description:</div><div> Packages a Sencha Touch 2 application for native app stores</div><div><br></div><div>Available actions: (*) denotes required parameter</div><div><br></div><div> generate Generates a Packager configuration JSON file</div><div> </div><div> -p, --path What to call the configuration file</div><div> </div><div> build Packages an app with the given configuration JSON file</div><div> </div><div> -p, --path What to call the configuration file</div><div> </div><div> run Packages and tries to run the application for the given configuration JSON file</div><div> </div><div> -p, --path What to call the configuration file</div><div> </div><div> </div><div>For more information on a specific action, simply type:</div><div> sencha package [action]</div><div><br></div><div>For example:</div><div> sencha package generate</div>]]></help> | |
| <params>action[=generate|build|run] arguments[=null]</params> | |
| </command> | |
| </framework> | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment