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


Creating App Templates

You can create app templates to give yourself a head start on similarly structured products, as well as to share with others.

This guide gives instructions for creating custom app templates. See the using app templates guide for information about using these facilities in a project.

Note: app templates can only be used when creating a new project. You cannot start a project and then later import a template like you would a user extension.

Creating a Custom App Template

A custom app template can be created out of any valid Sencha Architect project. Typically, you would create a project that contains only the code that you want used in all projects that are based on this app template.

A good use for a custom app template would be to create login functionality that can be used in all projects that require the user to log into the company site. Sencha Architect includes app templates to create login functionality for Ext JS. You can start with one of these templates or write your own login program starting with a Blank Screen. Typically, you would customize the view to contain your company name, create and apply a custom theme that uses your corporate colors, and add hooks to your login infrastructure.

To illustrate this process, we are going to create a very simple Custom Template that is based on the Ext JS Login/Register template.

  • Launch Architect and Create a New Project.
  • Choose the Ext JS framework and select the "Login/Register" template from the "Basic" category.
  • With the "MainView" component selected in the App Inspector, double-click on the "Header" string at the top of the Canvas display and replace the text with "Please log into the MyCompany network".
  • Save the project as you would save any other Architect project.

Note: The screen displays the actual path where the project will be saved based on what you type in the "Project Name" field.

  • Click on "File" in the Menu Bar and select "Add Template".
  • Choose "Use Current Project" from the pop-up dialog box that is displayed.
  • A dialog box similar to the following is then displayed:

  • Enter a title, category and optionally a description for the template, then save.
  • The template will be saved to your local templates folder. You can view this location by going to

      Edit menu > Preferences > File > Templates  

This location can be changed at any time and templates will be automatically migrated to the new location. You may also copy/paste template folders into this folder at any time.

You may also edit items in the templates folder if need be.

You can create a custom app template from an Architect project archive file .xda on your system.

  • Click on "File" in the Menu Bar and select "Add Template".
  • Choose "Select File" from the pop-up dialog box that is displayed, then select the .xda file you want to use from the File Browser window that is displayed.
  • Fill out the pop-up dialog box for the Template.

To share an app template with other users, you may export it:

  • Select "Export Template" from the "File" menu, or "Export selected" from the Template Management drop-down.
  • Verify or correct the information in the pop-up menu to define the template name and file location, then click "Save".

This creates a .xdt file that you can share with other users.

Users can import templates as follows:

  • Download the file to the local file system.
  • From Architect, select the "File" menu > "Add Template".
  • Choose "Select File" from the pop-up dialog box that is displayed, then select the .xdt file you want to import.
  • You may edit the title, description and category if needed.
  • Click the "Save" button and Architect imports the template into your location templates folder.

The template will be saved to your locale templates folder. Once a template has been imported, it can be edited as needed.

Architect 4.3