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.
Fields are used to define the members of a Model. They aren't instantiated directly; instead, when we create a class that extends Ext.data.Model, it automatically creates Field instances for each field configured in a Ext.data.Model. For example, we might set up a model like this:
Ext.define('User', {
extend: 'Ext.data.Model',
fields: [
'name', 'email',
{ name: 'age', type: 'int' },
{ name: 'gender', type: 'string', defaultValue: 'Unknown' }
]
});
Four fields will have been created for the User Model - name, email, age and gender. Note that we specified a couple of different formats here; if we only pass in the string name of the field (as with name and email), the field is set up with the 'auto' type. It's as if we'd done this instead:
Ext.define('User', {
extend: 'Ext.data.Model',
fields: [
{ name: 'name', type: 'auto' },
{ name: 'email', type: 'auto' },
{ name: 'age', type: 'int' },
{ name: 'gender', type: 'string', defaultValue: 'Unknown' }
]
});
Fields come in various types. When declaring a field, the type property is used to
specify the type of Field derived class used to manage values.
The predefined set of types are:
When reading fields it is often necessary to convert the values received before using
them or storing them in records. To handle these cases there is the
convert method. This method is passed the received value (as
well as the current record instance, but see below) and it returns the value to carry
forward.
For auto fields there is no convert method. This is for
efficiency. For other field types, there are often convert methods. You can provide
a convert config when the field is defined like this:
{
name: 'timestamp',
convert: function (value) {
return new Date(value);
}
}
While this can be convenient, see below for details on defining Custom Types as that is often a better practice and avoids repeating these functions.
Note that when a defaultValue is specified, it will also be passed through to
convert (either to the convert method or to the
convert config).
In some cases fields are the result of a calculation from other fields. Historically
this was a second role for convert but that has some short
comings. The simpler solution is the calculate config.
Values produced by calculate and convert
are stored in the record as with any other field. In fact, if we define a calculated
"firstName" field and log out all of the data, we'll see this:
var ed = Ext.create('User', { name: 'Ed Spencer' });
console.log(ed.data);
//outputs this:
{
age: 0,
email: "",
firstName: "Ed", // calculated field
gender: "Unknown",
name: "Ed Spencer"
}
calculate {
name: 'firstName',
calculate: function (data) {
return data.name.split(' ')[0];
}
}
Using calculate is the simplest and safest way to define a
calculated field. The most important part of this is that, internally, the code of the
supplied function is parsed to extract its dependencies. In this case, the "name" field
is the only dependency. This means that "firstName" will only need to be recalculated
when "name" is modified.
Note: Fields used by the calculate method must be explicitly defined in the fields of the model.
convertFollowing is the equivalent technique using convert
{
name: 'firstName',
convert: function (value, record) {
return record.get('name').split(' ')[0];
},
depends: [ 'name' ]
}
When a convert function accepts a 2nd argument (a reference to
the record), it is considered a calculated field. If a depends
config is not provided then this field's dependencies are unknown. In this case, the
depends are provided as would be automatically determined with
the calculate config.
Fields modified with the set method will have their stored value set using the convert / calculate method when present.
For example:
Ext.define('MyApp.model.Employee', {
extend: 'Ext.data.Model',
fields: [{
name: 'salary',
convert: function (val) {
var startingBonus = val * .1;
return val + startingBonus;
}
}],
convertOnSet: false
});
var tina = Ext.create('MyApp.model.Employee', {
salary: 50000
});
console.log(tina.get('salary')); // logs 55000
tina.set('salary', 60000);
console.log(tina.get('salary')); // logs 60000
This default behavior can be disabled by setting the Model's
Ext.data.Model#cfg-convertOnSet config to false.
Note: convertOnSet false only prevents the convert / calculate call when the
set fieldName param matches the field's name. See
convertOnSet for additional details.
When a field's convert method processes values from the record
(vs. just the field's value), it is best to also provide a depends config as shown
above. Fields that provide a calculate method must follow the
proper form for using fields so that dependencies can be extracted.
Calculated fields are processed after other fields based on their dependencies. Fields
with convert methods that use the provided record that do not
specify a depends config are processed as a group after all other
fields since such converters can rely on anything in the record. The order of processing
these fields with respect to each other is unspecified and should not be relied upon.
To handle the inverse scenario of convert there is the serialize method. This
method is called to produce the value to send to a server based on the internal value
as would be returned from convert. In most cases, these methods should "round trip"
a value:
assertEqual(value, field.serialize(field.convert(value)));
By default, only Ext.data.field.Date fields have a serialize method.
Other types simply send their value unmodified.
Developers may create their own application-specific data types by deriving from this class. This is typically much better than applying multiple configuration values on field instances as these often become repetitive.
To illustrate, we define a "time" field type that stores a time-of-day represented as a number of minutes since Midnight.
Ext.define('App.field.Time', {
extend: 'Ext.data.field.Field',
alias: 'data.field.time',
timeFormat: 'g:i',
convert: function (value) {
if (value && Ext.isString(value)) {
var date = Ext.Date.parse(value, this.timeFormat);
if (!date) {
return null;
}
return (date.getHours() - 1) * 60 + date.getMinutes();
}
return value;
}
});
Custom field types can override the validate method or
provide a set of validators.
Ext.define('App.field.PhoneNumber', {
extend: 'Ext.data.field.Field',
alias: 'data.field.phonenumber',
// Match U.S. phone numbers for example purposes
validators: {
type: 'format',
matcher: /\d{3}\-\d{3}\-\d{4}/
}
});
Once the class is defined, fields can be declared using the new type (based on its
alias) like so:
Ext.define('App.model.PhoneCall', {
fields: [
{ name: 'startTime', type: 'time' },
{ name: 'phoneNumber', type: 'phonenumber' }
]
});
Ext JS | Terms of Use