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.
We’re excited to announce the release of Sencha Ext JS 6.7 with major enhancements to modern toolkit. The Ext JS 6.7 Modern toolkit supports grid filtering, grid locking, virtual scrolling for infinite grid, material chip, multiselect combobox, and color picker. The Ext JS 6.7 classic toolkit have multiple component enhancements to grid, calendar, panel, charts, window, combobox, tabs, and dashboard. The Jetbrains, Eclipse and Visual studio plugins are updated to support latest version of IDEs.
New Modern features in this release include:
Grid filtering, so that end-user can display only those grid records that meet specified criteria
Locking Grid, so that end-user can lock columns or "freeze pane" similar to Excel.
Chip that can be used in common user experience tasks like making selection, filtering content, triggering actions.
Multiselect Combobox, so that end-user can see multiple selected values as tags in the combobox.
Multiselect Select, so that end-users can select multiple values in the select field.
Color Picker, so that end-user can bring up the color picker using color swatch, form field or color selector.
Ext JS tooling updates in this release include:
Ext Gen open tooling templates to support Ext JS 6.7
Sencha Cmd with enhanced developer control over application compression options
JetBrains IDE Plugin supporting latest 2018+ versions
Eclipse IDE plugin supporting latest Eclipse versions Neon, Oxygen and Photon
Visual Studio IDE plugin supporting Visual Studio 2017
4 Ext JS Examples with Ext JS 6.7 and open tooling
Ext JS 6.7 Modern Grid provides grid filtering, so that end-user can display only those grid records that meet specified criteria. Apart from text filter, grid column filter supports following grid filters:
Boolean grid filter that will allow you to create a filter selection that limits results to values matching true or false.
Date grid filter allows you to create a filter selection that limits results to values matching specific date constraints.
Number grid filter allows you to create a filter selection that limits results to values matching specific number constraints.
A Kitchensink example is provided that show all the capabilities of Grid filter plugin including ability to manage all filters globally.
Ext JS 6.7 Modern Grid provides Locking Grid, so that end-user can lock columns or "freeze pane" similar to Excel. The locking grid provides a column menu that will allow user an ability to lock a grid column on the left region or right region. The locking grid column menu will show current locked status.
Ext JS 6.7 provides compact material Chip that can be used in common user experience tasks like making selection, filtering content, triggering actions. The chip component view with thumbnail and text can be created as below. You can configure displayTpl to provide different chip views for desktop vs mobile.
chipView: { iconField: 'avatar', displayField: 'name', platformConfig: { '!phone': { displayTpl: '{name} ({email})' } } },
Ext JS 6.7 provides Multiselect Combobox, so that end-user can see multiple selected values as tags in the combobox. A standard comboBox is like a combination of a traditional HTML text input field and a select field. If the editable config is true, then the user is able to type freely into the field, and/or pick values from a dropdown selection list. The Multiselect combobox, in addition provides option for "multiselect: true" allowing end users select multiple values in combobox. The select values can be navigated using keyboard arrow keys and can be deleted with delete key.
Ext JS 6.7 also provides Multiselect Select, so that end-users can select multiple values in the select field.
Ext JS 6.7 provides Color Picker, so that end-user can bring up the color picker using color swatch, form field or color selector. The color picker provides way to select color using HSVA, RGB.
Ext JS 6.7 provides virtual scroller that allows for number of rows beyond browser’s normal scroll range. Virtual scrolling is used by default for all infinite lists and grids. This allows for a number of rows far greater than browser's normal maximum scroll range.
scrollable: {
type: 'virtual',
infinite: true // enable MAX_SAFE_INTEGER scroll
},
What’s New in Ext JS 6.7 Tooling
ExtGen 6.7 now contain updated templates for creating desktop as well as mobile applications that support Ext JS 6.7 framework. The templates allow you to use both classic and modern toolkit. You can create desktop and mobile application using just modern toolkit or create universal application with both classic and modern toolkit.
Sencha Cm 6.7 ships with upgraded closure compiler that enhances your control over compression options. Cmd 6.7 provides you options to easily change compression levels to enhance code obfuscation and reduce footprint size to meet your requirements. The closure compiler API provides different levels of compression and release notes include examples on using those options.
JetBrain IDE plugins are updated to support apps generated using ExtGen. The Code completion, code generation, code navigation, code inspection, code refactoring, documentation lookup are now supported for Ext Gen apps. The updated plugin supports latest JetBrains IDEs that include IntelliJ 2018+,WebStorm 2018+, PhpStorm 2018+, RubyMine 2018+, PyCharm 2018+.
Eclipse IDE plugin are updated to support apps generated using ExtGen. The Eclipse plugin now supports Eclipse IDEs Neon, Oxygen and Photon. The code completion, code generation, code navigation, documentation lookup are now supported for all new Eclipse IDEs.
Sencha Visual Studio Plugin is now supported for Visual Studio 2017 and it provides IntelliSense support for Ext JS. Visual Studio 2017 IDE Plugin support consistent code completion experience inside the IDE for:
Config, method, and property names for all Ext JS and user classes
Alias properties such as xtype, controller, viewModel, layout
Event names and listeners objects
Controller methods in listeners
Properties from the ViewModel in bind configs
To enable Ext JS code completion support, you will need to disable the VS2017 Javascript language service.
Ext JS 6.7 provides number of examples that are built using open tooling. You can use these apps to get quickly started with Ext JS 6.7 and open tooling
Full Stack Employee Directory (Coworkee) application - Github Repo
Full Stack Progressive Web App (PWA) Application - Github Repo
Modern Tutorial Sample Application - Github Repo
Quick Start Sample Application - Github Repo
Ext JS 6.7 include updates and enhancements to multiple components as well as bug fixes in both modern and classic toolkit. The Ext JS 6.7 classic toolkit have multiple enhancements to grid, calendar, panel, charts, window, combobox, tabs, and dashboard. Ext JS 6.7 has gone through extensive testing phases including automated testing with Sencha Test with more than thousand test cases.
Download the free 30-day trial of Sencha Ext JS 6.7 with open tooling
Read the getting started with open tooling and access API docs
View the Ext JS 6.7 examples on any device
Customers can use their Support portal login* to get access to Ext JS framework, cmd and all Ext JS npm packages
Note: npm requires you to replace @ in login with "..". For example, if your login to support portal is **[[email protected]m](mailto:[email protected]), your login to npm registry will be firstname.lastname..sencha.com. You can use your existing support portal password.