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.
This class extends the dimension item to be able to provide additional settings in the configurator plugin.
The field name on the record from where this dimension extracts data.
Defaults to:
''
This text is visible in the pivot grid in the following cases:
the dimension is defined on the left axis. The pivot grid will generate one grid column per dimension and this header will go into the grid column header.
the dimension is defined on the aggregate. The pivot grid will generate one grid column per dimension per top axis label. If there are at least 2 aggregate dimensions then this header will be visible. When only one is defined the aggregate dimension header is replaced by the top axis label.
if the Ext.pivot.plugin.Configurator is used then this header will be visible in the axis panels.
Defaults to:
''
This is the function that should be used to aggregate when this is an aggregate dimension.
You can either provide a function name available in Ext.pivot.Aggregators or set your own function.
It's probably best to override Ext.pivot.Aggregators to add you own function and use that function name on this config. This way the stateless pivot will save this value.
Defaults to:
"sum"
Column alignment when this dimension is a left axis or aggregate dimension. Used by the generated columns.
Defaults to:
"left"
Default text to use when a group name is blank. This value is applied even if you set your own label renderer.
Defaults to:
"(blank)"
If this dimension is sortable, should we do a case sensitive sort?
Defaults to:
true
Sets the value of caseSensitiveSort
caseSensitiveSort : Boolean
Configuration object that will be used when the grid columns are generated. Beware that this object will be merged into each column generated for each aggregate and left axis dimensions.
Note: This works when the dimension is used either as a left axis or an aggregate dimension.
Defaults to:
null
If this dimension is sortable then this is the type of sorting.
Defaults to:
"ASC"
Style used during export by the Ext.pivot.plugin.Exporter. This style will be applied to the columns generated for the aggregate or left axis dimensions in the exported file.
You could define it as a single object that will be used by all exporters:
aggregate: [{
dataIndex: 'price',
header: 'Total',
aggregator: 'sum',
exportStyle: {
format: 'Currency',
alignment: {
horizontal: 'Right'
},
font: {
italic: true
}
}
}]
You could also define it as an array of objects, each object having a type that specifies by
which exporter will be used:
aggregate: [{
dataIndex: 'price',
header: 'Total',
aggregator: 'sum',
exportStyle: [{
type: 'html', // used by the `html` exporter
format: 'Currency',
alignment: {
horizontal: 'Right'
},
font: {
italic: true
}
},{
type: 'csv', // used by the `csv` exporter
format: 'General'
}]
}]
Or you can define it as an array of objects that has:
type key that is considered the style to use by all exporterstype key defined that are exceptions of the above rule aggregate: [{
dataIndex: 'price',
header: 'Total',
aggregator: 'sum',
exportStyle: [{
// no type defined means this is the default
format: 'Currency',
alignment: {
horizontal: 'Right'
},
font: {
italic: true
}
},{
type: 'csv', // only the CSV exporter has a special style
format: 'General'
}]
}]
Defaults to:
null
Returns the value of exportStyle
Sets the value of exportStyle
exportStyle : Ext.exporter.file.Style / Ext.exporter.file.Style[]
Provide a filter configuration to filter your axis items. This works only on left/top axis dimensions.
Example for a label filter:
{
dataIndex: 'year',
header: 'Year',
filter: {
type: 'label',
operator: '=',
value: 2012
}
}
Example for a value filter:
{
dataIndex: 'year',
header: 'Year',
filter: {
type: 'value',
operator: 'between',
value: [2012, 2015]
}
}
Example for a top 10 value filter:
{
dataIndex: 'year',
header: 'Year',
filter: {
type: 'value',
operator: 'top10',
dimensionId: 'value', // this is the id of an aggregate dimension
topType: 'items',
topOrder: 'bottom'
}
}
Defaults to:
null
Column flex when this dimension is a left axis or aggregate dimension. Used by the generated columns.
Defaults to:
0
This formatter will be attached to the grid column generated for this dimension.
Note: This works when the dimension is used either as a left axis or an aggregate dimension.
Read more about grid column formatters here.
Defaults to:
null
This function is used when the groups are generated for the axis. It will return the value that will uniquely identify a group on the axis.
ie: you have a Date field that you want to group by year. This renderer could return the year from that Date value.
The function receives one parameter and that is the record.
It will run using Ext.callback so you can also provide a String that resolves to the view controller.
Defaults to:
null
record : Ext.data.Model
Record used to extract the group value
Callback function or the name of the callback function to execute when labels are generated for this dimension.
Note: This works when the dimension is used as either left or top axis dimension.
Example:
{
xtype: 'pivot',
matrix: {
topAxis: [{
dataIndex: 'month'
labelRenderer: function(monthValue){
return Ext.Date.monthNames[monthValue];
}
}]
// ...
}
}
The above labelRenderer will convert the month value to a textual month name.
Defaults to:
null
value : Mixed
Value that needs to be formatted
The label value displayed in the pivot grid
Callback function or the name of the callback function that will be attached to the grid column generated for this dimension.
Note: This works when the dimension is used as either left axis or aggregate dimension.
The following example describes how columns are generated by the pivot grid:
{
xtype: 'pivot',
matrix: {
leftAxis: [{
dataIndex: 'country'
}],
topAxis: [{
dataIndex: 'year',
labelRenderer: function(v) {
return 'Year ' + v;
}
}],
aggregate: [{
dataIndex: 'value',
aggregator: 'sum',
renderer: function(value, metaData, record, rowIndex, colIndex, store, view){
metaData.tdCls = (value < 0) ? 'redCls' : 'greenCls';
return Ext.util.Format(value, '0,000.00');
}
},{
dataIndex: 'qty',
aggregator: 'sum',
renderer: function(value, metaData, record, rowIndex, colIndex, store, view){
metaData.tdCls = (value < 0) ? 'redCls' : 'greenCls';
return Ext.util.Format(value, '0.00');
}
}]
}
}
Let's say that we have records for the years 2015 and 2016. In this scenario the resulting grid will have:
Read more about grid column renderers here.
Defaults to:
null
Define special restrictions or configurations for this field.
Defaults to:
{}
Sets the value of settings
settings : Ext.pivot.plugin.configurator.FieldSettings
Should 0 values be displayed as blank? This config is used when this is an aggregate dimension.
Defaults to:
false
Sets the value of showZeroAsBlank
showZeroAsBlank : Boolean
Provide here your own sorting function for this dimension. If none is specified then the defaultSorterFn is used.
Defaults to:
null
Field name on the record used when sorting this dimension results. Defaults to dataIndex if none is specified.
Defaults to:
''
Collection of unique values on this dimension; each item has a "value" and a "display".
True to identify a dimension of an aggregate configuration.
Defaults to:
false
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
ExtReact | Terms of Use