Guide applies to: modern
CLI Reference
This guide is a reference of the Open Tooling CLI commands available through ExtGen and its underlying tools.
CLI Tools | Description |
---|---|
ext-gen app […] | App generation tool. |
ext-gen migrate […] | App dependency migration tool. |
ext-build generate […] | Sencha Cmd CLI proxy. |
ext-gen app CLI - Application Generation
Ext JS open tooling requires NodeJS and Java.
App Generation CLI Options
Here’s a list of the CLI options you could use to generate your application.
Example:
ext-gen app (-h) (-d) (-i) (-t 'template') (-m 'moderntheme') (-c 'classictheme') (-n 'name') (-f 'folder')
CLI Options | Alias | Description |
---|---|---|
-h | —help | show help (no parameters also shows help) |
-d | —defaults | show defaults for package.json |
-i | —interactive | run in interactive mode (question prompts will display) |
-t | —template | name for Ext JS template used for generate |
-c | —classictheme | theme name for Ext JS classic toolkit (not in Community Edition) |
-m | —moderntheme | theme name for Ext JS modern toolkit |
-n | —name | name for Ext JS generated app |
-f | —folder | folder name for Ext JS application (not implemented yet) |
-v | —verbose | verbose npm messages (for problems only) |
Available App Templates
There are several app templates to generate your application from. Set the --template
property with one of the options below.
Example:
ext-gen app --template universalmodern --moderntheme theme-material --name CoolUniversalApp
Templates | Target Platforms | Description |
---|---|---|
classicdesktop | Desktop | Classic toolkit desktop App template. |
classicdesktoplogin | Desktop | Classic toolkit desktop App with login template. |
moderndesktop | Dekstop | Modern toolkit desktop App template. |
moderndesktopminimal | Desktop | Modern toolkit with simple desktop App template. |
universalclassicmodern | Mobile & Desktop | Mobile Modern toolkit & Classic toolkit desktop App template. |
universalmodern | Mobile & Desktop | This is a modern and universal template. |
Available Themes
These themes are available in the ext-gen app generation. Set the --classictheme
or --moderntheme
properties with one of the options below.
Example:
ext-gen app --template universalmodern --moderntheme theme-material --name CoolUniversalApp
Theme Options | Available in Toolkit |
---|---|
Modern Toolkit Themes | |
theme-material | Modern Toolkit |
theme-ios | Modern Toolkit |
theme-neptune | Modern Toolkit |
theme-triton | Modern Toolkit |
Classic Toolkit Themes | |
theme-classic | Classic Toolkit |
theme-material | Classic Toolkit |
theme-neptune | Classic Toolkit |
theme-neptune-touch | Classic Toolkit |
theme-crisp | Classic Toolkit |
theme-crisp-touch | Classic Toolkit |
theme-triton | Classic Toolkit |
theme-graphite | Classic Toolkit |
theme-material | Classic Toolkit |
ext-gen migrate - Application Migration
ExtGen’s migrate command is a helpful utility that will migrate an existing ExtJS application built with Sencha Cmd to an ExtJS application that uses Open Tooling (ExtGen).
ext-gen migrate
Full documentation on ext-gen migrate
can be found here.
ext-build CLI
ExtBuild provides Sencha Cmd functionality in Sencha’s npm projects. Requires Node and Java.
Installation
- Install npm (we assume you have pre-installed node.js).
npm install -g @sencha/ext-build
Usage
CLI Reference
Structure
ext-build generate app (sdk) (template) (name) (path)
\ ext-build generate viewpackage (profile) (viewname)
Commands | Description |
---|---|
generate, gen, g | Create a new application or viewpackage |
application, app, a | Use with generate command to generate a new application |
viewpackage | Use with generate command to generate a new viewpackage |
migrate | Migrating existing Sencha Cmd apps to Open Tooling |
CLI Options | Description |
---|---|
—builds | selected build profile (—builds “desktop:modern,theme-material;phone:modern,theme-material;” is default) |
—debug | show debugging |
—force | (deletes application, if present, before generate app (BE CAREFUL WITH THIS!)) |
—sdk | (path to Ext JS sdk - currently required for gen app, no running from sdk folder…) |
—template | (name of app template to use - only one currently - universalmodern) |
profile | (name of build profile to generate the viewpackage in) |
viewname | (name of viewpackage |
Examples
// Generate an application, specifying the SDK version and template
ext-build generate app --sdk 'Ext/ext-7.0.0' --template 'universalmodern' MyApp ./MyApp
// Generate an application, specifying the SDK version and template
ext-build gen app -s 'Ext/ext-7.0.0' -t 'universalmodern' MyApp ./MyApp
eb g a -s 'Ext/ext-7.0.0' -t 'universalmodern' MyApp ./MyApp
// Generate a new viewpackage named "settings" for the desktop build profile (configured in app.json) in an existing application
ext-build generate viewpackage desktop settings
// Generate a new viewpackage named "detail" for the phone build profile (configured in app.json) in an existing application
ext-build generate viewpackage phone detail
For Command line help:
ext-build
or eb
Driving Sencha Cmd Directly with npx
The feature rich ecosystem many ExtJS users are familiar, Sencha Cmd, is still available in an ExtGen application.
Investigating the @sencha
packages inside of your node_modules
, you will see Sencha Cmd among other framework packages. Open up the cmd
package and you’ll find the Sencha Cmd binary. How do you use this binary from your application?
First, if you are familiar with Sencha Cmd you will recall that during installation you probably added Sencha Cmd to your $PATH
, wich the binary typically being installed in your user bin directory. An Npm project also has a bin, located at node_modules/.bin
. Inside of this folder you will see the binaries made available to your project through npm.
The npm community has created the npx package. Npx will check whether the requested binary is available via your $PATH or if it’s available within your project’s node_modules/.bin
.
To take advantage of old workflows, to or harness additional Sencha horsepower, you can use the npx package + sencha cmd CLI syntax directly from the root of your ExtGen application.
Npx Examples
app watch
// Sencha Cmd
sencha app watch desktop
// Npx + Sencha Cmd
npx sencha app watch desktop
compile
// Sencha Cmd
sencha compile -classpath=js exclude -not -namespace Ext and concat ext-all-dev.js
// Npx + Sencha Cmd
npx sencha compile -classpath=js exclude -not -namespace Ext and concat ext-all-dev.js
Summary
In brief, nearly all of the same Sencha Cmd functionaly you may be previously used to can still be accessed by simply prepending your Sencha Cmd CLI syntax with the npx
directive.