The documentation for the ExtReact product diverges somewhat from the
documentation of other Sencha products. The sections below describe
documentation for all products except where indicated as unique to
ExtReact
.
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.
ExtReact component classes list the configurable name prominently at the top of the API class doc followed by the fully-qualified class name.
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.
ExtReact component classes display
configuration options as props
ExtReact component classes do not list
properties as a dedicated member type, but rather as
read only
props
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.
All ExtReact props are bindable
unless decorated as immutable
Immutable ExtReact props may not be use as a configurable prop when instantiating a component
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
Or in the case of an ExtReact component class this
indicates a member of type prop
- 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.
ExtReact component classes do not hoist the getter /
setter methods into the prop. All methods will be described in the
Methods
section
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.
Tracks what records are currently selected in a databound widget. This class is mixed in to dataview and all subclasses.
Allow users to deselect a record in a DataView, List or Grid. Only applicable when
the Selectable's mode
is 'SINGLE'
.
Defaults to:
false
Allow users to deselect a record in a DataView, List or Grid. Only applicable when
the Selectable's mode
is 'SINGLE'
.
Defaults to:
false
Set to true
to deselect current selection when the container body is clicked.
Defaults to:
true
Sets the value of deselectOnContainerClick
deselectOnContainerClick : Boolean
Set to true
to deselect current selection when the container body is clicked.
Defaults to:
true
Sets the value of deselectOnContainerClick
deselectOnContainerClick : Boolean
Set to true
to disable selection.
This configuration will lock the selection model that the DataView uses.
Defaults to:
null
Sets the value of disableSelection
disableSelection : Boolean
Set to true
to disable selection.
This configuration will lock the selection model that the DataView uses.
Defaults to:
null
Sets the value of disableSelection
disableSelection : Boolean
Defaults to:
null
This was an internal function accidentally exposed in 1.x and now deprecated. Calling it has no effect
Deprecated since version 2.0.0
This method is deprecated.
Defaults to:
null
Returns the array of previously selected items.
The previous selection.
Deprecated since version 2.0.0
This method is deprecated.
Sets the value of lastSelected
lastSelected : Ext.data.Model
Set to true
to disable selection.
This configuration will lock the selection model that the DataView uses.
Defaults to:
null
Deprecated since version 2.0.0
Please use disableSelection instead.
Modes of selection.
Defaults to:
'SINGLE'
Returns the value of mode
'SINGLE' / 'SIMPLE' / 'MULTI'
Modes of selection.
Defaults to:
'SINGLE'
Returns the value of mode
'SINGLE' / 'SIMPLE' / 'MULTI'
Remove records from the selection when they are removed from the store.
Important: When using paging or a
Ext.data.BufferedStore, records which are cached in the Store's
data collection may be removed from the Store
when pages change, or when rows are scrolled out of view. For this reason pruneRemoved
should be set to false
when using a buffered Store.
Also, when previously pruned pages are returned to the cache, the records objects in the page will be new instances, and will not match the instances in the selection model's collection. For this reason, you MUST ensure that the Model definition's idProperty references a unique key because in this situation, records in the Store have their IDs compared to records in the SelectionModel in order to re-select a record which is scrolled back into view.
Defaults to:
true
Remove records from the selection when they are removed from the store.
Important: When using paging or a Ext.data.BufferedStore,
records which are cached in the Store's data collection may be removed from the Store when pages change,
or when rows are scrolled out of view. For this reason pruneRemoved
should be set to false
when using a buffered Store.
Also, when previously pruned pages are returned to the cache, the records objects in the page will be new instances, and will not match the instances in the selection model's collection. For this reason, you MUST ensure that the Model definition's idProperty references a unique key because in this situation, records in the Store have their IDs compared to records in the SelectionModel in order to re-select a record which is scrolled back into view.
Defaults to:
true
One or more names of config properties that this component should publish to its ViewModel. Generally speaking, only properties defined in a class config block (including ancestor config blocks and mixins) are eligible for publishing to the viewModel. Some components override this and publish their most useful configs by default.
Note: We'll discuss publishing properties not found in the config block below.
Values determined to be invalid by component (often form fields and model validations) will not be published to the ViewModel.
This config uses the reference
to determine the name of the data
object to place in the ViewModel
. If reference
is not set then this config
is ignored.
By using this config and reference
you can bind configs between
components. For example:
...
items: [{
xtype: 'textfield',
reference: 'somefield', // component's name in the ViewModel
publishes: 'value' // value is not published by default
},{
...
},{
xtype: 'displayfield',
bind: 'You have entered "{somefield.value}"'
}]
...
Classes must provide this config as an Object:
Ext.define('App.foo.Bar', {
publishes: {
foo: true,
bar: true
}
});
This is required for the config system to properly merge values from derived classes.
For instances this value can be specified as a value as show above or an array or object as follows:
{
xtype: 'textfield',
reference: 'somefield',
publishes: [
'value',
'rawValue',
'dirty'
]
}
// This achieves the same result as the above array form.
{
xtype: 'textfield',
reference: 'somefield',
publishes: {
value: true,
rawValue: true,
dirty: true
}
}
In some cases, users may want to publish a property to the viewModel that is not found in a class config block. In these situations, you may utilize publishState if the property has a setter method. Let's use setFieldLabel as an example:
setFieldLabel: function(fieldLabel) {
this.callParent(arguments);
this.publishState('fieldLabel', fieldLabel);
}
With the above chunk of code, fieldLabel may now be published to the viewModel.
Defaults to:
{ selection: 1 }
A Ext.util.Collection instance, or configuration object used to create the collection of selected records.
Defaults to:
true
The selected record.
Defaults to:
null
Returns the currently selected records.
The selected records.
The selected record.
Defaults to:
null
Returns the currently selected records.
The selected records.
This object holds a map of config
properties that will update their binding
as they are modified. For example, value
is a key added by form fields. The
form of this config is the same as publishes
.
This config is defined so that updaters are not created and added for all bound properties since most cannot be modified by the end-user and hence are not appropriate for two-way binding.
Defaults to:
{ selection: 1 }
Deselects any currently selected records and clears all stored selections.
Deprecated since version 2.0.0
Please use deselectAll instead.
Deselects the given record(s). If many records are currently selected, it will only deselect those you pass in.
records : Number/Array/Ext.data.Model
The record(s) to deselect. Can also be a number to reference by index.
suppressEvent : Boolean
If true
the deselect
event will not be fired.
Deselects the given record(s). If many records are currently selected, it will only deselect those you pass in.
records : Number/Array/Ext.data.Model
The record(s) to deselect. Can also be a number to reference by index.
suppressEvent : Boolean
If true
the deselect
event will not be fired.
Deselects a record instance by record instance or index.
records : Ext.data.Model/Number
An array of records or an index.
suppressEvent : Boolean
Set to false
to not fire a deselect event.
Deprecated since version 2.0.0
Please use deselect instead.
Selects a set of multiple records.
records : Object
keepExisting : Object
suppressEvent : Object
Selects a record instance by record instance or index.
records : Ext.data.Model/Number
An array of records or an index.
keepExisting : Boolean
suppressEvent : Boolean
Set to false
to not fire a select event.
Deprecated since version 2.0.0
Please use select instead.
Selects a single record.
record : Object
suppressEvent : Object
Returns the number of selections.
Deprecated since version 2.0.0
Please use getSelectionCount instead.
Returns the selection mode currently used by this Selectable.
The current mode.
Deprecated since version 2.0.0
Please use getMode instead.
Returns the currently selected records.
The selected records.
Returns true
if the Selectable is currently locked.
True if currently locked
Deprecated since version 2.0.0
Please use getDisableSelection instead.
Returns true
if the specified row is selected.
record : Ext.data.Model/Number
The record or index of the record to check.
Returns true
if the specified row is selected.
record : Ext.data.Model/Number
The record or index of the record to check.
Respond to selection. Call the onItemSelect template method
selectedCollection : Object
adds : Object
Respond to deselection. Call the onItemDeselect template method
selectedCollection : Object
chunk : Object
Adds the given records to the currently selected set.
records : Ext.data.Model/Array/Number
The records to select.
keepExisting : Boolean
If true
, the existing selection will be added to
(if not, the old selection is replaced).
suppressEvent : Boolean
If true
, the select
event will not be fired.
Adds the given records to the currently selected set.
records : Ext.data.Model/Array/Number
The records to select.
keepExisting : Boolean
If true
, the existing selection will be added to (if not, the old selection is replaced).
suppressEvent : Boolean
If true
, the select
event will not be fired.
Selects all records.
silent : Boolean
true
to suppress all select events.
Selects all records.
silent : Boolean
true
to suppress all select events.
Selects a range of rows if the selection model
Ext.mixin.Selectable#getDisableSelection is not locked.
All rows in between startRecord
and endRecord
are also selected.
startRecord : Number
The index of the first row in the range.
endRecord : Number
The index of the last row in the range.
keepExisting : Boolean (optional)
true
to retain existing selections.
Selects a range of rows if the selection model Ext.mixin.Selectable#getDisableSelection is not locked.
All rows in between startRecord
and endRecord
are also selected.
startRecord : Number
The index of the first row in the range.
endRecord : Number
The index of the last row in the range.
keepExisting : Boolean (optional)
true
to retain existing selections.
Sets a record as the last focused record. This does NOT mean that the record has been selected.
newRecord : Ext.data.Record
oldRecord : Ext.data.Record
Sets a record as the last focused record. This does NOT mean that the record has been selected.
newRecord : Ext.data.Record
oldRecord : Ext.data.Record
Override members of this class. Overridden methods can be invoked via Ext.Base#callParent.
Ext.define('My.Cat', {
constructor: function() {
alert("I'm a cat!");
}
});
My.Cat.override({
constructor: function() {
alert("I'm going to be a cat!");
this.callParent(arguments);
alert("Meeeeoooowwww");
}
});
var kitty = new My.Cat(); // alerts "I'm going to be a cat!"
// alerts "I'm a cat!"
// alerts "Meeeeoooowwww"
Direct use of this method should be rare. Use Ext.define instead:
Ext.define('My.CatOverride', {
override: 'My.Cat',
constructor: function() {
alert("I'm going to be a cat!");
this.callParent(arguments);
alert("Meeeeoooowwww");
}
});
The above accomplishes the same result but can be managed by the Ext.Loader which can properly order the override and its target class and the build process can determine whether the override is needed based on the required state of the target class (My.Cat).
members : Object
The properties to add to this class. This should be specified as an object literal containing one or more properties.
this class
Fires when a selection changes.
this : Ext.mixin.Selectable
records : Ext.data.Model[]
The records whose selection has changed.
eOpts : Object
The options object passed to Ext.util.Observable.addListener.
Fires when a selection changes.
this : Ext.mixin.Selectable
records : Ext.data.Model[]
The records whose selection has changed.
eOpts : Object
The options object passed to Ext.util.Observable.addListener.