X-Git-Url: http://git.ithinksw.org/extjs.git/blobdiff_plain/7a654f8d43fdb43d78b63d90528bed6e86b608cc..3789b528d8dd8aad4558e38e22d775bcab1cbd36:/docs/api/Ext.state.Stateful.html?ds=sidebyside diff --git a/docs/api/Ext.state.Stateful.html b/docs/api/Ext.state.Stateful.html deleted file mode 100644 index da9b290b..00000000 --- a/docs/api/Ext.state.Stateful.html +++ /dev/null @@ -1,450 +0,0 @@ -
Mixins
A mixin for being able to save the state of an object to an underlying -Ext.state.Provider.
-(optional)
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 child element of a Component, we need to specify the element
option to
-identify the Component property to add a DOM listener to:
new Ext.panel.Panel({
- width: 400,
- height: 200,
- dockedItems: [{
- xtype: 'toolbar'
- }],
- listeners: {
- click: {
- element: 'el', //bind to the underlying el property on the panel
- fn: function(){ console.log('click el'); }
- },
- dblclick: {
- element: 'body', //bind to the underlying body property on the panel
- fn: function(){ console.log('dblclick body'); }
- }
- }
-});
-
-
-
-
-A buffer to be applied if many state events are fired within -a short period. Defaults to 100.
-A buffer to be applied if many state events are fired within -a short period. Defaults to 100.
-An array of events that, when fired, should trigger this object to
-save its state (defaults to none). stateEvents
may be any type
-of event supported by this object, including browser or custom events
-(e.g., ['click', 'customerchange']).
See stateful
for an explanation of saving and
-restoring object state.
The unique id for this object to use for state management purposes.
- -See stateful for an explanation of saving and restoring state.
- -A flag which causes the object to attempt to restore the state of
-internal properties from a saved state on startup. The object must have
-a stateId
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 object.
-
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 object attempts to save state when one of the events
-listed in the stateEvents
configuration fires.
To save state, a stateful object 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 restorable state of the object.
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 stateId
During construction, a stateful object attempts to restore
-its state by calling Ext.state.Manager.get passing the
-stateId
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.
- -Adds the specified events to the list of events which this Observable may fire.
-Adds the specified events to the list of events which this Observable may fire.
-Either an object with event names as properties with a value of true
-or the first event name string if multiple event names are being passed as separate parameters.
[additional] Optional additional event names if multiple event names are being passed as separate parameters. -Usage:
- -this.addEvents('storeloaded', 'storecleared');
-
-
-Appends an event handler to this object.
-Appends an event handler to this object.
-The name of the event to listen for. May also be an object who's property names are event names. See
-The method the event invokes.
-(optional) The scope (this
reference) in which the handler function is executed.
-If omitted, defaults to the object which fired the event.
(optional) An object containing handler configuration. -properties. This may contain any of the following properties:
this
reference) in which the handler function is executed.
-If omitted, defaults to the object which fired the event.This option is useful during Component construction to add DOM event listeners to elements of Components which -will exist only after the Component is rendered. For example, to add a click listener to a Panel's body: -
new Ext.panel.Panel({
- title: 'The title',
- listeners: {
- click: this.handlePanelClick,
- element: 'body'
- }
-});
-
-
-
-When added in this way, the options available are the options applicable to Ext.core.Element.addListener
- - -
-Combining Options
-Using the options argument, it is possible to combine different types of listeners:
-
-A delayed, one-time listener.
-
myPanel.on('hide', this.handleClick, this, {
-single: true,
-delay: 100
-});
-
-Attaching multiple handlers in 1 call
-The method also allows for a single argument to be passed which is a config object containing properties
-which specify multiple events. For example:
-
myGridPanel.on({
- cellClick: this.onCellClick,
- mouseover: this.onMouseOver,
- mouseout: this.onMouseOut,
- scope: this // Important. Ensure "this" is correct during handler execution
-});
-
.
-- -
Adds listeners to any Observable object (or Element) which are automatically removed when this Component -is destroyed. - -
Adds listeners to any Observable object (or Element) which are automatically removed when this Component -is destroyed. - -
The item to which to add a listener/listeners.
-The event name, or an object containing event name properties.
-Optional. If the ename
parameter was an event name, this
-is the handler function.
Optional. If the ename
parameter was an event name, this
-is the scope (this
reference) in which the handler function is executed.
Optional. If the ename
parameter was an event name, this
-is the addListener options.
Add events that will trigger the state to be saved.
-Add events that will trigger the state to be saved.
-The event name or an array of event names.
-Applies the state to the object. This should be overridden in subclasses to do -more complex state operations. By default it applies the state properties onto -the current object.
-The state
-Starts capture on the specified Observable. All events will be passed -to the supplied function with the event name + standard signature of the event -before the event is fired. If the supplied function returns false, -the event will not fire.
-The Observable to capture events from.
-The function to call when an event is fired.
-(optional) The scope (this
reference) in which the function is executed. Defaults to the Observable firing the event.
Removes all listeners for this object including the managed listeners
-Removes all listeners for this object including the managed listeners
-Removes all managed listeners for this object.
-Removes all managed listeners for this object.
-Enables events fired by this Observable to bubble up an owner hierarchy by calling
-this.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 -implementation in Ext.Component returns the Component's immediate owner. But if a known target is required, this can be overridden to -access the required target more quickly.
- - -Example:
- - -Ext.override(Ext.form.field.Base, {
-// Add functionality to Field's initComponent to enable the change event to bubble
-initComponent : Ext.Function.createSequence(Ext.form.field.Base.prototype.initComponent, function() {
- this.enableBubble('change');
-}),
-
-// We know that we want Field's events to bubble directly to the FormPanel.
-getBubbleTarget : function() {
- if (!this.formPanel) {
- this.formPanel = this.findParentByType('form');
- }
- return this.formPanel;
-}
-});
-
-var myForm = new Ext.formPanel({
-title: 'User Details',
-items: [{
- ...
-}],
-listeners: {
- change: function() {
- // Title goes red if form has been modified.
- myForm.header.setStyle('color', 'red');
- }
-}
-});
-
-
-The event name to bubble, or an Array of event names.
-Fires the specified event with the passed parameters (minus the event name).
- - -An event may be set to bubble up an Observable parent hierarchy (See Ext.Component.getBubbleTarget) -by calling enableBubble.
- -The name of the event to fire.
-Variable number of parameters are passed to handlers.
-returns false if any of the handlers return false otherwise it returns true.
-Gets the current state of the object. By default this function returns null, -it should be overridden in subclasses to implement methods for getting the state.
-The current state
-Gets the state id for this object.
-Gets the state id for this object.
-The state id, null if not found.
-Checks to see if this object has any listeners for a specified event
-Checks to see if this object has any listeners for a specified event
-The name of the event to check for
-True if the event is being listened for, else false
-Sets observability on the passed class constructor.
- -This makes any event fired on any instance of the passed class also fire a single event through -the class allowing for central handling of events on many instances at once.
- -Usage:
- -Ext.util.Observable.observe(Ext.data.Connection);
-Ext.data.Connection.on('beforerequest', function(con, options) {
- console.log('Ajax request made to ' + options.url);
-});
-
-The class constructor to make observable.
-An object containing a series of listeners to add. See addListener.
-Appends an event handler to this object (shorthand for addListener.)
-Appends an event handler to this object (shorthand for addListener.)
-The type of event to listen for
-The method the event invokes
-(optional) The scope (this
reference) in which the handler function is executed.
-If omitted, defaults to the object which fired the event.
(optional) An object containing handler configuration.
-Relays selected events from the specified Observable as if the events were fired by this
.
Relays selected events from the specified Observable as if the events were fired by this
.
The Observable whose events this object is to relay.
-Array of event names to relay.
-Removes all added captures from the Observable.
-Removes all added captures from the Observable.
-The Observable to release
-Removes an event handler.
-Removes an event handler.
-The type of event the handler was associated with.
-The handler to remove. This must be a reference to the function passed into the addListener call.
-(optional) The scope originally specified for the handler.
-Removes listeners that were added by the mon method.
-Removes listeners that were added by the mon method.
-The item from which to remove a listener/listeners.
-The event name, or an object containing event name properties.
-Optional. If the ename
parameter was an event name, this
-is the handler function.
Optional. If the ename
parameter was an event name, this
-is the scope (this
reference) in which the handler function is executed.
Resume firing events. (see suspendEvents)
-If events were suspended using the queueSuspended
parameter, then all
-events fired during event suspension will be sent to any listeners now.
Suspend the firing of all events. (see resumeEvents)
-Suspend the firing of all events. (see resumeEvents)
-Pass as true to queue up suspended events to be fired -after the resumeEvents call instead of discarding all suspended events;
-Removes an event handler (shorthand for removeListener.)
-Removes an event handler (shorthand for removeListener.)
-The type of event the handler was associated with.
-The handler to remove. This must be a reference to the function passed into the addListener call.
-(optional) The scope originally specified for the handler.
-Fires before the state of the object is restored. Return false from an event handler to stop the restore.
-Fires before the state of the object is restored. Return false from an event handler to stop the restore.
-The hash of state values returned from the StateProvider. If this -event is not vetoed, then the state object is passed to applyState. By default, -that simply copies property values into this object. The method maybe overriden to -provide custom state restoration.
-Fires before the state of the object is saved to the configured state provider. Return false to stop the save.
-Fires before the state of the object is saved to the configured state provider. Return false to stop the save.
-The hash of state values. This is determined by calling -getState() on the object. This method must be provided by the -developer to return whetever representation of state is required, by default, Ext.state.Stateful -has a null implementation.
-Fires after the state of the object is restored.
-Fires after the state of the object is restored.
-The hash of state values returned from the StateProvider. This is passed -to applyState. By default, that simply copies property values into this -object. The method maybe overriden to provide custom state restoration.
-Fires after the state of the object is saved to the configured state provider.
-Fires after the state of the object is saved to the configured state provider.
-The hash of state values. This is determined by calling -getState() on the object. This method must be provided by the -developer to return whetever representation of state is required, by default, Ext.state.Stateful -has a null implementation.
-