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 3


Using Device Profiles in Architect and Sencha Touch

With the wide range of devices available on the market, it has become increasingly important to allow users to create a different app experience for multiple devices. That's why we introduced Device Profiles in Sencha Touch. Now, you can also utilize them in Sencha Architect as well!

If you're unfamiliar with Device Profiles, you may want to read more about them here before proceeding:

Adding Profiles to the Application

To add Profile support to your application, you need to tell it about the Profiles and create subclasses for each. Let's get started by adding a profile to your application in four simple steps.

  1. Select the application node in the inspector


  2. Next, we'll add profiles as a custom configuration. All you need to do is type profiles: [] into the config pane's filter box and press Add.


  3. Now edit the profiles by clicking the edit array button, which looks like this:


  4. At this point you can add a string to the array using the editor. For this example, let's add "tablet".



Note: Pressing the up arrow at the top of the editor should give the class level view.


That's it! You have now successfully enabled profiles for your application. The next step is to add the profile class, Tablet.js.

Adding Profile Classes

To add a new profile class, simply add a JS resource from the toolbox for each profile you’d like to create.

Let's go ahead and create Tablet. After creation, set the url config as profile/Tablet.js. Now you have an empty javascript file so let’s go ahead and differentiate this class for its device.

In this guide, we will ask you to add the following code to Tablet.js:

Ext.define('MyApp.profile.Tablet', {
    extend: '',

    config: {
        controllers: ['Groups'],
        views: ['GroupAdmin'],
        models: ['MyApp.model.Group']

    isActive: function() {

Note: _This code is borrowed from the Sencha Touch Device Profiles Guide. Your code will differ greatly based on the functionality and layout you desire for your application._

Adding a Device Specific View

Next, let's add a specialized view. If you're unfamiliar with specialized views, you may want to check out the "Specializing Views" section in our Device Profiles guide: Device Profiles - Specializing Views

Ext.define('Mail.view.tablet.Main', {
    extend: 'Mail.view.Main',

    config: {
        title: 'Tablet-specific version'

Ext.define('Mail.view.Main', {
    extend: 'Ext.Panel',

    config: {
        title: 'Generic version',
        html: 'This is the main screen'

Next, we’ll need to use a Class as it extends Main.view.Main.

Note: We can add Mail.view.Main by by dragging it out from the toolbox.

Adding a Class


All you need to do for this step is drop "Class" on the Views tree node and it will become a view. Locate the extend config and edit it to be .view., or ‘Mail.view.Main’ in this example. Lastly, set the userClassName to ‘tablet.Main’ and you have a profile specific view!

For something as simple as changing the title in each profile, you would simply add title: ‘Tablet specific version’ to the filter field.

However, there are times when you may want to create a far more intricate and robust experience per device. In this case, you would want to use a JS Resource in the same way we did for the profile classes above.

Final Thoughts

With a couple tips and some imagination, a wonderful user experience with device profiles can be created for your application using Sencha Architect.

For questions and community support, please use the following forum post to collaborate: How do I use device profiles in Sencha Architect?

Architect 3