/* This file is part of Ext JS 3.4 Copyright (c) 2011-2013 Sencha Inc Contact: http://www.sencha.com/contact GNU General Public License Usage This file may be used under the terms of the GNU General Public License version 3.0 as published by the Free Software Foundation and appearing in the file LICENSE included in the packaging of this file. Please review the following information to ensure the GNU General Public License version 3.0 requirements will be met: http://www.gnu.org/copyleft/gpl.html. If you are unsure which license is appropriate for your use, please contact the sales department at http://www.sencha.com/contact. Build date: 2013-04-03 15:07:25 */ Ext.data.JsonP.Ext_DatePicker({"alternateClassNames":[],"aliases":{"widget":["datepicker"]},"enum":null,"parentMixins":[],"tagname":"class","subclasses":[],"extends":"Ext.Component","uses":[],"html":"
Hierarchy
Ext.util.ObservableExt.ComponentExt.DatePickerFiles
A popup date picker. This class is used by the DateField class\nto allow browsing and selection of valid dates.
\n\n\nAll the string values documented below may be overridden by including an Ext locale file in\nyour page.
\n\nWhether the component can move the Dom node when rendering (defaults to true).
\nDefaults to: true
Specify the id of the element, a DOM element or an existing Element corresponding to a DIV\nthat is already present in the document that specifies some structural markup for this\ncomponent.
\n\n\nTrue if the component should check for hidden classes (e.g. 'x-hidden' or 'x-hide-display') and remove\nthem on render (defaults to false).
\nDefaults to: false
An array of events that, when fired, should be bubbled to any parent container.\nSee Ext.util.Observable.enableBubble.\nDefaults to [].\n\n
Defaults to: []
The text to display on the cancel button (defaults to 'Cancel'
)
Defaults to: 'Cancel'
The CSS class used to to apply to the special clearing div rendered\ndirectly after each form field wrapper to provide field clearing (defaults to\n'x-form-clear-left').
\n\n\nNote: this config is only used when this Component is rendered by a Container\n\n\n
which has been configured to use the FormLayout layout\nmanager (e.g. Ext.form.FormPanel or specifying layout:'form') and either a\nfieldLabel is specified or isFormField=true is specified.
See Ext.layout.FormLayout.fieldTpl also.
\n\nAn optional extra CSS class that will be added to this component's Element (defaults to ''). This can be\nuseful for adding customized styles to the component or any of its children using standard CSS rules.
\nOptional. Specify an existing HTML element, or the id
of an existing HTML element to use as the content\nfor this component.
layout
\nscheme that the Component may use. It is just HTML. Layouts operate on child items
.x-hidden
or the x-hide-display
CSS class to\nprevent a brief flicker of the content before it is rendered to the panel.An optional extra CSS class that will be added to this component's container. This can be useful for\nadding customized styles to the container or any of its children using standard CSS rules. See\nExt.layout.ContainerLayout.extraCls also.
\n\n\nNote: ctCls defaults to '' except for the following class\nwhich assigns a value by default:\n
ctCls: 'x-box-layout-ct custom-class'\n
\n\n\nAn array of textual day names which can be overriden for localization support (defaults to Date.dayNames)
\nAn array of textual day names which can be overriden for localization support (defaults to Date.dayNames)
\nRender this component disabled (default is false).
\nDefaults to: false
CSS class added to the component when it is disabled (defaults to 'x-item-disabled').
\nDefaults to: 'x-item-disabled'
An array of 'dates' to disable, as strings. These strings will be used to build a dynamic regular\nexpression so they are very powerful. Some examples:
\n\nNote that the format of the dates included in the array should exactly match the format config.\nIn order to support regular expressions, if you are using a date format that has '.' in it, you will have to\nescape the dot when restricting dates. For example: ['03\\.08\\.03'].
\nJavaScript regular expression used to disable a pattern of dates (defaults to null). The disabledDates\nconfig will generate this regex internally, but if you specify disabledDatesRE it will take precedence over the\ndisabledDates value.
\nThe tooltip text to display when the date falls on a disabled date (defaults to 'Disabled'
)
Defaults to: 'Disabled'
An array of days to disable, 0-based. For example, [0, 6] disables Sunday and Saturday (defaults to null).
\nThe tooltip to display when the date falls on a disabled day (defaults to 'Disabled'
)
Defaults to: 'Disabled'
The label text to display next to this Component (defaults to '').
\n\n\nNote: this config is only used when this Component is rendered by a Container which\n\n\n
has been configured to use the FormLayout layout manager (e.g.\nExt.form.FormPanel or specifying layout:'form').
Also see hideLabel and\nExt.layout.FormLayout.fieldTpl.
\n\n\nExample use:
\n\nnew Ext.FormPanel({\n height: 100,\n renderTo: Ext.getBody(),\n items: [{\n xtype: 'textfield',\n fieldLabel: 'Name'\n }]\n});\n
\n\nThe default date format string which can be overriden for localization support. The format must be\nvalid according to Date.parseDate (defaults to 'm/d/y'
).
Defaults to: 'm/d/y'
Optional. A function that will handle the select event of this picker.\nThe handler is passed the following parameters:
picker
: DatePickerdate
: Datetrue to completely hide the label element\n(label and separator). Defaults to false.\nBy default, even if you do not specify a fieldLabel the space will still be\nreserved so that the field will line up with other fields that do have labels.\nSetting this to true will cause the field to not reserve that space.
\n\n\nNote: see the note for clearCls.
Example use:
\n\nnew Ext.FormPanel({\n height: 100,\n renderTo: Ext.getBody(),\n items: [{\n xtype: 'textfield'\n hideLabel: true\n }]\n});\n
\n\nHow this component should be hidden. Supported values are 'visibility'\n(css visibility), 'offsets' (negative offset position) and 'display'\n(css display).
\n\n\nNote: the default of 'display' is generally preferred\n\n\n
since items are automatically laid out when they are first shown (no sizing\nis done while hidden).
\nDefaults to: 'display'
True to hide and show the component's container when hide/show is called on the component, false to hide\nand show the component itself (defaults to false). For example, this can be used as a shortcut for a hide\nbutton on a window by setting hide:true on the button when adding it to its parent container.
\nDefaults to: false
An HTML fragment, or a DomHelper specification to use as the layout element\ncontent (defaults to ''). The HTML content is added after the component is rendered,\nso the document will not contain this HTML at the time the render event is fired.\nThis content is inserted into the body before any configured contentEl is appended.
\nThe unique id of this component (defaults to an auto-assigned id).\nYou should assign an id if you need to be able to access the component later and you do\nnot have an object reference available (e.g., using Ext.getCmp).
\n\n\nNote that this id will also be used as the element id for the containing HTML element\nthat is rendered to the page for this component. This allows you to write id-based CSS\nrules to style the specific instance of this component uniquely, and also to select\nsub-elements using this component's id as the parent.
\n\n\nNote: to avoid complications imposed by a unique id also see\nitemId
and ref
.
Note: to access the container of an item see ownerCt
.
Note: this config is only used when this Component is rendered by a Container which\nhas been configured to use the FormLayout layout manager (e.g.\nExt.form.FormPanel or specifying layout:'form').
\n\n\nAn additional CSS class to apply to the div wrapping the form item\nelement of this field. If supplied, itemCls at the field level will override\nthe default itemCls supplied at the container level. The value specified for\nitemCls will be added to the default class ('x-form-item').
\n\n\nSince it is applied to the item wrapper (see\nExt.layout.FormLayout.fieldTpl), it allows\nyou to write standard CSS rules that can apply to the field, the label (if specified), or\nany other element within the markup for the field.
\n\n\nNote: see the note for fieldLabel.
Example use:
\n\n// Apply a style to the field's label:\n<style>\n .required .x-form-item-label {font-weight:bold;color:red;}\n</style>\n\nnew Ext.FormPanel({\n height: 100,\n renderTo: Ext.getBody(),\n items: [{\n xtype: 'textfield',\n fieldLabel: 'Name',\n itemCls: 'required' //this label will be styled\n },{\n xtype: 'textfield',\n fieldLabel: 'Favorite Color'\n }]\n});\n
\n\nAn itemId can be used as an alternative way to get a reference to a component\nwhen no object reference is available. Instead of using an id
with\nExt.getCmp, use itemId
with\nExt.Container.getComponent which will retrieve\nitemId
's or id's. Since itemId
's are an index to the\ncontainer's internal MixedCollection, the itemId
is scoped locally to the container --\navoiding potential conflicts with Ext.ComponentMgr which requires a unique\nid
.
var c = new Ext.Panel({ //\n height: 300,\n renderTo: document.body,\n layout: 'auto',\n items: [\n {\n itemId: 'p1',\n title: 'Panel 1',\n height: 150\n },\n {\n itemId: 'p2',\n title: 'Panel 2',\n height: 150\n }\n ]\n})\np1 = c.getComponent('p1'); // not the same as Ext.getCmp()\np2 = p1.ownerCt.getComponent('p2'); // reference via a sibling\n
\n\n\n\n\n\nNote: to access the container of an item see ownerCt.
\n\nThe separator to display after the text of each\nfieldLabel. This property may be configured at various levels.\nThe order of precedence is:\n
Note: see the note for clearCls.
Also see hideLabel and\nExt.layout.FormLayout.fieldTpl.
\n\n\nExample use:
\n\nnew Ext.FormPanel({\n height: 100,\n renderTo: Ext.getBody(),\n layoutConfig: {\n labelSeparator: '~' // layout config has lowest priority (defaults to ':')\n },\n labelSeparator: '>>', // config at container level\n items: [{\n xtype: 'textfield',\n fieldLabel: 'Field 1',\n labelSeparator: '...' // field/component level config supersedes others\n },{\n xtype: 'textfield',\n fieldLabel: 'Field 2' // labelSeparator will be '='\n }]\n});\n
\n\nA CSS style specification string to apply directly to this field's\nlabel. Defaults to the container's labelStyle value if set (e.g.,\nExt.layout.FormLayout.labelStyle , or '').
\n\n\nNote: see the note for clearCls
.
Also see hideLabel
and\nExt.layout.FormLayout.fieldTpl.
Example use:
\n\nnew Ext.FormPanel({\n height: 100,\n renderTo: Ext.getBody(),\n items: [{\n xtype: 'textfield',\n fieldLabel: 'Name',\n labelStyle: 'font-weight:bold;'\n }]\n});\n
\n\n(optional)
A config object containing one or more event handlers to be added to this\nobject during initialization. This should be a valid listeners config object as specified in the\naddListener example for attaching multiple handlers at once.
\n\nDOM events from ExtJs Components
\n\n\nWhile some ExtJs Component classes export selected DOM events (e.g. \"click\", \"mouseover\" etc), this\n\n\n
is usually only done when extra value can be added. For example the DataView's\nclick
event passing the node clicked on. To access DOM\nevents directly from a Component's HTMLElement, listeners must be added to the Element after the Component\nhas been rendered. A plugin can simplify this step:
// Plugin is configured with a listeners config object.\n// The Component is appended to the argument list of all handler functions.\nExt.DomObserver = Ext.extend(Object, {\n constructor: function(config) {\n this.listeners = config.listeners ? config.listeners : config;\n },\n\n // Component passes itself into plugin's init method\n init: function(c) {\n var p, l = this.listeners;\n for (p in l) {\n if (Ext.isFunction(l[p])) {\n l[p] = this.createHandler(l[p], c);\n } else {\n l[p].fn = this.createHandler(l[p].fn, c);\n }\n }\n\n // Add the listeners to the Element immediately following the render call\n c.render = c.render.createSequence(function() {\n var e = c.getEl();\n if (e) {\n e.on(l);\n }\n });\n },\n\n createHandler: function(fn, c) {\n return function(e) {\n fn.call(this, e, c);\n };\n }\n});\n\nvar combo = new Ext.form.ComboBox({\n\n // Collapse combo when its element is clicked on\n plugins: [ new Ext.DomObserver({\n click: function(evt, comp) {\n comp.collapse();\n }\n })],\n store: myStore,\n typeAhead: true,\n mode: 'local',\n triggerAction: 'all'\n});\n
\n\n\n\nMaximum allowable date (JavaScript date object, defaults to null)
\nMaximum allowable date (JavaScript date object, defaults to null)
\nThe error text to display if the maxDate validation fails (defaults to 'This date is after the maximum date'
)
Defaults to: 'This date is after the maximum date'
Minimum allowable date (JavaScript date object, defaults to null)
\nMinimum allowable date (JavaScript date object, defaults to null)
\nThe error text to display if the minDate validation fails (defaults to 'This date is before the minimum date'
)
Defaults to: 'This date is before the minimum date'
An array of textual month names which can be overriden for localization support (defaults to Date.monthNames)
\nAn array of textual month names which can be overriden for localization support (defaults to Date.monthNames)
\nThe header month selector tooltip (defaults to 'Choose a month (Control+Up/Down to move years)'
)
Defaults to: 'Choose a month (Control+Up/Down to move years)'
The next month navigation button tooltip (defaults to 'Next Month (Control+Right)'
)
Defaults to: 'Next Month (Control+Right)'
The text to display on the ok button (defaults to ' OK '
to give the user extra clicking room)
Defaults to: ' OK '
An optional extra CSS class that will be added to this component's Element when the mouse moves\nover the Element, and removed when the mouse moves out. (defaults to ''). This can be\nuseful for adding customized 'active' or 'hover' styles to the component or any of its children using standard CSS rules.
\nAn object or array of objects that will provide custom functionality for this component. The only\nrequirement for a valid plugin is that it contain an init method that accepts a reference of type Ext.Component.\nWhen a component is created, if any plugins are available, the component will call the init method on each\nplugin, passing a reference to itself. Each plugin can then call methods or respond to events on the\ncomponent as needed to provide its functionality.
\nThe previous month navigation button tooltip (defaults to 'Previous Month (Control+Left)'
)
Defaults to: 'Previous Month (Control+Left)'
The registered ptype to create. This config option is not used when passing\na config object into a constructor. This config option is used only when\nlazy instantiation is being used, and a Plugin is being\nspecified not as a fully instantiated Component, but as a Component config\nobject. The ptype will be looked up at render time up to determine what\ntype of Plugin to create.
\nIf you create your own Plugins, you may register them using\nExt.ComponentMgr.registerPlugin in order to be able to\ntake advantage of lazy instantiation and rendering.
A path specification, relative to the Component's ownerCt
\nspecifying into which ancestor Container to place a named reference to this Component.
The ancestor axis can be traversed by using '/' characters in the path.\nFor example, to put a reference to a Toolbar Button into the Panel which owns the Toolbar:
\n\n\nvar myGrid = new Ext.grid.EditorGridPanel({\n title: 'My EditorGridPanel',\n store: myStore,\n colModel: myColModel,\n tbar: [{\n text: 'Save',\n handler: saveChanges,\n disabled: true,\n ref: '../saveButton'\n }],\n listeners: {\n afteredit: function() {\n// The button reference is in the GridPanel\n myGrid.saveButton.enable();\n }\n }\n});\n
\n\n\nIn the code above, if the ref
had been 'saveButton'
\nthe reference would have been placed into the Toolbar. Each '/' in the ref
\nmoves up one level from the Component's ownerCt
.
Specify the id of the element, a DOM element or an existing Element that this component\nwill be rendered into.
\n\n\nSee render also.
\n\nThe scope (this
reference) in which the handler
\nfunction will be called. Defaults to this DatePicker instance.
False to hide the footer area containing the Today button and disable the keyboard handler for spacebar\nthat selects the current date (defaults to true
).
Defaults to: true
Day index at which the week should begin, 0-based (defaults to 0, which is Sunday)
\nDefaults to: 0
An array of events that, when fired, should trigger this component to\nsave its state (defaults to none). stateEvents
may be any type\nof event supported by this component, including browser or custom events\n(e.g., ['click', 'customerchange']).
See stateful
for an explanation of saving and\nrestoring Component state.
The unique id for this component to use for state management purposes\n(defaults to the component id if one was set, otherwise null if the\ncomponent is using a generated id).
\n\nSee stateful
for an explanation of saving and\nrestoring Component state.
A flag which causes the Component to attempt to restore the state of\ninternal properties from a saved state on startup. The component must have\neither a stateId
or id
assigned\nfor state to be managed. Auto-generated ids are not guaranteed to be stable\nacross page loads and cannot be relied upon to save and restore the same\nstate for a component.
\n
For state saving to work, the state manager's provider must have been\nset to an implementation of Ext.state.Provider which overrides the\nset and get\nmethods to save and recall name/value pairs. A built-in implementation,\nExt.state.CookieProvider is available.
\nTo set the state provider for the current page:
\nExt.state.Manager.setProvider(new Ext.state.CookieProvider({\n expires: new Date(new Date().getTime()+(1000*60*60*24*7)), //7 days from now\n}));\n
\nA stateful Component attempts to save state when one of the events\nlisted in the stateEvents
configuration fires.
To save state, a stateful Component first serializes its state by\ncalling getState
. By default, this function does\nnothing. The developer must provide an implementation which returns an\nobject hash which represents the Component's restorable state.
The value yielded by getState is passed to Ext.state.Manager.set\nwhich uses the configured Ext.state.Provider to save the object\nkeyed by the Component's stateId
, or, if that is not\nspecified, its id
.
During construction, a stateful Component attempts to restore\nits state by calling Ext.state.Manager.get passing the\nstateId
, or, if that is not specified, the\nid
.
The resulting object is passed to applyState
.\nThe default implementation of applyState
simply copies\nproperties into the object, but a developer may override this to support\nmore behaviour.
You can perform extra processing on state save and restore by attaching\nhandlers to the beforestaterestore, staterestore,\nbeforestatesave and statesave events.
\n\nA custom style specification to be applied to this component's Element. Should be a valid argument to\nExt.Element.applyStyles.
\n\nnew Ext.Panel({\n title: 'Some Title',\n renderTo: Ext.getBody(),\n width: 400, height: 300,\n layout: 'form',\n items: [{\n xtype: 'textarea',\n style: {\n width: '95%',\n marginBottom: '10px'\n }\n },\n new Ext.Button({\n text: 'Send',\n minWidth: '100',\n style: {\n marginBottom: '10px'\n }\n })\n ]\n});\n
\n\nThe text to display on the button that selects the current date (defaults to 'Today'
)
Defaults to: 'Today'
A string used to format the message for displaying in a tooltip over the button that\nselects the current date. Defaults to '{0} (Spacebar)'
where\nthe {0}
token is replaced by today's date.
Defaults to: '{0} (Spacebar)'
An data
and\ntplWriteMode
configurations.
The Ext.(X)Template method to use when\nupdating the content area of the Component. Defaults to 'overwrite'\n(see Ext.XTemplate.overwrite
).
Defaults to: 'overwrite'
The registered xtype to create. This config option is not used when passing\na config object into a constructor. This config option is used only when\nlazy instantiation is being used, and a child item of a Container is being\nspecified not as a fully instantiated Component, but as a Component config\nobject. The xtype will be looked up at render time up to determine what\ntype of child Component to create.
\nThe predefined xtypes are listed here.
If you subclass Components to create your own Components, you may register\nthem using Ext.ComponentMgr.registerType in order to be able to\ntake advantage of lazy instantiation and rendering.
\nTrue if this component is disabled. Read-only.
\nThe Ext.Element which encapsulates this Component. Read-only.
\n\n\nThis will usually be a <DIV> element created by the class's onRender method, but\nthat may be overridden using the autoEl
config.
Note: this element will not be available until this Component has been rendered.
To add listeners for DOM events to this Component (as opposed to listeners\nfor this Component's own Observable events), see the listeners\nconfig for a suggestion, or use a render listener directly:
\n\n\nnew Ext.Panel({\n title: 'The Clickable Panel',\n listeners: {\n render: function(p) {\n // Append the Panel to the click handler's argument list.\n p.getEl().on('click', handlePanelClick.createDelegate(null, [p], true));\n },\n single: true // Remove the listener after first invocation\n }\n});\n
\n\n\nSee also getEl
\n\nprivate\nSet by other components to stop the picker focus being updated when the value changes.
\nDefaults to: true
default value used to initialise each date in the DatePicker\n(note: 12 noon was chosen because it steers well clear of all DST timezone changes)
\nDefaults to: 12
This Component's initial configuration specification. Read-only.
\nThe ancestor Container into which the ref reference was inserted if this Component\nis a child of a Container, and has been configured with a ref
.
True if this component has been rendered. Read-only.
\nDefaults to: false
Create a new DatePicker
\nThe config object
\nOverrides: Ext.Component.constructor
Adds a CSS class to the component's underlying element.
\nThe CSS class name to add
\nthis
\nAdds the specified events to the list of events which this Observable may fire.
\nEither an object with event names as properties with a value of true
\nor the first event name string if multiple event names are being passed as separate parameters.
. Event name if multiple event names are being passed as separate parameters.\nUsage:
\n\nthis.addEvents('storeloaded', 'storecleared');\n
\n\nAppends an event handler to this object.
\nThe name of the event to listen for.
\nThe method the event invokes.
\nThe scope (this
reference) in which the handler function is executed.\nIf omitted, defaults to the object which fired the event.
An object containing handler configuration.\nproperties. This may contain any of the following properties:
this
reference) in which the handler function is executed.\nIf omitted, defaults to the object which fired the event.\nCombining Options
\nUsing the options argument, it is possible to combine different types of listeners:
\n
\nA delayed, one-time listener.\n
myDataView.on('click', this.onClick, this, {\nsingle: true,\ndelay: 100\n});
\n\nAttaching multiple handlers in 1 call
\nThe method also allows for a single argument to be passed which is a config object containing properties\nwhich specify multiple handlers.\n
\n
myGridPanel.on({\n'click' : {\n fn: this.onClick,\n scope: this,\n delay: 100\n},\n'mouseover' : {\n fn: this.onMouseOver,\n scope: this\n},\n'mouseout' : {\n fn: this.onMouseOut,\n scope: this\n}\n});
\n\nOr a shorthand syntax:
\n
myGridPanel.on({\n'click' : this.onClick,\n'mouseover' : this.onMouseOver,\n'mouseout' : this.onMouseOut,\n scope: this\n});
\n\nApply this component to existing markup that is valid. With this function, no call to render() is required.
\nBubbles up the component/container heirarchy, calling the specified function with each component. The scope (this) of\nfunction call will be the scope provided or the current component. The arguments to the function\nwill be the args provided or the current component. If the function returns false at any point,\nthe bubble is stopped.
\nThe function to call
\nThe scope of the function (defaults to current node)
\nThe args to call the function with (default to passing the current component)
\nthis
\nClone the current component using the original config values passed into this instance by default.
\nA new config containing any properties to override in the cloned version.\nAn id property can be passed on this object, otherwise one will be generated to avoid duplicates.
\nclone The cloned copy of this component
\nDestroys this component by purging any event listeners, removing the component's element from the DOM,\nremoving the component from its Ext.Container (if applicable) and unregistering it from\nExt.ComponentMgr. Destruction is generally handled automatically by the framework and this method\nshould usually not need to be called directly.
\nDisable this component and fire the 'disable' event.
\nthis
\nEnables events fired by this Observable to bubble up an owner hierarchy by calling\nthis.getBubbleTarget()
if present. There is no implementation in the Observable base class.
This is commonly used by Ext.Components to bubble events to owner Containers. See Ext.Component.getBubbleTarget. The default\nimplementation in Ext.Component returns the Component's immediate owner. But if a known target is required, this can be overridden to\naccess the required target more quickly.
\n\n\nExample:
\n\n\nExt.override(Ext.form.Field, {\n // Add functionality to Field's initComponent to enable the change event to bubble\n initComponent : Ext.form.Field.prototype.initComponent.createSequence(function() {\n this.enableBubble('change');\n }),\n\n // We know that we want Field's events to bubble directly to the FormPanel.\n getBubbleTarget : function() {\n if (!this.formPanel) {\n this.formPanel = this.findParentByType('form');\n }\n return this.formPanel;\n }\n});\n\nvar myForm = new Ext.formPanel({\n title: 'User Details',\n items: [{\n ...\n }],\n listeners: {\n change: function() {\n // Title goes red if form has been modified.\n myForm.header.setStyle('color', 'red');\n }\n }\n});\n
\n\nFind a container above this component at any level by a custom function. If the passed function returns\ntrue, the container will be returned.
\nThe custom function to call with the arguments (container, this component).
\nThe first Container for which the custom function returns true
\nFind a container above this component at any level by xtype or class
\nThe xtype to check for this Component. Note that the the component can either be an instance\nor a component class:
\nFalse to check whether this Component is descended from the xtype (this is\nthe default), or true to check whether this Component is directly of the specified xtype.
\nThe first Container which matches the given xtype or class
\nFires the specified event with the passed parameters (minus the event name).
\n\n\nAn event may be set to bubble up an Observable parent hierarchy (See Ext.Component.getBubbleTarget)\nby calling enableBubble.
\n\nThe name of the event to fire.
\nVariable number of parameters are passed to handlers.
\nreturns false if any of the handlers return false otherwise it returns true.
\nprivate
\n\nTry to focus this component.
\nIf applicable, true to also select the text in this component
\nDelay the focus this number of milliseconds (true for 10 milliseconds)
\nthis
\nOverrides: Ext.Component.focus
Provides the link for Observable's fireEvent method to bubble up the ownership hierarchy.
\nthe Container which owns this Component.
\nReturns the Ext.Element which encapsulates this Component.
\n\n\nThis will usually be a <DIV> element created by the class's onRender method, but\nthat may be overridden using the autoEl config.
\n\n\nNote: this element will not be available until this Component has been rendered.
To add listeners for DOM events to this Component (as opposed to listeners\nfor this Component's own Observable events), see the listeners config for a suggestion,\nor use a render listener directly:
\n\n\nnew Ext.Panel({\n title: 'The Clickable Panel',\n listeners: {\n render: function(p) {\n // Append the Panel to the click handler's argument list.\n p.getEl().on('click', handlePanelClick.createDelegate(null, [p], true));\n },\n single: true // Remove the listener after first invocation\n }\n});\n
\n\nThe Element which encapsulates this Component.
\nReturns the id
of this component or automatically generates and\nreturns an id
if an id
is not defined yet:
'ext-comp-' + (++Ext.Component.AUTO_ID)\n
\n\nid
\nGets the xtype for this component as registered with Ext.ComponentMgr. For a list of all\navailable xtypes, see the Ext.Component header. Example usage:
\n\nvar t = new Ext.form.TextField();\nalert(t.getXType()); // alerts 'textfield'\n
\n\nThe xtype
\nReturns this Component's xtype hierarchy as a slash-delimited string. For a list of all\navailable xtypes, see the Ext.Component header.
\n\n\nIf using your own subclasses, be aware that a Component must register its own xtype\nto participate in determination of inherited xtypes.
\n\n\nExample usage:
\n\n\nvar t = new Ext.form.TextField();\nalert(t.getXTypes()); // alerts 'component/box/field/textfield'\n
\n\nThe xtype hierarchy string
\nChecks to see if this object has any listeners for a specified event
\nThe name of the event to check for
\nTrue if the event is being listened for, else false
\nHide this component. Listen to the 'beforehide' event and return\nfalse to cancel hiding the component. Fires the 'hide'\nevent after hiding the component. Note this method is called internally if\nthe component is configured to be hidden
.
this
\nMethod to establish a reference to a component.
\nReturns true if this component is visible.
\nTrue if this component is visible, false otherwise.
\nTests whether or not this Component is of a specific xtype. This can test whether this Component is descended\nfrom the xtype (default) or whether it is directly of the xtype specified (shallow = true).
\n\n\nIf using your own subclasses, be aware that a Component must register its own xtype\nto participate in determination of inherited xtypes.
\n\n\nFor a list of all available xtypes, see the Ext.Component header.
\n\n\nExample usage:
\n\n\nvar t = new Ext.form.TextField();\nvar isText = t.isXType('textfield'); // true\nvar isBoxSubclass = t.isXType('box'); // true, descended from BoxComponent\nvar isBoxInstance = t.isXType('box', true); // false, not a direct BoxComponent instance\n
\n\nThe xtype to check for this Component. Note that the the component can either be an instance\nor a component class:
\n\nvar c = new Ext.Component();\nconsole.log(c.isXType(c));\nconsole.log(c.isXType(Ext.Component));\n
\n\nFalse to check whether this Component is descended from the xtype (this is\nthe default), or true to check whether this Component is directly of the specified xtype.
\nTrue if this component descends from the specified xtype, false otherwise.
\nAdds listeners to any Observable object (or Elements) which are automatically removed when this Component\nis destroyed. Usage:
\n\n\nmyGridPanel.mon(myGridPanel.getSelectionModel(), 'selectionchange', handleSelectionChange, null, {buffer: 50});\n\n\n\n\n\n
or:
\n\n\nmyGridPanel.mon(myGridPanel.getSelectionModel(), {\n selectionchange: handleSelectionChange,\n buffer: 50\n});\n\n\n\n\n
The item to which to add a listener/listeners.
\nThe event name, or an object containing event name properties.
\nOptional. If the ename
parameter was an event name, this\nis the handler function.
Optional. If the ename
parameter was an event name, this\nis the scope (this
reference) in which the handler function is executed.
Optional. If the ename
parameter was an event name, this\nis the addListener options.
Removes listeners that were added by the mon method.
\nThe item from which to remove a listener/listeners.
\nThe event name, or an object containing event name properties.
\nOptional. If the ename
parameter was an event name, this\nis the handler function.
Optional. If the ename
parameter was an event name, this\nis the scope (this
reference) in which the handler function is executed.
Appends an event handler to this object (shorthand for addListener.)
\nThe type of event to listen for
\nThe method the event invokes
\nThe scope (this
reference) in which the handler function is executed.\nIf omitted, defaults to the object which fired the event.
An object containing handler configuration.
\nMethod to manage awareness of when components are added to their\nrespective Container, firing an added event.\nReferences are established at add time rather than at render time.
\nContainer which holds the component
\nPosition at which the component was added
\nMethod to manage awareness of when components are removed from their\nrespective Container, firing an removed event. References are properly\ncleaned up after removing a component from its owning container.
\nprivate
\nRelays selected events from the specified Observable as if the events were fired by this.
\nThe Observable whose events this object is to relay.
\nArray of event names to relay.
\nRemoves a CSS class from the component's underlying element.
\nThe CSS class name to remove
\nthis
\nRemoves an event handler.
\nThe type of event the handler was associated with.
\nThe handler to remove. This must be a reference to the function passed into the addListener call.
\nThe scope originally specified for the handler.
\nRender this Component into the passed HTML element.
\n\n\nIf you are using a Container object to house this Component, then\ndo not use the render method.
\n\n\nA Container's child Components are rendered by that Container's\nlayout manager when the Container is first rendered.
\n\n\nCertain layout managers allow dynamic addition of child components. Those that do\ninclude Ext.layout.CardLayout, Ext.layout.AnchorLayout,\nExt.layout.FormLayout, Ext.layout.TableLayout.
\n\n\nIf the Container is already rendered when a new child Component is added, you may need to call\nthe Container's doLayout to refresh the view which causes any\nunrendered child Components to be rendered. This is required so that you can add multiple\nchild components if needed while only refreshing the layout once.
\n\n\nWhen creating complex UIs, it is important to remember that sizing and positioning\nof child items is the responsibility of the Container's layout manager.\nIf you expect child items to be sized in response to user interactions, you must\nconfigure the Container with a layout manager which creates and manages the type of layout you\nhave in mind.
\n\n\nOmitting the Container's layout config means that a basic\nlayout manager is used which does nothing but render child components sequentially into the\nContainer. No sizing or positioning will be performed in this situation.
\n\nThe element this Component should be\nrendered into. If it is being created from existing markup, this should be omitted.
\nThe element ID or DOM node index within the container before\nwhich this component will be inserted (defaults to appending to the end of the container)
\nthis
\nResume firing events. (see suspendEvents)\nIf events were suspended using the queueSuspended parameter, then all\nevents fired during event suspension will be sent to any listeners now.
\nConvenience function for setting disabled/enabled by boolean.
\nthis
\nReplaces any existing disabled dates with new values and refreshes the DatePicker.
\nAn array of date strings (see the disabledDates config\nfor details on supported values), or a JavaScript regular expression used to disable a pattern of dates.
\nReplaces any existing disabled days (by index, 0-6) with new values and refreshes the DatePicker.
\nAn array of disabled day indexes. See the disabledDays config\nfor details on supported values.
\nConvenience function to hide or show this component by boolean.
\nTrue to show, false to hide
\nthis
\nShow this component. Listen to the 'beforeshow' event and return\nfalse to cancel showing the component. Fires the 'show'\nevent after showing the component.
\nthis
\nSuspend the firing of all events. (see resumeEvents)
\nPass as true to queue up suspended events to be fired\nafter the resumeEvents call instead of discarding all suspended events;
\nRemoves an event handler (shorthand for removeListener.)
\nThe type of event the handler was associated with.
\nThe handler to remove. This must be a reference to the function passed into the addListener call.
\nThe scope originally specified for the handler.
\nprivate
\n\nUpdate the content area of a component.
\nIf this component has been configured with a template via the tpl config\nthen it will use this argument as data to populate the template.\nIf this component was not configured with a template, the components\ncontent area will be updated via Ext.Element update
\n(optional) Only legitimate when using the html configuration. Defaults to false
\n(optional) Only legitimate when using the html configuration. Callback to execute when scripts have finished loading
\nOverrides: Ext.Component.update
Fires when a component is added to an Ext.Container
\nContainer which holds the component
\nPosition at which the component was added
\nFires after the component rendering is finished.
\n\n\nThe afterrender event is fired after this Component has been rendered, been postprocesed\nby any afterRender method defined for the Component, and, if stateful, after state\nhas been restored.
\n\nFires before the component is destroyed. Return false from an event handler to stop the destroy.
\nFires before the component is hidden by calling the hide method.\nReturn false from an event handler to stop the hide.
\nFires before the component is rendered. Return false from an\nevent handler to stop the render.
\nFires before the component is shown by calling the show method.\nReturn false from an event handler to stop the show.
\nFires before the state of the component is restored. Return false from an event handler to stop the restore.
\nThe hash of state values returned from the StateProvider. If this\nevent is not vetoed, then the state object is passed to applyState. By default,\nthat simply copies property values into this Component. The method maybe overriden to\nprovide custom state restoration.
\nFires before the state of the component is saved to the configured state provider. Return false to stop the save.
\nThe hash of state values. This is determined by calling\ngetState() on the Component. This method must be provided by the\ndeveloper to return whetever representation of state is required, by default, Ext.Component\nhas a null implementation.
\nFires after the component is hidden.\nFires after the component is hidden when calling the hide method.
\nFires when a component is removed from an Ext.Container
\nContainer which holds the component
\nFires when a date is selected
\nDatePicker
\nThe selected date
\nFires after the state of the component is restored.
\nThe hash of state values returned from the StateProvider. This is passed\nto applyState. By default, that simply copies property values into this\nComponent. The method maybe overriden to provide custom state restoration.
\nFires after the state of the component is saved to the configured state provider.
\nThe hash of state values. This is determined by calling\ngetState() on the Component. This method must be provided by the\ndeveloper to return whetever representation of state is required, by default, Ext.Component\nhas a null implementation.
\n