Docs Help

Terms, Icons, and Labels

Many classes have shortcut names used when creating (instantiating) a class with a configuration object. The shortcut name is referred to as an alias (or xtype if the class extends Ext.Component). The alias/xtype is listed next to the class name of applicable classes for quick reference.

Access Levels

Framework classes or their members may be specified as private or protected. Else, the class / member is public. Public, protected, and private are access descriptors used to convey how and when the class or class member should be used.

Member Types

Member Syntax

Below is an example class member that we can disect to show the syntax of a class member (the lookupComponent method as viewed from the Ext.button.Button class in this case).

lookupComponent ( item ) : Ext.Component

Called when a raw config object is added to this container either during initialization of the items config, or when new items are added), or {@link #insert inserted.

This method converts the passed object into an instanced child component.

This may be overridden in subclasses when special processing needs to be applied to child creation.


item :  Object

The config object being added.


The component to be added.

Let's look at each part of the member row:

Member Flags

The API documentation uses a number of flags to further commnicate the class member's function and intent. The label may be represented by a text label, an abbreviation, or an icon.

Class Icons

- Indicates a framework class

- A singleton framework class. *See the singleton flag for more information

- A component-type framework class (any class within the Ext JS framework that extends Ext.Component)

- Indicates that the class, member, or guide is new in the currently viewed version

Member Icons

- Indicates a class member of type config

- Indicates a class member of type property

- Indicates a class member of type method

- Indicates a class member of type event

- Indicates a class member of type theme variable

- Indicates a class member of type theme mixin

- Indicates that the class, member, or guide is new in the currently viewed version

Class Member Quick-Nav Menu

Just below the class name on an API doc page is a row of buttons corresponding to the types of members owned by the current class. Each button shows a count of members by type (this count is updated as filters are applied). Clicking the button will navigate you to that member section. Hovering over the member-type button will reveal a popup menu of all members of that type for quick navigation.

Getter and Setter Methods

Getting and setter methods that correlate to a class config option will show up in the methods section as well as in the configs section of both the API doc and the member-type menus just beneath the config they work with. The getter and setter method documentation will be found in the config row for easy reference.

History Bar

Your page history is kept in localstorage and displayed (using the available real estate) just below the top title bar. By default, the only search results shown are the pages matching the product / version you're currently viewing. You can expand what is displayed by clicking on the button on the right-hand side of the history bar and choosing the "All" radio option. This will show all recent pages in the history bar for all products / versions.

Within the history config menu you will also see a listing of your recent page visits. The results are filtered by the "Current Product / Version" and "All" radio options. Clicking on the button will clear the history bar as well as the history kept in local storage.

If "All" is selected in the history config menu the checkbox option for "Show product details in the history bar" will be enabled. When checked, the product/version for each historic page will show alongside the page name in the history bar. Hovering the cursor over the page names in the history bar will also show the product/version as a tooltip.

Search and Filters

Both API docs and guides can be searched for using the search field at the top of the page.

On API doc pages there is also a filter input field that filters the member rows using the filter string. In addition to filtering by string you can filter the class members by access level and inheritance. This is done using the checkboxes at the top of the page.

The checkbox at the bottom of the API class navigation tree filters the class list to include or exclude private classes.

Clicking on an empty search field will show your last 10 searches for quick navigation.

API Doc Class Metadata

Each API doc page (with the exception of Javascript primitives pages) has a menu view of metadata relating to that class. This metadata view will have one or more of the following:

Expanding and Collapsing Examples and Class Members

Runnable examples (Fiddles) are expanded on a page by default. You can collapse and expand example code blocks individually using the arrow on the top-left of the code block. You can also toggle the collapse state of all examples using the toggle button on the top-right of the page. The toggle-all state will be remembered between page loads.

Class members are collapsed on a page by default. You can expand and collapse members using the arrow icon on the left of the member row or globally using the expand / collapse all toggle button top-right.

Desktop -vs- Mobile View

Viewing the docs on narrower screens or browsers will result in a view optimized for a smaller form factor. The primary differences between the desktop and "mobile" view are:

Viewing the Class Source

The class source can be viewed by clicking on the class name at the top of an API doc page. The source for class members can be viewed by clicking on the "view source" link on the right-hand side of the member row.

Sencha Cmd 6.x


What's New in Cmd 6.5 (EA)

We are very excited to announce the release of Cmd 6.5. In addition to continued improvements to core functionality, and support for all of our non-framework products, we're also adding support for:

  • ES6 (ECMA Script 2015)

  • Progressive Web Applications

Let's dig into these new additions!

ES6 (ECMAScript 2015) Support

The main addition to Cmd 6.5 is support for ES6 or ECMAScript 2015. This allows developers to utilize current JavaScript coding standards within their Ext JS applications. Cmd will also continue to support past coding conventions.

Note: A lot has changed in the JavaScript world. If you're new to ECMAScript 2015, check out this list of supported syntax.

Cmd 6.5 will even support ECMAScript 2015 for older versions of Sencha Frameworks. Supported versions include:

  • Ext JS 6

  • Ext JS 5

  • Ext JS 4.1.1a+

  • Touch 2.1.x+

Note: Ext JS 4.x supports IE6. You may need to set your language version to ES3 for complete transpilation coverage (more below).

While Cmd supports ECMAScript 2015, not all browsers do. That's why Cmd 6.5 also introduces a transpiler for non-compliant browsers.


Cmd is capable of transpiling your modern source code into an older style of Javascript. This means that Cmd can read code written with ES6 conventions, and produce the equivalent code for non-ES6 capable browsers.

Dev Build Support

Due to the nature of the transpiling process, it can only be performed on production builds. This means that only modern versions of the main browsers can support ECMAScript 2015 code in "Developer Mode".

These browsers include:

  • Chrome (also includes Android 6+)

  • Edge

  • Firefox

  • Safari

  • IOS10

Note: As long as the browser has 100% support for ES6, it is supported in Dev Mode.

Production Build Browser Support

Happily, our list of supported browsers is much greater once you've built a production version of your application. Browser support for production built applications includes:

  • Safari 6+

  • Firefox

  • IE8+

  • Chrome

  • Opera 15+

  • Safari / iOS 6+

  • Chrome / Android 4.1+

  • IE10+ / Win 8

Disabling the Transpiler

The transpiler is totally optional and can be disabled by specifying "ES6" as your supported levels. This is useful for developers who are not interested in supporting older browsers. Simply add this JS object to your build target's output as seen here:

"output": {
    "js": {
        "version": "ES6"

Cmd's JS version supports the following values:

  • ES3 : ECMASCRIPT Level 3
  • ES5 : ECMASCRIPT Level 5 (default)
  • ES5_STRICT : ECMASCRIPT Level 5 Strict
  • ES6 : ECMASCRIPT Level 6
  • ES6_STRICT : ECMASCRIPT Level 6 Strict

Note: For more information about which level of ES support is right for you, please check out this compatibility guide.

Progressive Web Applications

Cmd 6.5+ helps you turn any Ext JS app into a progressive web app.

Progressive web apps provide a native app experience using modern web technologies. Google offers an excellent introduction to progressive web apps:

Your First Progressive Web App

Cmd specifically allows developers to:

  • Display an app banner that invites Android users to install the app to their home screen.

  • Provide offline support via service-worker based caching. Only Chrome and Firefox currently support this. Edge support is coming soon.

For more information about Progressive Web Applications, check the new PWA guide.

Note: You must first have Node JS installed locally to use the Cmd Progressive Web App integrations.

Sencha Cmd 6.x

Ext JS
Sencha Test
Sencha Themer
IDE Plugins
Sencha Inspector
Sencha Fiddle
Offline Documentation

Sencha Test

2.0.1 2.0.0 1.0.3



Sencha Themer

1.1.0 1.0.2


4.x 3.x

IDE Plugins

IDE Plugins

Sencha Inspector

Sencha Inspector

Sencha Fiddle

Sencha Fiddle

Offline Documentation

Offline Documentation