MODULES Uize.Util.PropertyAdapter
- Contents
-
1. Introduction
-
1.1. In a Nutshell
- 1.1.1. A Basic Example
-
1.1.2. Features
- 1.1.2.1. Two State Properties
- 1.1.2.2. Value Adapter
- 1.1.2.3. Connection and Disconnection
- 1.1.2.4. Synchronization
- 1.1.2.5. Dynamically Updatable
- 1.1.2.6. Infinite Loop Protection
- 1.1.2.7. Uize.Util.PropertyAdapter vs Uize.Util.Coupler
- 1.2. Examples
- 1.3. Implementation Info
-
1.1. In a Nutshell
- 2. State Properties
- 3. Instance Methods
-
4. Static Methods
- 4.1. Uize.Util.PropertyAdapter.alphastructor
- 4.2. Uize.Util.PropertyAdapter.declare
- 4.3. Uize.Util.PropertyAdapter.doMy
- 4.4. Uize.Util.PropertyAdapter.dualContextMethods
- 4.5. Uize.Util.PropertyAdapter.dualContextProperties
- 4.6. Uize.Util.PropertyAdapter.fire
- 4.7. Uize.Util.PropertyAdapter.get
- 4.8. Uize.Util.PropertyAdapter.instanceMethods
- 4.9. Uize.Util.PropertyAdapter.instanceProperties
- 4.10. Uize.Util.PropertyAdapter.mixins
- 4.11. Uize.Util.PropertyAdapter.omegastructor
- 4.12. Uize.Util.PropertyAdapter.set
- 4.13. Uize.Util.PropertyAdapter.singleton
- 4.14. Uize.Util.PropertyAdapter.stateProperties
- 4.15. Uize.Util.PropertyAdapter.staticMethods
- 4.16. Uize.Util.PropertyAdapter.staticProperties
- 4.17. Uize.Util.PropertyAdapter.subclass
- 4.18. Uize.Util.PropertyAdapter.toggle
- 4.19. Uize.Util.PropertyAdapter.unwire
- 4.20. Uize.Util.PropertyAdapter.wire
- 5. Static Properties
-
1. Introduction
1. Introduction
The Uize.Util.PropertyAdapter
class implements a mechanism for connecting two state properties together, with optional bi-directional value adapter code.
DEVELOPERS: Chris van Rensburg
1.1. In a Nutshell
The Uize.Util.PropertyAdapter
class makes it easy to connect two state properties in a synchronization relationship, where a change in the value of one of the properties results in the value of the other property being synchronized to the new value of the property that changed.
Any two state properties can be connected to each other using a property adapter instance. It can be two properties of the same instance, or it can be properties of two different instances. The properties being connected can belong to widget instances (i.e. instances of Uize.Widget
subclasses), but the instances owning the properties do not have to be widgets. The instances owning the two properties being connected do not even have to be of the same class. And the two properties do not even have to be of the same type or have the same value range - the Uize.Util.PropertyAdapter
class provides a way to specify a value adapter that should be used to adapt the value in either direction.
1.1.1. A Basic Example
To connect two properties of any two instances together through a property adapter is as easy as creating an instance of the Uize.Util.PropertyAdapter
class.
EXAMPLE
Uize.Util.PropertyAdapter ({ propertyA:{ instance:sliderA, property:'minValue' }, propertyB:{ instance:sliderB, property:'minValue' } });
In the above example, the minValue
state properties of two sliders (instances of the Uize.Widget.Bar.Slider
class) are being connected through a property adapter, so that if the value of the minValue
property is modified in sliderA
, the value of the minValue
property of sliderB
is automatically synchronized to that new value, and vice versa.
1.1.2. Features
While elegant in its simplicity (and not involving all that much code), the Uize.Util.PropertyAdapter
class is quite powerful and versatile with the small set of features it has.
1.1.2.1. Two State Properties
Each instance of the Uize.Util.PropertyAdapter
class can connect two state properties together: property A and property B.
1.1.2.1.1. Property A
Property A is one of the two state properties that can be connected together via an instance of the Uize.Util.PropertyAdapter
class.
To set the instance and property for property A, set the value of the propertyA
state property of the Uize.Util.PropertyAdapter
instance to a valid property specifier (see A Basic Example).
1.1.2.1.1.1. Property A Is Primary
While both property A and property B are kept synchronized by a property adapter, and affecting any one will affect the other, property A is given special treatment and is regarded as the primary property of the pair.
In practical terms, what this means is that whenever initial connection is established between two properties, the value of property B is initially synchronized to the value of property A. If the values of the two properties were already in agreement (taking into account also the optional value adapter), then there will be no change in the value of property B. If they are not in agreement at the time of initial connection, then the value of property B will change - the value of property A will never change upon connecting the two properties.
1.1.2.1.2. Property B
Property B is one of the two state properties that can be connected together via an instance of the Uize.Util.PropertyAdapter
class.
To set the instance and property for property B, set the value of the propertyB
state property of the Uize.Util.PropertyAdapter
instance to a valid property specifier (see A Basic Example).
1.1.2.1.2.1. Property B Is Secondary
While property A is primary, property B is secondary in the connection of two properties (for an explanation of what this means in practical terms, refer to the section Property A is Primary).
1.1.2.1.3. Property Specifier
Specifying the instance and property for either property A or property B is done using a property specifier.
A property specifier can take one of several forms, as outlined below...
1.1.2.1.3.1. Property Specifier Object Form
The canonical form of a property specifier is an object, containing the properties instance
and property
.
SYNTAX
{ instance : instanceOBJ, // reference to an instance of a Uize subclass property : propertyNameSTR // name of a state property on the specified instance }
The value of the instance
property should be a reference to an instance of a Uize.Class
subclass, and the value of the property
property should be a string specifying the name of a state property on the instance specified by the instance
property. If the value of the property
property is null
or undefined
, then the property name will be defaulted to 'value'
.
Because the property specifier object form is the canonical form for a property specifier, when a property is specified using either the property specifier array form or the property specifier instance form, the property specifier is resolved to the object form.
1.1.2.1.3.2. Property Specifier Array Form
As a convenience, a property can be specified using the concise array form, in which a property is specified as a two element array.
SYNTAX
[ instanceOBJ, // reference to an instance of a Uize subclass propertyNameSTR // name of a state property on the specified instance ]
The value of the first element of the array should be a reference to an instance of a Uize.Class
subclass, and the value of the second element of the array should be a string specifying the name of a state property on the instance specified by the instance
property. If the value of the second element is null
or undefined
, then the property name will be defaulted to 'value'
.
1.1.2.1.3.3. Property Specifier Instance Form
In the special case where one wishes to specify the value
property of an instance of a Uize.Class
subclass, the property can be specified simply by specifying a reference to the instance.
SYNTAX
instanceOBJ // reference to an instance of a Uize subclass
It is a fairly common use case to connect the value
property of two instances to one another using a property adapter. For such cases, specifying just the instances for each of the properties is a convenient shorthand.
1.1.2.1.3.4. Versatile Conformer
When using a property specifier to specify a value for either of the propertyA
or propertyB
state properties, the property specifier is resolved to the canonical property specifier object form using a versatile conformer.
Because the values of the propertyA
or propertyB
state properties are conformed, a property specifier expressed in either the property specifier array form or the property specifier instance form will not be stored internally in those alternate forms, but will instead be conformed to the canonical property specifier object form.
1.1.2.2. Value Adapter
A powerful feature of the Uize.Util.PropertyAdapter
class is its support for a value adapter, which allows transformation of the values of property A and property B in both directions.
A value adapter is an object of the following form...
STRUCTURE
{ aToB : aToBValueTransformerFUNC, // transforms property A value into property B value bToA : bToAValueTransformerFUNC // transforms property B value into property A value }
1.1.2.2.1. aToB
The aToB
property of a value adapter object specifies a value transformer function that should be used to transform a value for property A to produce a value for property B.
1.1.2.2.2. bToA
The bToA
property specifies a value transformer function that should be used to transform a value for property B to produce a value for property A.
1.1.2.2.3. Value Transformer
A value transformer specified for either of the properties aToB
or bToA
should be a function that expects to receive a single parameter representing the value to be transformed, and that should return the transformed value.
EXAMPLE
{ aToB:function (value) {return value * value}, bToA:function (value) {return Math.sqrt (value)} }
In the above example, a value adapter is defining a mathematical relationship between a value A and a value B, where value B is the square of value A and, conversely, where value A is the square root of value B. The aToB
property specifies the function that is use to convert value A to value B, which takes a value parameter and returns its square. The bToA
property specifies the function that is use to convert value B to value A, which takes a value parameter and returns its square root.
1.1.2.2.4. Use Cases for a Value Adapter
A value adapter allows the values of the two state properties that are connected through a property adapter to be encoded or serialized differently, or to have some other form of relationship to one another (such as a mathematical relationship, for example).
1.1.2.2.4.1. Value Adapter for Mathematical Relationships
A value adapter can be used in the context of a property adapter to maintain a mathematical relationship between two state properties.
EXAMPLE
Uize.Util.PropertyAdapter ({ propertyA:numberTextInput, // instance of Uize.Widget.TextInput propertyB:numberSquaredTextInput, // instance of Uize.Widget.TextInput valueAdapter:{ aToB:function (value) {return value * value}, bToA:function (value) {return Math.sqrt (value)} } });
In the above example, a property adapter is being used to connect the value
state properties of two text input widgets (instances of the Uize.Widget.TextInput
class): numberTextInput
and numberSquaredTextInput
. A value adapter is specified to maintain a relationship where the value of the numberSquaredTextInput
instance is the square of the value of the numberTextInput
instance and, conversely, where the value of the numberTextInput
instance is the square root of the numberSquaredTextInput
instance.
1.1.2.2.4.2. Value Adapter for Different Encodings
A value adapter can be used in the context of a property adapter to maintain an encoding relationship between two state properties.
EXAMPLE
Uize.Util.PropertyAdapter ({ propertyA:colorAsHexTextInput, propertyB:colorAsRgbTextInput, valueAdapter:Uize.Color.adapter ('#hex','RGB string') });
In the above example, a property adapter is being used to connect the value
state properties of two text input widgets (instances of the Uize.Widget.TextInput
class): colorAsHexTextInput
and colorAsRgbTextInput
. A value adapter is specified to maintain a relationship where the values of the colorAsHexTextInput
and colorAsRgbTextInput
instances represent the same color, but where the value of the colorAsHexTextInput
instance is the color encoded in hex format (e.g. #ffa500
for orange), and the value of the colorAsRgbTextInput
instance is the color encoded in RGB tuple format (e.g. rgb(255,165,0)
for orange). In this example, we're fortunate enough to be able to use the Uize.Color.adapter
static method of the Uize.Color
object to generate a value adapter that will adapt a color value between the two encodings '#hex'
and 'RGB string'
.
1.1.2.2.5. How a Value Adapter is Used
If a value adapter is specified for a property adapter instance, it is used whenever synchronization needs to be performed between the state properties that are connected through the property adapter.
When property A to property B synchronization is performed, the value transformer function specified by the aToB
property of the value adapter object is applied to the value of property A to produce a new value for property B. Conversely, when property B to property A synchronization is performed, the value transformer function specified by the bToA
property of the value adapter object is applied to the value of property B to produce a new value for property A.
1.1.2.3. Connection and Disconnection
The two state properties specified for an instance of the Uize.Util.PropertyAdapter
class are connected and disconnected under different conditions.
1.1.2.3.1. Initial Connection
Initial connection is when the two state properties are either connected for the very first time, or are reconnected after having been disconnected.
Specifically, initial connection occurs when...
the value of the connected state property becomes true , and the value of neither the propertyA nor propertyB state property is null or undefined |
|
immediately after either of property A or property B are changed or the value adapter is changed, and the value of neither the propertyA nor propertyB state property is null or undefined |
Whenever initial connection occurs, the propery adapter instance performs property A to property B synchronization, and value change event handlers are wired on the instances that own the two state properties in order to ensure that the appropriate synchronization is performed when the value of either property A or property B is modified.
1.1.2.3.2. Disconnection
Disconnection is when two state properties that were previously connected through a property adapter instance become disconnected so that their values are no longer kept synchronized.
Specifically, disconnection occurs when two state properties were previously connected and then ...
the value of the connected state property becomes false |
|
the value of any of the propertyA , propertyB , or valueAdapter state properties is changed (if the value of neither the propertyA nor propertyB state property is null or undefined after the change, then disconnection will occur right before the initial connection that occurs for the new configuration of connected properties and/or value adapter) |
1.1.2.4. Synchronization
Synchronization is when the value of one of the two state properties that are connected through a property adapter instance changes, and the value of the other property in the pair is updated in order to keep it synchronized with the one that changed.
When two state properties are specified for a property adapter instance, but that instance's connected
state property is set to false
, then synchronization will not be performed if the value of either of the two state properties is modified. Whenever synchronization is performed, the value of the valueAdapter
state property is taken into consideration (see How a Value Adapter is Used).
1.1.2.4.1. Property A to Property B Synchronization
Once initial connection has occured between two state properties specified for a property adapter instance, a change in the value of property A will result in the value of property B being synchronized to the new value of property A.
When the value of property B is synchronized to the value of property A, any value adapter specified for the property adapter instance is taken into account (see How a Value Adapter is Used).
1.1.2.4.1.1. Property A to Property B Synchronization on Initial Connection
Unlike property B to property A synchronization, synchronization from property A to property B is also performed upon initial connection of the two state properties.
This ensures that the values of property A and property B are in agreement immediately upon connecting the two properties through the property adapter.
1.1.2.4.2. Property B to Property A Synchronization
Once initial connection has occured between two state properties specified for a property adapter instance, a change in the value of property B will result in the value of property A being synchronized to the new value of property B.
When the value of property A is synchronized to the value of property B, any value adapter specified for the property adapter instance is taken into account (see How a Value Adapter is Used).
1.1.2.5. Dynamically Updatable
The Uize.Util.PropertyAdapter
class supports dynamic updating of all of its state properties.
This means that one can dynamically connect and disconnect the properties connected through an instance, one can dynamically change the properties connected through an instance, and one can dynamically change the value adapter being used by an instance.
1.1.2.5.1. Dynamically Connect and Disconnect
The Uize.Util.PropertyAdapter
class supports dynamically connecting and disconnecting the two state properties that are connected through a property adapter instance.
The properties can be connected or disconneced at any time, simply by setting the value of the property adapter instance's connected
state property.
1.1.2.5.2. Dynamically Change the Properties
Any or both of the two state properties that are connected through a property adapter instance can be changed midstream, simply by setting the value of either or both of the property adapter instance's propertyA
and propertyB
state properties.
When dynamically changing the properties that are connected through a property adapter, disconnection will occur for any previously connected properties, after which initial connection will occur for the new configuration of properties.
1.1.2.5.3. Dynamically Change the Value Adapter
The Uize.Util.PropertyAdapter
class supports dynamically changing the value adapter that is used to transform values when performing synchronization from property A to property B, and vice versa.
Changing the value adapter that is used by a property adapter instance is as simple as setting the value of the instance's valueAdapter
state property. When dynamically changing the value adapter, disconnection will occur for any previously connected properties, after which initial connection will occur for the new configuration of properties and value adapter.
1.1.2.6. Infinite Loop Protection
The Uize.Util.PropertyAdapter
class implements infinite loop protection, to prevent runaway looping that may otherwise occur as a result of non-settling property values or a divergent value adapter.
1.1.2.6.1. Non-settling Property Values
Non-settling property values is a problem that could occur if a value adapter is specified where a value for property B that is generated from property A using the aToB
transformer function cannot be converted back to the exact original value for property A using the bToA
tranformer function, and the same is also true for transforming with property B as the original value.
The actual cause of non-settling property values could be a value adapter whose transformer functions involve mathematical calculations that suffer from insufficient precision.
1.1.2.6.1.1. Divergent Value Adapter
A specific type of issue of non-settling property values occurs when the two transformer functions of a value adapter produce infinitely diverging values for property A and property B.
EXAMPLE
Uize.Util.PropertyAdapter ({ propertyA:sliderA, propertyB:sliderB, valueAdapter:{ aToB:function (value) {return value + 1}, bToA:function (value) {return value + 1} } });
In the above example, both the aToB
and bToA
transformer functions of the value adapter increment the value they're given. If synchronization was allowed to be a runaway process, both the value for property A and property B would continue incrementing ad infinitum.
1.1.2.6.2. How Looping is Prevented
Fortunately, the Uize.Util.PropertyAdapter
class implements a simple mechanism to prevent infinite loops that could otherwise occur with non-settling property values.
In simple terms, while value change event handlers are wired for both property A and property B in order to support synchronization in both directions, a change in the value of one of the properties that is synchronized to the other property blocks the change in the value of the other property from causing synchronization back to the property that originally changed and initiated the synchronization in the first place. Simple. Nipped in the bud.
1.1.2.7. Uize.Util.PropertyAdapter vs Uize.Util.Coupler
While the Uize.Util.PropertyAdapter
and Uize.Util.Coupler
classes are similar in spirit, there are some key differences to note.
the Uize.Util.PropertyAdapter class supports connecting any two state properties of any two instances (e.g. the textColor property of some instance with the bgColor property of some other instance), while the Uize.Util.Coupler class supports connecting the same set of any number of state properties across two or more instances (e.g. the minValue and maxValue properties of three different slider widget instances) |
|
the Uize.Util.Coupler class supports only exact synchronization of the values of the various connected properties, while the Uize.Util.PropertyAdapter class supports an optional value adapter object that allows for the connected properties to have different value ranges or encodings |
1.1.2.7.1. For Simple Cases, They're Equivalent
In the most simple case of connecting the same named property of two instances, without any value adapting between the properties, either of the Uize.Util.PropertyAdapter
and Uize.Util.Coupler
classes could be used to the same effect.
USING A COUPLER...
Uize.Util.Coupler ({ instances:[instanceA,instanceB], properties:['someProperty'] });
USING A PROPERTY ADAPTER...
Uize.Util.PropertyAdapter ({ propertyA:[instanceA,'someProperty'], propertyA:[instanceB,'someProperty'] });
1.2. Examples
The following example pages are good showcases for the Uize.Util.PropertyAdapter
module...
Basic Color Grid - See an example of a color grid, where the color swatches in the grid are interpolated from RGB corner colors that can be dynamically set by the user. | |
Color Format Converter - Easily convert color values from one format to another. Convert between RGB hex, RGB tuple string, HSL, HSV, CMYK, and SVG color names. |
SEARCH FOR EXAMPLES
Use the link below to search for example pages on the UIZE Web site that reference the Uize.Util.PropertyAdapter
module...
SEARCH
1.3. Implementation Info
The Uize.Util.PropertyAdapter
module defines the Uize.Util.PropertyAdapter
class, which is a subclass of Uize.Class
.
INHERITANCE CHAIN
Uize.Class
−> Uize.Util.PropertyAdapter
1.3.1. Features Introduced in This Module
The features listed in this section have been introduced in this module.
STATE PROPERTIES
1.3.2. Features Overridden in This Module
The features listed in this section have been overridden in this module.
The module that an overridden feature was initially introduced in will be noted in the IMPLEMENTATION INFO notes for the feature.
INSTANCE METHODS
STATIC PROPERTIES
Uize.Util.PropertyAdapter.moduleName
| Uize.Util.PropertyAdapter.nonInheritableStatics
1.3.3. Features Inherited From Other Modules
The features listed in this section have been inherited from other modules.
The module that an inherited feature was initially introduced in will be noted in the IMPLEMENTATION INFO notes for the feature.
INSTANCE METHODS
fire
| get
| is
| isMet
| kill
| met
| onChange
| once
| set
| toggle
| unmet
| unwire
| whenever
| wire
STATIC METHODS
Uize.Util.PropertyAdapter.alphastructor
| Uize.Util.PropertyAdapter.declare
| Uize.Util.PropertyAdapter.doMy
| Uize.Util.PropertyAdapter.dualContextMethods
| Uize.Util.PropertyAdapter.dualContextProperties
| Uize.Util.PropertyAdapter.fire
| Uize.Util.PropertyAdapter.get
| Uize.Util.PropertyAdapter.instanceMethods
| Uize.Util.PropertyAdapter.instanceProperties
| Uize.Util.PropertyAdapter.mixins
| Uize.Util.PropertyAdapter.omegastructor
| Uize.Util.PropertyAdapter.set
| Uize.Util.PropertyAdapter.singleton
| Uize.Util.PropertyAdapter.stateProperties
| Uize.Util.PropertyAdapter.staticMethods
| Uize.Util.PropertyAdapter.staticProperties
| Uize.Util.PropertyAdapter.subclass
| Uize.Util.PropertyAdapter.toggle
| Uize.Util.PropertyAdapter.unwire
| Uize.Util.PropertyAdapter.wire
STATIC PROPERTIES
1.3.4. Modules Directly Under This Namespace
There are no modules directly under this namespace.
1.3.5. Unit Tests
The Uize.Util.PropertyAdapter
module is unit tested by the Uize.Test.Uize.Util.PropertyAdapter
test module.
2. State Properties
2.1. connected
A boolean, indicating whether or not the connection is active and the properties specified by the propertyA
and propertyB
state properties are connected together.
If this property is set to false
after properties have already been connected, then they will be disconnected. They can be reconnected again later by setting the value of this property back to true
. Whenever the value of this property changes from false
to true
and properties are specified for both property A and property B, then initial connection will be established.
NOTES
the initial value is true |
IMPLEMENTATION INFO
this feature was introduced in this module |
2.2. propertyA
A property specifier, specifying the instance and the property for property A.
If the value of this property is changed after properties have already been connected, then the previously connected properties will be disconnected and initial connection will be established for the new pair of properties.
NOTES
see the companion propertyB state property |
|
the initial value is undefined |
IMPLEMENTATION INFO
this feature was introduced in this module |
2.3. propertyB
A property specifier, specifying the instance and the property for property B.
If the value of this property is changed after properties have already been connected, then the previously connected properties will be disconnected and initial connection will be established for the new pair of properties.
NOTES
see the companion propertyA state property |
|
the initial value is undefined |
IMPLEMENTATION INFO
this feature was introduced in this module |
2.4. valueAdapter
An object, specifying a value adapter that should be used to translate the value of property A to a value for property B, or vice versa.
If the value of this property is changed after properties have already been connected, then initial connection will be re-established for the previously connected properties, using the newly specified value adapter to synchronize property B to property A.
NOTES
see the related propertyA and propertyB state properties |
|
the initial value is undefined |
IMPLEMENTATION INFO
this feature was introduced in this module |
3. Instance Methods
3.1. fire
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
3.2. get
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
3.3. is
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
3.4. isMet
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
3.5. kill
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
3.6. met
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
3.7. onChange
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
3.8. once
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
3.9. set
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
3.10. toggle
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
3.11. unmet
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
3.12. unwire
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
3.13. valueOf
this is an override of an inherited feature (implementation is in this module, first introduced in Uize.Class ) |
IMPLEMENTATION INFO
3.14. whenever
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
3.15. wire
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
4. Static Methods
4.1. Uize.Util.PropertyAdapter.alphastructor
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
|
this static feature is inherited by subclasses |
4.2. Uize.Util.PropertyAdapter.declare
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
|
this static feature is inherited by subclasses |
4.3. Uize.Util.PropertyAdapter.doMy
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
|
this static feature is inherited by subclasses |
4.4. Uize.Util.PropertyAdapter.dualContextMethods
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
|
this static feature is inherited by subclasses |
4.5. Uize.Util.PropertyAdapter.dualContextProperties
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
|
this static feature is inherited by subclasses |
4.6. Uize.Util.PropertyAdapter.fire
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
|
this static feature is inherited by subclasses |
4.7. Uize.Util.PropertyAdapter.get
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
|
this static feature is inherited by subclasses |
4.8. Uize.Util.PropertyAdapter.instanceMethods
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
|
this static feature is inherited by subclasses |
4.9. Uize.Util.PropertyAdapter.instanceProperties
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
|
this static feature is inherited by subclasses |
4.10. Uize.Util.PropertyAdapter.mixins
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
|
this static feature is inherited by subclasses |
4.11. Uize.Util.PropertyAdapter.omegastructor
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
|
this static feature is inherited by subclasses |
4.12. Uize.Util.PropertyAdapter.set
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
|
this static feature is inherited by subclasses |
4.13. Uize.Util.PropertyAdapter.singleton
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
|
this static feature is inherited by subclasses |
4.14. Uize.Util.PropertyAdapter.stateProperties
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
|
this static feature is inherited by subclasses |
4.15. Uize.Util.PropertyAdapter.staticMethods
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
|
this static feature is inherited by subclasses |
4.16. Uize.Util.PropertyAdapter.staticProperties
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
|
this static feature is inherited by subclasses |
4.17. Uize.Util.PropertyAdapter.subclass
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
|
this static feature is inherited by subclasses |
4.18. Uize.Util.PropertyAdapter.toggle
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
|
this static feature is inherited by subclasses |
4.19. Uize.Util.PropertyAdapter.unwire
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
|
this static feature is inherited by subclasses |
4.20. Uize.Util.PropertyAdapter.wire
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
|
this static feature is inherited by subclasses |
5. Static Properties
5.1. Uize.Util.PropertyAdapter.moduleName
IMPLEMENTATION INFO
this is an override of an inherited feature (implementation is in this module, first introduced in Uize.Class ) |
|
this static feature is inherited by subclasses |
5.2. Uize.Util.PropertyAdapter.nonInheritableStatics
IMPLEMENTATION INFO
this is an override of an inherited feature (implementation is in this module, first introduced in Uize.Class ) |
|
this static feature is not inherited by subclasses |
5.3. Uize.Util.PropertyAdapter.pathToResources
Inherited from Uize.Class
.
IMPLEMENTATION INFO
this is an inherited feature (implementation is in Uize.Class , first introduced in Uize.Class ) |
|
this static feature is inherited by subclasses |