|
| | allowDomMove : Boolean Whether the component can move the Dom node when rendering (defaults to true). | Component |
| | anchor : StringNote: this config is only used when this Component is rendered
+by a Container which has been configured to use an Anc... Note: this config is only used when this Component is rendered
+by a Container which has been configured to use an AnchorLayout
+based layout manager, for example:
+ See Ext.layout.AnchorLayout.anchor also. | Component |
| | applyTo : MixedSpecify the id of the element, a DOM element or an existing Element corresponding to a DIV
+that is already present in... Specify the id of the element, a DOM element or an existing Element corresponding to a DIV
+that is already present in the document that specifies some structural markup for this
+component.
+- Description :
+When applyTo is used, constituent parts of the component can also be specified
+by id or CSS class name within the main element, and the component being created may attempt
+to create its subcomponents from that markup if applicable.
+
+- Notes :
+When using this config, a call to render() is not required.
+If applyTo is specified, any value passed for renderTo will be ignored and the target
+element's parent node will automatically be used as the component's container.
+ | Component |
| | autoEl : MixedA tag name or DomHelper spec used to create the Element which will
+encapsulate this Component.
+You do not normally ne... A tag name or DomHelper spec used to create the Element which will
+encapsulate this Component.
+ You do not normally need to specify this. For the base classes Ext.Component, Ext.BoxComponent,
+and Ext.Container, this defaults to 'div'. The more complex Ext classes use a more complex
+DOM structure created by their own onRender methods.
+ This is intended to allow the developer to create application-specific utility Components encapsulated by
+different DOM elements. Example usage: {
+ xtype: 'box',
+ autoEl: {
+ tag: 'img',
+ src: 'http://www.example.com/example.jpg'
+ }
+}, {
+ xtype: 'box',
+ autoEl: {
+ tag: 'blockquote',
+ html: 'autoEl is cool!'
+ }
+}, {
+ xtype: 'container',
+ autoEl: 'ul',
+ cls: 'ux-unordered-list',
+ items: {
+ xtype: 'box',
+ autoEl: 'li',
+ html: 'First list item'
+ }
+}
| Component |
| | autoHeight : BooleanTrue to use height:'auto', false to use fixed height (or allow it to be managed by its parent
+Container's layout mana... True to use height:'auto', false to use fixed height (or allow it to be managed by its parent
+Container's layout manager. Defaults to false.
+ Note: Although many components inherit this config option, not all will
+function as expected with a height of 'auto'. Setting autoHeight:true means that the
+browser will manage height based on the element's contents, and that Ext will not manage it at all.
+ If the browser is managing the height, be aware that resizes performed by the browser in response
+to changes within the structure of the Component cannot be detected. Therefore changes to the height might
+result in elements needing to be synchronized with the new height. Example: var w = new Ext.Window({
+ title: 'Window',
+ width: 600,
+ autoHeight: true,
+ items: {
+ title: 'Collapse Me',
+ height: 400,
+ collapsible: true,
+ border: false,
+ listeners: {
+ beforecollapse: function() {
+ w.el.shadow.hide();
+ },
+ beforeexpand: function() {
+ w.el.shadow.hide();
+ },
+ collapse: function() {
+ w.syncShadow();
+ },
+ expand: function() {
+ w.syncShadow();
+ }
+ }
+ }
+}).show();
| BoxComponent |
| | autoShow : BooleanTrue if the component should check for hidden classes (e.g. 'x-hidden' or 'x-hide-display') and remove
+them on render... True if the component should check for hidden classes (e.g. 'x-hidden' or 'x-hide-display') and remove
+them on render (defaults to false). | Component |
| | autoWidth : BooleanTrue to use width:'auto', false to use fixed width (or allow it to be managed by its parent
+Container's layout manage... True to use width:'auto', false to use fixed width (or allow it to be managed by its parent
+Container's layout manager. Defaults to false.
+ Note: Although many components inherit this config option, not all will
+function as expected with a width of 'auto'. Setting autoWidth:true means that the
+browser will manage width based on the element's contents, and that Ext will not manage it at all.
+ If the browser is managing the width, be aware that resizes performed by the browser in response
+to changes within the structure of the Component cannot be detected. Therefore changes to the width might
+result in elements needing to be synchronized with the new width. For example, where the target element is: <div id='grid-container' style='margin-left:25%;width:50%'></div>
+A Panel rendered into that target element must listen for browser window resize in order to relay its
+child items when the browser changes its width: var myPanel = new Ext.Panel({
+ renderTo: 'grid-container',
+ monitorResize: true, // relay on browser resize
+ title: 'Panel',
+ height: 400,
+ autoWidth: true,
+ layout: 'hbox',
+ layoutConfig: {
+ align: 'stretch'
+ },
+ defaults: {
+ flex: 1
+ },
+ items: [{
+ title: 'Box 1',
+ }, {
+ title: 'Box 2'
+ }, {
+ title: 'Box 3'
+ }],
+});
| BoxComponent |
| | clearCls : StringThe CSS class used to to apply to the special clearing div rendered
+directly after each form field wrapper to provide... The CSS class used to to apply to the special clearing div rendered
+directly after each form field wrapper to provide field clearing (defaults to
+'x-form-clear-left').
+ Note: this config is only used when this Component is rendered by a Container
+which has been configured to use the FormLayout layout
+manager (e.g. Ext.form.FormPanel or specifying layout:'form') and either a
+fieldLabel is specified or isFormField=true is specified.
+ See Ext.layout.FormLayout.fieldTpl also. | Component |
| | cls : StringAn optional extra CSS class that will be added to this component's Element (defaults to ''). This can be
+useful for ... An optional extra CSS class that will be added to this component's Element (defaults to ''). This can be
+useful for adding customized styles to the component or any of its children using standard CSS rules. | Component |
| | ctCls : StringAn optional extra CSS class that will be added to this component's container. This can be useful for
+adding customize... An optional extra CSS class that will be added to this component's container. This can be useful for
+adding customized styles to the container or any of its children using standard CSS rules. See
+Ext.layout.ContainerLayout.extraCls also.
+ Note: ctCls defaults to '' except for the following class
+which assigns a value by default:
+
+To configure the above Class with an extra CSS class append to the default. For example,
+for BoxLayout (Hbox and Vbox): ctCls: 'x-box-layout-ct custom-class'
+ | Component |
| | disabled : Boolean Render this component disabled (default is false). | Component |
| | disabledClass : String CSS class added to the component when it is disabled (defaults to 'x-item-disabled'). | Component |
| | fieldLabel : StringThe label text to display next to this Component (defaults to '').
+Note: this config is only used when this Component... The label text to display next to this Component (defaults to '').
+ Note: this config is only used when this Component is rendered by a Container which
+has been configured to use the FormLayout layout manager (e.g.
+Ext.form.FormPanel or specifying layout:'form').
+ Also see hideLabel and
+Ext.layout.FormLayout.fieldTpl.
+Example use: new Ext.FormPanel({
+ height: 100,
+ renderTo: Ext.getBody(),
+ items: [{
+ xtype: 'textfield',
+ fieldLabel: 'Name'
+ }]
+});
| Component |
| | height : NumberThe height of this component in pixels (defaults to auto).
+Note to express this dimension as a percentage or offset s... The height of this component in pixels (defaults to auto).
+ Note to express this dimension as a percentage or offset see Ext.Component.anchor. | BoxComponent |
| | hidden : BooleanRender this component hidden (default is false). If true, the
+ hide method will be called internally. | Component |
| | hideLabel : Booleantrue to completely hide the label element
+(label and separator). Defaults to false.
+By default, even if you do not sp... true to completely hide the label element
+(label and separator). Defaults to false.
+By default, even if you do not specify a fieldLabel the space will still be
+reserved so that the field will line up with other fields that do have labels.
+Setting this to true will cause the field to not reserve that space.
+ Note: see the note for clearCls.
+Example use: new Ext.FormPanel({
+ height: 100,
+ renderTo: Ext.getBody(),
+ items: [{
+ xtype: 'textfield'
+ hideLabel: true
+ }]
+});
| Component |
| | hideMode : StringHow this component should be hidden. Supported values are 'visibility'
+(css visibility), 'offsets' (negative offset p... How this component should be hidden. Supported values are 'visibility'
+(css visibility), 'offsets' (negative offset position) and 'display'
+(css display).
+ Note: the default of 'display' is generally preferred
+since items are automatically laid out when they are first shown (no sizing
+is done while hidden). | Component |
| | hideParent : BooleanTrue to hide and show the component's container when hide/show is called on the component, false to hide
+and show the... True to hide and show the component's container when hide/show is called on the component, false to hide
+and show the component itself (defaults to false). For example, this can be used as a shortcut for a hide
+button on a window by setting hide:true on the button when adding it to its parent container. | Component |
| | id : StringThe unique id of this component (defaults to an auto-assigned id).
+You should assign an id if you need to be able to ... The unique id of this component (defaults to an auto-assigned id).
+You should assign an id if you need to be able to access the component later and you do
+not have an object reference available (e.g., using Ext.getCmp).
+ Note that this id will also be used as the element id for the containing HTML element
+that is rendered to the page for this component. This allows you to write id-based CSS
+rules to style the specific instance of this component uniquely, and also to select
+sub-elements using this component's id as the parent.
+ Note: to avoid complications imposed by a unique id also see
+itemId and ref.
+ Note: to access the container of an item see ownerCt. | Component |
| | itemCls : StringAn additional CSS class to apply to the div wrapping the form item
+element of this field. If supplied, itemCls at th... An additional CSS class to apply to the div wrapping the form item
+element of this field. If supplied, itemCls at the field level will override
+the default itemCls supplied at the container level. The value specified for
+itemCls will be added to the default class ('x-form-item').
+ Since it is applied to the item wrapper (see
+Ext.layout.FormLayout.fieldTpl), it allows
+you to write standard CSS rules that can apply to the field, the label (if specified), or
+any other element within the markup for the field.
+ Note: see the note for fieldLabel.
+Example use: // Apply a style to the field's label:
+<style>
+ .required .x-form-item-label {font-weight:bold;color:red;}
+</style>
+
+new Ext.FormPanel({
+ height: 100,
+ renderTo: Ext.getBody(),
+ items: [{
+ xtype: 'textfield',
+ fieldLabel: 'Name',
+ itemCls: 'required' //this label will be styled
+ },{
+ xtype: 'textfield',
+ fieldLabel: 'Favorite Color'
+ }]
+});
| Component |
| | itemId : StringAn itemId can be used as an alternative way to get a reference to a component
+when no object reference is available. ... An itemId can be used as an alternative way to get a reference to a component
+when no object reference is available. Instead of using an id with
+Ext.getCmp, use itemId with
+Ext.Container.getComponent which will retrieve
+itemId's or id's. Since itemId's are an index to the
+container's internal MixedCollection, the itemId is scoped locally to the container --
+avoiding potential conflicts with Ext.ComponentMgr which requires a unique
+id.
+ var c = new Ext.Panel({ //
+ height: 300,
+ renderTo: document.body,
+ layout: 'auto',
+ items: [
+ {
+ itemId: 'p1',
+ title: 'Panel 1',
+ height: 150
+ },
+ {
+ itemId: 'p2',
+ title: 'Panel 2',
+ height: 150
+ }
+ ]
+})
+p1 = c.getComponent('p1'); // not the same as Ext.getCmp()
+p2 = p1.ownerCt.getComponent('p2'); // reference via a sibling
+ Also see id and ref.
+ Note: to access the container of an item see ownerCt. | Component |
| | labelSeparator : StringThe separator to display after the text of each
+fieldLabel. This property may be configured at various levels.
+The o... The separator to display after the text of each
+fieldLabel. This property may be configured at various levels.
+The order of precedence is:
+
+- field / component level
+- container level
+- layout level (defaults to colon ':')
+
+To display no separator for this field's label specify empty string ''.
+ Note: see the note for clearCls.
+ Also see hideLabel and
+Ext.layout.FormLayout.fieldTpl.
+Example use: new Ext.FormPanel({
+ height: 100,
+ renderTo: Ext.getBody(),
+ layoutConfig: {
+ labelSeparator: '~' // layout config has lowest priority (defaults to ':')
+ },
+ labelSeparator: '>>', // config at container level
+ items: [{
+ xtype: 'textfield',
+ fieldLabel: 'Field 1',
+ labelSeparator: '...' // field/component level config supersedes others
+ },{
+ xtype: 'textfield',
+ fieldLabel: 'Field 2' // labelSeparator will be '='
+ }]
+});
| Component |
| | labelStyle : StringA CSS style specification string to apply directly to this field's
+label. Defaults to the container's labelStyle val... A CSS style specification string to apply directly to this field's
+label. Defaults to the container's labelStyle value if set (e.g.,
+Ext.layout.FormLayout.labelStyle , or '').
+ Note: see the note for clearCls.
+ Also see hideLabel and
+Ext.layout.FormLayout.fieldTpl.
+Example use: new Ext.FormPanel({
+ height: 100,
+ renderTo: Ext.getBody(),
+ items: [{
+ xtype: 'textfield',
+ fieldLabel: 'Name',
+ labelStyle: 'font-weight:bold;'
+ }]
+});
| Component |
| | listeners : ObjectA config object containing one or more event handlers to be added to this
+object during initialization. This should ... A config object containing one or more event handlers to be added to this
+object during initialization. This should be a valid listeners config object as specified in the
+addListener example for attaching multiple handlers at once.
+ DOM events from ExtJs Components
+ While some ExtJs Component classes export selected DOM events (e.g. "click", "mouseover" etc), this
+is usually only done when extra value can be added. For example the DataView's
+click event passing the node clicked on. To access DOM
+events directly from a Component's HTMLElement, listeners must be added to the Element after the Component
+has been rendered. A plugin can simplify this step: // Plugin is configured with a listeners config object.
+// The Component is appended to the argument list of all handler functions.
+Ext.DomObserver = Ext.extend(Object, {
+ constructor: function(config) {
+ this.listeners = config.listeners ? config.listeners : config;
+ },
+
+ // Component passes itself into plugin's init method
+ init: function(c) {
+ var p, l = this.listeners;
+ for (p in l) {
+ if (Ext.isFunction(l[p])) {
+ l[p] = this.createHandler(l[p], c);
+ } else {
+ l[p].fn = this.createHandler(l[p].fn, c);
+ }
+ }
+
+ // Add the listeners to the Element immediately following the render call
+ c.render = c.render.createSequence(function() {
+ var e = c.getEl();
+ if (e) {
+ e.on(l);
+ }
+ });
+ },
+
+ createHandler: function(fn, c) {
+ return function(e) {
+ fn.call(this, e, c);
+ };
+ }
+});
+
+var combo = new Ext.form.ComboBox({
+
+ // Collapse combo when its element is clicked on
+ plugins: [ new Ext.DomObserver({
+ click: function(evt, comp) {
+ comp.collapse();
+ }
+ })],
+ store: myStore,
+ typeAhead: true,
+ mode: 'local',
+ triggerAction: 'all'
+});
| Observable |
| | margins : ObjectNote: this config is only used when this BoxComponent is rendered
+by a Container which has been configured to use the... Note: this config is only used when this BoxComponent is rendered
+by a Container which has been configured to use the BorderLayout
+or one of the two BoxLayout subclasses.
+ An object containing margins to apply to this BoxComponent in the
+format: {
+ top: (top margin),
+ right: (right margin),
+ bottom: (bottom margin),
+ left: (left margin)
+}
+ May also be a string containing space-separated, numeric margin values. The order of the
+sides associated with each value matches the way CSS processes margin values:
+
+- If there is only one value, it applies to all sides.
+- If there are two values, the top and bottom borders are set to the first value and the
+right and left are set to the second.
+- If there are three values, the top is set to the first value, the left and right are set
+to the second, and the bottom is set to the third.
+- If there are four values, they apply to the top, right, bottom, and left, respectively.
+
+ Defaults to: {top:0, right:0, bottom:0, left:0}
| BoxComponent |
| | overCls : StringAn optional extra CSS class that will be added to this component's Element when the mouse moves
+over the Element, and... An optional extra CSS class that will be added to this component's Element when the mouse moves
+over the Element, and removed when the mouse moves out. (defaults to ''). This can be
+useful for adding customized 'active' or 'hover' styles to the component or any of its children using standard CSS rules. | Component |
| | overflowText : String Text to be used for the menu if the item is overflowed. | Toolbar.Item |
| | pageX : Number The page level x coordinate for this component if contained within a positioning container. | BoxComponent |
| | pageY : Number The page level y coordinate for this component if contained within a positioning container. | BoxComponent |
| | plugins : Object/ArrayAn object or array of objects that will provide custom functionality for this component. The only
+requirement for a ... An object or array of objects that will provide custom functionality for this component. The only
+requirement for a valid plugin is that it contain an init method that accepts a reference of type Ext.Component.
+When a component is created, if any plugins are available, the component will call the init method on each
+plugin, passing a reference to itself. Each plugin can then call methods or respond to events on the
+component as needed to provide its functionality. | Component |
| | ptype : StringThe registered ptype to create. This config option is not used when passing
+a config object into a constructor. This ... The registered ptype to create. This config option is not used when passing
+a config object into a constructor. This config option is used only when
+lazy instantiation is being used, and a Plugin is being
+specified not as a fully instantiated Component, but as a Component config
+object. The ptype will be looked up at render time up to determine what
+type of Plugin to create.
+If you create your own Plugins, you may register them using
+ Ext.ComponentMgr.registerPlugin in order to be able to
+take advantage of lazy instantiation and rendering. | Component |
| | ref : StringA path specification, relative to the Component's ownerCt specifying into which
+ancestor Container to place a named r... A path specification, relative to the Component's ownerCt specifying into which
+ancestor Container to place a named reference to this Component.
+ The ancestor axis can be traversed by using '/' characters in the path.
+For example, to put a reference to a Toolbar Button into the Panel which owns the Toolbar: var myGrid = new Ext.grid.EditorGridPanel({
+ title: 'My EditorGridPanel',
+ store: myStore,
+ colModel: myColModel,
+ tbar: [{
+ text: 'Save',
+ handler: saveChanges,
+ disabled: true,
+ ref: '../saveButton'
+ }],
+ listeners: {
+ afteredit: function() {
+// The button reference is in the GridPanel
+ myGrid.saveButton.enable();
+ }
+ }
+});
+ In the code above, if the ref had been 'saveButton' the reference would
+have been placed into the Toolbar. Each '/' in the ref moves up one level from the
+Component's ownerCt. | Component |
| | region : StringNote: this config is only used when this BoxComponent is rendered
+by a Container which has been configured to use the... Note: this config is only used when this BoxComponent is rendered
+by a Container which has been configured to use the BorderLayout
+layout manager (e.g. specifying layout:'border').
+ See Ext.layout.BorderLayout also. | BoxComponent |
| | renderTo : MixedSpecify the id of the element, a DOM element or an existing Element that this component
+will be rendered into.
+Notes ... Specify the id of the element, a DOM element or an existing Element that this component
+will be rendered into.
+- Notes :
+Do not use this option if the Component is to be a child item of
+a Container. It is the responsibility of the
+ Container's layout manager
+to render and manage its child items. When using this config, a call to render() is not required.
+
+
+ See render also. | Component |
| | stateEvents : ArrayAn array of events that, when fired, should trigger this component to
+save its state (defaults to none). stateEvents ... An array of events that, when fired, should trigger this component to
+save its state (defaults to none). stateEvents may be any type
+of event supported by this component, including browser or custom events
+(e.g., ['click', 'customerchange']).
+ See stateful for an explanation of saving and
+restoring Component state. | Component |
| | stateId : StringThe unique id for this component to use for state management purposes
+(defaults to the component id if one was set, o... The unique id for this component to use for state management purposes
+(defaults to the component id if one was set, otherwise null if the
+component is using a generated id).
+ See stateful for an explanation of saving and
+restoring Component state. | Component |
| | stateful : BooleanA flag which causes the Component to attempt to restore the state of
+internal properties from a saved state on startu... A flag which causes the Component to attempt to restore the state of
+internal properties from a saved state on startup. The component must have
+either a stateId or id assigned
+for state to be managed. Auto-generated ids are not guaranteed to be stable
+across page loads and cannot be relied upon to save and restore the same
+state for a component.
+ For state saving to work, the state manager's provider must have been
+set to an implementation of Ext.state.Provider which overrides the
+set and get
+methods to save and recall name/value pairs. A built-in implementation,
+Ext.state.CookieProvider is available.
+ To set the state provider for the current page:
+ Ext.state.Manager.setProvider(new Ext.state.CookieProvider({
+ expires: new Date(new Date().getTime()+(1000*60*60*24*7)), //7 days from now
+}));
+ A stateful Component attempts to save state when one of the events
+listed in the stateEvents configuration fires.
+ To save state, a stateful Component first serializes its state by
+calling getState. By default, this function does
+nothing. The developer must provide an implementation which returns an
+object hash which represents the Component's restorable state.
+ The value yielded by getState is passed to Ext.state.Manager.set
+which uses the configured Ext.state.Provider to save the object
+keyed by the Component's stateId, or, if that is not
+specified, its id.
+ During construction, a stateful Component attempts to restore
+its state by calling Ext.state.Manager.get passing the
+stateId, or, if that is not specified, the
+id.
+ The resulting object is passed to applyState.
+The default implementation of applyState simply copies
+properties into the object, but a developer may override this to support
+more behaviour.
+ You can perform extra processing on state save and restore by attaching
+handlers to the beforestaterestore, staterestore,
+beforestatesave and statesave events. | Component |
| | style : StringA custom style specification to be applied to this component's Element. Should be a valid argument to
+Ext.Element.ap... A custom style specification to be applied to this component's Element. Should be a valid argument to
+ Ext.Element.applyStyles.
+ new Ext.Panel({
+ title: 'Some Title',
+ renderTo: Ext.getBody(),
+ width: 400, height: 300,
+ layout: 'form',
+ items: [{
+ xtype: 'textarea',
+ style: {
+ width: '95%',
+ marginBottom: '10px'
+ }
+ },
+ new Ext.Button({
+ text: 'Send',
+ minWidth: '100',
+ style: {
+ marginBottom: '10px'
+ }
+ })
+ ]
+});
| Component |
| | width : Number The width of the spacer in pixels (defaults to 2px via css style .x-toolbar .xtb-spacer). | Toolbar.Spacer |
| | x : Number The local x (left) coordinate for this component if contained within a positioning container. | BoxComponent |
| | xtype : StringThe registered xtype to create. This config option is not used when passing
+a config object into a constructor. This ... The registered xtype to create. This config option is not used when passing
+a config object into a constructor. This config option is used only when
+lazy instantiation is being used, and a child item of a Container is being
+specified not as a fully instantiated Component, but as a Component config
+object. The xtype will be looked up at render time up to determine what
+type of child Component to create.
+The predefined xtypes are listed here.
+
+If you subclass Components to create your own Components, you may register
+them using Ext.ComponentMgr.registerType in order to be able to
+take advantage of lazy instantiation and rendering. | Component |
| | y : Number The local y (top) coordinate for this component if contained within a positioning container. | BoxComponent |
PropertiesToolbar.Spacer -
Properties