2012-07-19 00:11:26 +00:00
|
|
|
/**
|
|
|
|
* VisualEditor Factory class.
|
2012-07-19 21:25:16 +00:00
|
|
|
*
|
2012-07-19 00:11:26 +00:00
|
|
|
* @copyright 2011-2012 VisualEditor Team and others; see AUTHORS.txt
|
|
|
|
* @license The MIT License (MIT); see LICENSE.txt
|
|
|
|
*/
|
|
|
|
|
2012-04-20 21:44:41 +00:00
|
|
|
/**
|
2012-05-31 23:50:16 +00:00
|
|
|
* Generic object factory.
|
2012-05-14 22:05:09 +00:00
|
|
|
*
|
2012-04-20 21:44:41 +00:00
|
|
|
* @class
|
2012-05-31 23:50:16 +00:00
|
|
|
* @abstract
|
2012-04-20 21:44:41 +00:00
|
|
|
* @constructor
|
2012-11-07 20:09:18 +00:00
|
|
|
* @extends {ve.Registry}
|
2012-04-20 21:44:41 +00:00
|
|
|
*/
|
2012-09-06 23:15:55 +00:00
|
|
|
ve.Factory = function VeFactory() {
|
Object management: Object create/inherit/clone utilities
* For the most common case:
- replace ve.extendClass with ve.inheritClass (chose slightly
different names to detect usage of the old/new one, and I
like 'inherit' better).
- move it up to below the constructor, see doc block for why.
* Cases where more than 2 arguments were passed to
ve.extendClass are handled differently depending on the case.
In case of a longer inheritance tree, the other arguments
could be omitted (like in "ve.ce.FooBar, ve.FooBar,
ve.Bar". ve.ce.FooBar only needs to inherit from ve.FooBar,
because ve.ce.FooBar inherits from ve.Bar).
In the case of where it previously had two mixins with
ve.extendClass(), either one becomes inheritClass and one
a mixin, both to mixinClass().
No visible changes should come from this commit as the
instances still all have the same visible properties in the
end. No more or less than before.
* Misc.:
- Be consistent in calling parent constructors in the
same order as the inheritance.
- Add missing @extends and @param documentation.
- Replace invalid {Integer} type hint with {Number}.
- Consistent doc comments order:
@class, @abstract, @constructor, @extends, @params.
- Fix indentation errors
A fairly common mistake was a superfluous space before the
identifier on the assignment line directly below the
documentation comment.
$ ack "^ [^*]" --js modules/ve
- Typo "Inhertiance" -> "Inheritance".
- Replacing the other confusing comment "Inheritance" (inside
the constructor) with "Parent constructor".
- Add missing @abstract for ve.ui.Tool.
- Corrected ve.FormatDropdownTool to ve.ui.FormatDropdownTool.js
- Add function names to all @constructor functions. Now that we
have inheritance it is important and useful to have these
functions not be anonymous.
Example of debug shot: http://cl.ly/image/1j3c160w3D45
Makes the difference between
< documentNode;
> ve_dm_DocumentNode
...
: ve_dm_BranchNode
...
: ve_dm_Node
...
: ve_dm_Node
...
: Object
...
without names (current situation):
< documentNode;
> Object
...
: Object
...
: Object
...
: Object
...
: Object
...
though before this commit, it really looks like this
(flattened since ve.extendClass really did a mixin):
< documentNode;
> Object
...
...
...
Pattern in Sublime (case-sensitive) to find nameless
constructor functions:
"^ve\..*\.([A-Z])([^\.]+) = function \("
Change-Id: Iab763954fb8cf375900d7a9a92dec1c755d5407e
2012-09-05 06:07:47 +00:00
|
|
|
// Parent constructor
|
2012-11-07 20:09:18 +00:00
|
|
|
ve.Registry.call( this );
|
2012-05-31 23:50:16 +00:00
|
|
|
|
|
|
|
// Properties
|
2012-04-23 18:46:13 +00:00
|
|
|
this.registry = [];
|
2012-04-20 21:44:41 +00:00
|
|
|
};
|
|
|
|
|
Object management: Object create/inherit/clone utilities
* For the most common case:
- replace ve.extendClass with ve.inheritClass (chose slightly
different names to detect usage of the old/new one, and I
like 'inherit' better).
- move it up to below the constructor, see doc block for why.
* Cases where more than 2 arguments were passed to
ve.extendClass are handled differently depending on the case.
In case of a longer inheritance tree, the other arguments
could be omitted (like in "ve.ce.FooBar, ve.FooBar,
ve.Bar". ve.ce.FooBar only needs to inherit from ve.FooBar,
because ve.ce.FooBar inherits from ve.Bar).
In the case of where it previously had two mixins with
ve.extendClass(), either one becomes inheritClass and one
a mixin, both to mixinClass().
No visible changes should come from this commit as the
instances still all have the same visible properties in the
end. No more or less than before.
* Misc.:
- Be consistent in calling parent constructors in the
same order as the inheritance.
- Add missing @extends and @param documentation.
- Replace invalid {Integer} type hint with {Number}.
- Consistent doc comments order:
@class, @abstract, @constructor, @extends, @params.
- Fix indentation errors
A fairly common mistake was a superfluous space before the
identifier on the assignment line directly below the
documentation comment.
$ ack "^ [^*]" --js modules/ve
- Typo "Inhertiance" -> "Inheritance".
- Replacing the other confusing comment "Inheritance" (inside
the constructor) with "Parent constructor".
- Add missing @abstract for ve.ui.Tool.
- Corrected ve.FormatDropdownTool to ve.ui.FormatDropdownTool.js
- Add function names to all @constructor functions. Now that we
have inheritance it is important and useful to have these
functions not be anonymous.
Example of debug shot: http://cl.ly/image/1j3c160w3D45
Makes the difference between
< documentNode;
> ve_dm_DocumentNode
...
: ve_dm_BranchNode
...
: ve_dm_Node
...
: ve_dm_Node
...
: Object
...
without names (current situation):
< documentNode;
> Object
...
: Object
...
: Object
...
: Object
...
: Object
...
though before this commit, it really looks like this
(flattened since ve.extendClass really did a mixin):
< documentNode;
> Object
...
...
...
Pattern in Sublime (case-sensitive) to find nameless
constructor functions:
"^ve\..*\.([A-Z])([^\.]+) = function \("
Change-Id: Iab763954fb8cf375900d7a9a92dec1c755d5407e
2012-09-05 06:07:47 +00:00
|
|
|
/* Inheritance */
|
|
|
|
|
2012-11-07 20:09:18 +00:00
|
|
|
ve.inheritClass( ve.Factory, ve.Registry );
|
Object management: Object create/inherit/clone utilities
* For the most common case:
- replace ve.extendClass with ve.inheritClass (chose slightly
different names to detect usage of the old/new one, and I
like 'inherit' better).
- move it up to below the constructor, see doc block for why.
* Cases where more than 2 arguments were passed to
ve.extendClass are handled differently depending on the case.
In case of a longer inheritance tree, the other arguments
could be omitted (like in "ve.ce.FooBar, ve.FooBar,
ve.Bar". ve.ce.FooBar only needs to inherit from ve.FooBar,
because ve.ce.FooBar inherits from ve.Bar).
In the case of where it previously had two mixins with
ve.extendClass(), either one becomes inheritClass and one
a mixin, both to mixinClass().
No visible changes should come from this commit as the
instances still all have the same visible properties in the
end. No more or less than before.
* Misc.:
- Be consistent in calling parent constructors in the
same order as the inheritance.
- Add missing @extends and @param documentation.
- Replace invalid {Integer} type hint with {Number}.
- Consistent doc comments order:
@class, @abstract, @constructor, @extends, @params.
- Fix indentation errors
A fairly common mistake was a superfluous space before the
identifier on the assignment line directly below the
documentation comment.
$ ack "^ [^*]" --js modules/ve
- Typo "Inhertiance" -> "Inheritance".
- Replacing the other confusing comment "Inheritance" (inside
the constructor) with "Parent constructor".
- Add missing @abstract for ve.ui.Tool.
- Corrected ve.FormatDropdownTool to ve.ui.FormatDropdownTool.js
- Add function names to all @constructor functions. Now that we
have inheritance it is important and useful to have these
functions not be anonymous.
Example of debug shot: http://cl.ly/image/1j3c160w3D45
Makes the difference between
< documentNode;
> ve_dm_DocumentNode
...
: ve_dm_BranchNode
...
: ve_dm_Node
...
: ve_dm_Node
...
: Object
...
without names (current situation):
< documentNode;
> Object
...
: Object
...
: Object
...
: Object
...
: Object
...
though before this commit, it really looks like this
(flattened since ve.extendClass really did a mixin):
< documentNode;
> Object
...
...
...
Pattern in Sublime (case-sensitive) to find nameless
constructor functions:
"^ve\..*\.([A-Z])([^\.]+) = function \("
Change-Id: Iab763954fb8cf375900d7a9a92dec1c755d5407e
2012-09-05 06:07:47 +00:00
|
|
|
|
2012-04-20 21:44:41 +00:00
|
|
|
/* Methods */
|
|
|
|
|
2012-04-23 18:46:13 +00:00
|
|
|
/**
|
2012-05-31 23:50:16 +00:00
|
|
|
* Register a constructor with the factory.
|
2012-05-14 22:05:09 +00:00
|
|
|
*
|
2012-05-04 20:31:14 +00:00
|
|
|
* @method
|
2012-10-04 20:42:00 +00:00
|
|
|
* @param {String|String[]} name Symbolic name or list of symbolic names
|
2012-05-31 23:50:16 +00:00
|
|
|
* @param {Function} constructor Constructor to use when creating object
|
2012-11-07 20:09:18 +00:00
|
|
|
* @throws 'constructor must be a function'
|
2012-04-23 18:46:13 +00:00
|
|
|
*/
|
2012-10-04 20:42:00 +00:00
|
|
|
ve.Factory.prototype.register = function ( name, constructor ) {
|
2012-04-23 18:46:13 +00:00
|
|
|
if ( typeof constructor !== 'function' ) {
|
2012-11-07 20:09:18 +00:00
|
|
|
throw new Error( 'constructor must be a function, cannot be a ' + typeof constructor );
|
2012-10-04 20:42:00 +00:00
|
|
|
}
|
2012-11-07 20:09:18 +00:00
|
|
|
ve.Registry.prototype.register.call( this, name, constructor );
|
2012-04-23 18:46:13 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
/**
|
2012-10-04 20:42:00 +00:00
|
|
|
* Create an object based on a name.
|
2012-05-14 22:05:09 +00:00
|
|
|
*
|
2012-10-04 20:42:00 +00:00
|
|
|
* Name is used to look up the constructor to use, while all additional arguments are passed to the
|
2012-04-30 22:42:36 +00:00
|
|
|
* constructor directly, so leaving one out will pass an undefined to the constructor.
|
2012-05-14 22:05:09 +00:00
|
|
|
*
|
2012-05-04 20:31:14 +00:00
|
|
|
* @method
|
2012-10-04 20:42:00 +00:00
|
|
|
* @param {string} name Object name.
|
2012-10-08 02:14:15 +00:00
|
|
|
* @param {mixed} [...] Arguments to pass to the constructor.
|
|
|
|
* @returns {Object} The new object.
|
2012-10-04 20:42:00 +00:00
|
|
|
* @throws 'Unknown object name'
|
2012-04-23 18:46:13 +00:00
|
|
|
*/
|
2012-10-04 20:42:00 +00:00
|
|
|
ve.Factory.prototype.create = function ( name ) {
|
2012-10-08 02:14:15 +00:00
|
|
|
var args, obj,
|
2012-10-04 20:42:00 +00:00
|
|
|
constructor = this.registry[name];
|
2012-10-08 02:14:15 +00:00
|
|
|
|
|
|
|
if ( constructor === undefined ) {
|
2012-11-07 20:09:18 +00:00
|
|
|
throw new Error( 'No class registered by that name: ' + name );
|
2012-04-23 18:46:13 +00:00
|
|
|
}
|
2012-10-08 02:14:15 +00:00
|
|
|
|
2012-10-04 20:42:00 +00:00
|
|
|
// Convert arguments to array and shift the first argument (name) off
|
2012-10-08 02:14:15 +00:00
|
|
|
args = Array.prototype.slice.call( arguments, 1 );
|
|
|
|
|
|
|
|
// We can't use the "new" operator with .apply directly because apply needs a
|
2012-10-04 20:42:00 +00:00
|
|
|
// context. So instead just do what "new" does: create an object that inherits from
|
2012-10-08 02:14:15 +00:00
|
|
|
// the constructor's prototype (which also makes it an "instanceof" the constructor),
|
|
|
|
// then invoke the constructor with the object as context, and return it (ignoring
|
|
|
|
// the constructor's return value).
|
|
|
|
obj = ve.createObject( constructor.prototype );
|
|
|
|
constructor.apply( obj, args );
|
|
|
|
return obj;
|
2012-04-20 21:44:41 +00:00
|
|
|
};
|