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, inheritance, and read only. 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.

Architect 4.3


Using App Templates

App templates and user extensions allow you to easily reuse code as well as share it with others. However, there are some key differences between the two:

  • App templates can be used only to start a project. User extensions can be incorporated into your project at any time during the development process.
  • Templates are used in totality whereas user extensions add components to your toolbox that can be included with or without other components from the user extension package.
  • Templates are created in Architect, whereas user extensions may contain JavaScript and/or CSS code that was created outside Sencha Architect.

Please note the following details about App templates:

  • App templates can only be used when first starting a project.
  • A project created from a template is not updated when the template itself is updated.
  • Users can create their own app templates. Read more about this in the Creating app templates guide.

Using App Templates

App templates are provided to streamline the process of starting a new project. Several common project types are included in the Sencha Architect package. You can add additional templates that you or someone else created.

When you first launch Architect, choose "Create New". You'll see a screen that allows you to choose the framework to use and then you may select an app template for your project.

  • Choose your desired framework.
  • Click on the arrow to the right of the framework name to select another version of the framework. When you do this, "Blank Project" is displayed.
  • Click "Blank Project" to enter the standard Architect development screen. You can click on "Blank Project" for the current framework as well if you want to begin your project without a template.
  • The available templates for each framework are grouped logically into "Basic", "Layouts", "Examples", and "Starter Apps". Links to each group are displayed in the left column. You can look through the available templates and select the one that is closest to what you need.
  • To see a Preview of a app template, click on the "Eye" icon that is displayed on the upper-right when you hover over the template.
  • Click on the app template that is close to what you need for your project.
  • Click the "Create" button in the lower right of the screen and Architect will set up a project for you that is based on this Template.
  • When you click on the "New Project" button on the toolbar, you will be taken to the template page you used to start the previous project.

These templates set up the application's structure, and may include views, controllers, models, stores, themes, etc. Generally, any building block that can be used in an Architect project can be included in a template.

You can then customize the template as appropriate to create your project.

You can always start development with a blank canvas by selecting "Blank Canvas".

Architect 4.3