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.
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.
Public classes and class members are available for use by any other class or application code and may be relied upon as a stable and persistent within major product versions. Public classes and members may safely be extended via a subclass.
Protected class members are stable public
members intended to be used by the
owning class or its subclasses. Protected members may safely be extended via a subclass.
Private classes and class members are used internally by the framework and are not intended to be used by application developers. Private classes and members may change or be omitted from the framework at any time without notice and should not be relied upon in application logic.
static
label next to the
method name. *See Static below.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).
Let's look at each part of the member row:
lookupComponent
in this example)( item )
in this example)Ext.Component
in this case). This may be omitted for methods that do not
return anything other than undefined
or may display as multiple possible values
separated by a forward slash /
signifying that what is returned may depend on the
results of the method call (i.e. a method may return a Component if a get method calls is
successful or false
if unsuccessful which would be displayed as
Ext.Component/Boolean
).PROTECTED
in
this example - see the Flags section below)Ext.container.Container
in this example). The source
class will be displayed as a blue link if the member originates from the current class
and gray if it is inherited from an ancestor or mixed-in class.view source
in the example)item : Object
in the example).undefined
a "Returns" section
will note the type of class or object returned and a description (Ext.Component
in the
example)Available since 3.4.0
- not pictured in
the example) just after the member descriptionDefaults to: false
)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.
classInstance.method1().method2().etc();
false
is returned from
an event handler- 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
- 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
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.
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.
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.
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.
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:
Ext.button.Button
class has an alternate class name of Ext.Button
). Alternate class
names are commonly maintained for backward compatibility.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.
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:
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.
Themer 1.3.9 supports theming and building custom themes for Ext JS 7.3 applications.
Themer 1.3.8 supports theming and building custom themes for Ext JS 7.2 applications.
Themer 1.3.7 supports theming and build custom themes for Ext JS 7.1 applications.
Themer 1.3.7 supports theming ExtReact 7.1 applications.
Themer 1.3.7 supports theming ExtAngular 7.1 applications.
Themer 1.3.7 supports theming ExtWebComponents 7.1 applications.
Themer 1.3.6 supports theming and build custom themes for Ext JS 7.0 applications.
Themer 1.3.6 supports theming ExtReact 7.0 applications.
Themer 1.3.6 supports theming ExtAngular 7.0 applications.
Themer 1.3.6 supports theming ExtWebComponents 7.0 applications.
Themer 1.3.5 supports theming and building custom themes for Ext JS 6.7 applications.
Themer 1.3.5 supports theming ExtReact 6.7 applications. You can build Custom Themes for React apps with Themer 1.3.5 Note: You will need to restart “npm start” after creating new custom theme in your react app.
Themer 1.3.5 supports theming ExtAngular applications. You can build Custom Themes for Angular apps with Themer 1.3.5 Note: You will need to restart “npm start” after creating new custom theme in your Angular app.
We are very excited to announce the following additions.
Themer 1.3.4 now supports ExtGen 1.0.1. So you can create Ext JS 6.6 apps with ExtGen and theme with Themer 1.3.4
Themer 1.3.4 now supports ExtReact 6.6.2. So you can create ExtReact 6.6.2 apps and theme with Themer 1.3.4
We’re excited to announce the release of Sencha Themer 1.3.3, which adds support of ExtReact 6.6. ExtReact and all related packages are hosted on Sencha's private npm registry. To gain access to this registry, sign up for a trial of ExtReact.
What’s New
ExtReact 6.6 Support
Themer supports theming ExtReact 6.6 applications using the latest React 16.x framework and Web Pack 4 plugin. ExtReact components are themable without having to write any code, which is great for React developers. Material theme is popular amongst React developers and all ExtReact components have full support for Material theme. With Themer you can style new modern components - Time Panel, Time Field, Gauges with needles and visually create uniquely themed components for your React application.
ExtReact Application Generator Support
Themer supports theming applications created using ExtReact Application Generator that you can install using the below command:
npm install -g @sencha/ext-react-gen
ext-react-gen app --theme triton --name ThemerTritonApp
You can specify Material, Triton, iOS or Neptune as base theme while creating applications using ExtReact Application Generator. You can use Themer to create a new theme by selecting the path to your ExtReact generated app in Themer. To add additional themes to your application, you will need to install corresponding theme packages in your application. For example, to add the Material theme package to an app that is currently using the Triton theme, use the following command:
npm i @sencha/ext-modern-theme-material --save
Note:
Style ExtReact Components uniquely
Themer supports creating multiple visual renditions of the same ExtReact component using a prop called “ui”. The example below shows that you can create “text-field-ui” in Themer and use in your React application, as follows:
<Toolbar docked="top">
<SearchField
ui="text-field-ui"
ref={field => this.query = field}
placeholder="Search..."
onChange={this.onSearch.bind(this)}
/>
</Toolbar>
We’re excited to announce the release of Sencha Themer 1.3.2, which supports the latest Ext JS 6.6 framework and components, including the new Graphite theme, and ExtReact based applications. This release also supports Ext JS 6.6 applications created using npm and open tooling.
Note: **Cmd 6.5.1 or higher is required for Themer 1.3.2*
What’s New
Theme Ext JS 6.6 and applications created using open tooling
Ext JS 6.6 with npm and open tooling fundamentally changes how you build and create Ext JS apps. All Ext JS customers now have access to the Ext JS framework, components and themes available as npm packages that are hosted in the npm repository at npm.sencha.com. Themer 1.3.2 supports theming applications created using the new open tooling ExtGen and ExtBuild.
Once you create your application with ExtGen:
ext-gen app -i
You can use Themer to create a new theme by selecting the path to your generated app in hemer. To add additional themes to your application, you will need to install corresponding theme packages in your application. For example, to add the Triton theme package to an app currently using Material theme, use the following command:
npm i @sencha/ext-modern-theme-triton --save
Themer will show all available themes that are installed in your application as base themes. As you theme your app, the generated application will use the webpack development server so that any changes to the app will be immediately reflected in the browser.
You have the option to continue using Sencha Cmd and Fashion instead of the webpack development server. In such case, you will use:
npx sencha app watch -fashion
Note: You will need to restart "npm start" after creating the new theme within the application workspace.
Support for visually styling new Ext JS components – Time Panel, Time Field
Ext JS 6.6 now includes modern time field and time panel components that provide an analog time view based on material design specification. The Time Panel component has 80+ Sass variables and mixin options to customize it for unique styling. The Time Field has 90+ Sass variables and mixin options. Themer 1.3.2 makes it easy to theme the apps using these components without writing Sass code. You can visually style applications using graphical tools and rapidly create custom theme.
Support for customizing new accessible Graphite theme
Ext JS 6.6 includes a new beautiful graphite theme which is an accessible high-contrast theme and is designed to make applications that are easier for visually impaired users to view. The Graphite theme can be used out-of-the-box for your applications or can be extended using Themer 1.3.2 to create a customized look and feel. Each component can be individually customized to give you full control over the colors, fonts and paddings of the Graphite theme.
We are very excited to announce the following additions.
Themer now supports Ext JS 6.5.3, which includes new component, multiple enhacements, and bug fixes.
Please check out the What's New guide for more information about Ext JS 6.5.3.
Cmd 6.5.3 continues to improve on 6.5.3.
Please check out the What's New
guide for more information about Cmd JS 6.5.3.
We are pleased to announce the release of Themer 1.3.0. 1.3 provides many bug fixes and improvements, which you can review here. In addition to these updates, we are also very excited to announce the following additions.
Themer now supports Ext JS 6.5.1, which includes hundreds of bug fixes and continued improvements regarding Modern and Classic toolkit parity.
Please check out the What's New guide for more information about Ext JS 6.5.
The most requested feature for Themer is the ability to add 'local' fonts to your themes. These could be proprietary fonts you own, or you just simply want to serve the fonts from your server instead of from Google. Either way Themer now supports 'Local Fonts'. You can read more about Managing Web Fonts in Themer here.
Themer 1.3 improves it's interactions with your existing apps and workspaces, now supporting workspaces with multiple frameworks and better support for toolkit specific apps. You may also create toolkit specific themes.
For users who do not use Sencha Cmd to build your applications, Themer now provides an option to 'Export CSS'. This option will build the theme package and all of it's assets and provide a directory and CSS file to be included via normal methods.
Cmd 6.5.1 continues to improve on 6.5. One impactful change in Cmd 6.5.1 for Themer is a change in the API so Themer can now allow UIs to be added without changing the SASS namespace in your theme package. This means existing themes that rely on the namespace value will now be more compatible with Themer.
If a theme was generated with Themer 1.2.0 (with Cmd 6.5.0+), then shared via a git in some way, the themes will likely not be openable in Themer 1.3.0 as a critical file was included in .gitignore.
The best workaround is to have the original author place the correct theme.db
in the right place: [theme_dir]/.sencha/themer/theme.db
.
.gitignore
in workspace/app root and remove the .sencha
lineworkspace/app root/packages/local/theme_name/.sencha/themer/theme.db
Populate file with valid JSON that contains the following:
{
"settings": [{
"name": "toolkit",
"value": "[modern or classic -- pick the toolkit this theme should use]"
}, {
"name": "version",
"value": "1.2.0.41"
}
}