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.
Ext.grid.filters.menu.*
Ext.grid.filters.Column
Ext.data.Query
Ext.util.Filter
This plugin enables user-defined filters for a grid.
In general an gridfilters plugin will be passed to the grid:
There are several menu subclasses that provide default rendering for various data types
Ext.grid.filters.menu.String: Renders for string input fields
These subclasses can be configured in columns as such:
columns: [
{text: 'First Name', dataIndex:'firstname'},
{text: 'Last Name', dataIndex:'lastname', filter: 'string'},
{text: 'seniority', dataIndex: 'seniority', filter: 'number'},
{text: 'Hired Month', dataIndex:'hired', filter: 'date'},
{text: 'Active', dataIndex:'active', filter: 'boolean'}
]
Menu items can also be customised as shown below:
columns: [
{
text: 'First Name',
dataIndex:'firstname'
},
{
text: 'Last Name',
filter: {
type: 'string',
menu: {
items: {
like: {
placeholder: 'Custom Like...'
}
}
}
}
},
{
text: 'Hired Month',
filter: {
type: 'date',
menu: {
items: {
lt: {
label: 'Custom Less than',
placeholder: 'Custom Less than...',
dateFormat: 'd-m-y'
},
gt: {
label: 'Custom Greater than',
placeholder: 'Custom Greater than...',
dateFormat: 'd-m-y'
},
eq: {
label: 'Custom On',
placeholder: 'Custom On...',
dateFormat: 'd-m-y'
}
}
}
}
},
{
text: 'seniority'
filter: {
type: 'number',
menu: {
items: {
lt: {
label: 'Custom Less than',
placeholder: 'Custom Less than...',
},
gt: {
label: 'Custom Greater than',
placeholder: 'Custom Greater than...',
},
eq: {
label: 'Custom Equal to',
placeholder: 'Custom Equal to...',
}
}
}
}
},
{
text: 'Active',
filter: {
type: 'boolean',
menu: {
items: {
yes: {
text: 'Custom True'
},
no: {
text: 'Custom False'
}
}
}
}
}
]
This config holds the current filter. This config is stateful.
Defaults to:
null
An identifier for the plugin that can be set at creation time to later retrieve the plugin using the getPlugin method. For example:
var panel = Ext.create({
xtype: 'panel',
plugins: [{
id: 'foo',
...
}]
});
// later on:
var plugin = panel.getPlugin('foo');
Available since: 6.2.0
The events and associated handlers to which to listen on the owner
.
Defaults to:
{ destroyable: true, storechange: 'onOwnerStoreChange' }
Sets the value of ownerListeners
ownerListeners : Object
The events and associated handlers to which to listen on the source
of the
connected store
. That is, these listeners are attached to the unfiltered
collection. When remoteFilter
is true
there is no unfiltered collection so
these listeners are attached to the only collection that exists (which is
filtered by the server).
Defaults to:
null
Sets the value of sourceListeners
sourceListeners : Object
This config specifies the config properties that will be persisted using the
Ext.state.Provider. If this config is set to true
, the
configs specified by statefulDefaults
will be assumed.
stateful: true
Otherwise, this config can be an array of strings of the properties to save:
stateful: [
'width',
'height',
'collapsed'
]
The above is equivalent to:
stateful: {
width: true,
height: true,
collapsed: true
}
Note: To be truly stateful, an id
or stateId
must also be assigned.
A stateful object will save its state when any of these config properties change value.
Defaults to:
false
The default set of stateful properties. The form of this config is the same as stateful except this config cannot be a Boolean.
This config is intended for classes to specify so that instances can simply
enable statefulness using stateful: true
.
Defaults to:
null
The unique id for this object to use for state management purposes.
Defaults to:
null
The events and associated handlers to which to listen on the store
of the
owner
.
Defaults to:
null
Sets the value of storeListeners
storeListeners : Object
This method is called before destroy
to ensure that this instance's stateful
properties are saved to persistent storage. Since this object is about to be
destroyed, this cannot be delayed.
Creates clone of the plugin.
overrideCfg : Object (optional)
Additional config for the derived plugin.
The destroy method is invoked by the owning Component at the time the Component is being destroyed.
Plugins that can be disconnected from their host component should implement this method.
Available since: 6.2.0
Returns the component to which this plugin is attached.
The owning host component.
Creates a state builder to access or edit this instance's state object. If this
instance has a getStatefulOwner
, the returned
builder will have a parent
reference that owner's state builder. This can be
an arbitrarily deep chain but does proceed all the way up to the root instance
(with no owner) since that is the instance that determines the ultimate state
storage key.
cache : Boolean (optional)
Pass true
to return a cached builder.
Defaults to: false
This method allows a class to specify an owning stateful object. This is used by Ext.plugin.Abstract to save their state as part of their owning Ext.Component.
The return value can be either a Stateful
object or an array whose first element is
a Stateful
object. This object's state will be stored inside the state object of
the returned Stateful
object. If an array is returned, the elements beyond the first
are sub-keys in the state object.
For example, Ext.plugin.Abstract implement this method like so:
getStatefulOwner: function() {
return [ this.cmp, 'plugins' ];
}
The effect of this is to produce a state object like so:
{
plugins: {
pluginId1: {
//...
}
}
}
In order for a child object's state to be saved and restored, all of its parents must
also be stateful (i.e., have a stateId
).
The init method is invoked to formally associate the host component and the plugin.
Subclasses should perform initialization and set up any requires links between the plugin and its host Component in their own implementation of this method.
host : Ext.Component
The host Component which owns this plugin.
This method is called to load state from the provided state
builder. This method
should return the config properties loaded from state
.
This method, like saveState
, can be overridden by derived classes:
loadState: function(state) {
var ret = this.callParent([ state ]);
if (ret.foo) {
// use custom data...
delete ret.foo; // remove it since it isn't a config
}
return ret;
}
When overriding this method, it is also likely necessary to override saveState
.
state : Ext.state.Builder
stateful : Object
The stateful properties as an object keyed by config name.
Saves the state of this instance to the persistence store. This method is called by the Ext.state.Provider when it is ready to save state to storage.
Returns this instance's state object from the persistence store. This object should contain config properties.
Saves the current state of this object to the provided state
builder. By default
this method saves the configs specified as stateful
.
This method can also be overridden by subclasses to store custom data directly to
the state
builder:
saveState: function(state) {
this.callParent([ state ]);
state.set('foo', 42);
}
When overriding this method, it is also likely necessary to override loadState
.
state : Ext.state.Builder
The state builder to which to save state.
stateful : Object
The stateful properties as an object keyed by config name.
Sets the host component to which this plugin is attached. For a plugin to be
removable without being destroyed, this method should be provided and be prepared
to receive null
for the component.
host : Ext.Component
The owning host component.
This method is called internally by initConfig
to apply whatever changes are
needed from persistent storage.
instanceConfig : Object
The base config object
configurator : Ext.Configurator
The config object to use.
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