mediawiki-extensions-Visual.../modules/ve-mw/dm/metaitems/ve.dm.MWAlienMetaItem.js

/*!
 * VisualEditor DataModel MWAlienMetaItem class.
 *
 * @copyright 2011-2017 VisualEditor Team and others; see AUTHORS.txt
 * @license The MIT License (MIT); see LICENSE.txt
 */

/**
 * DataModel MW-specific meta item.
 *
 * @class
 * @abstract
 * @extends ve.dm.AlienMetaItem
 * @constructor
 * @param {Object} element Reference to element in meta-linmod
 */
ve.dm.MWAlienMetaItem = function VeDmMWAlienMetaItem() {
	// Parent constructor
	ve.dm.MWAlienMetaItem.super.apply( this, arguments );
};

/* Inheritance */

OO.inheritClass( ve.dm.MWAlienMetaItem, ve.dm.AlienMetaItem );

/* Static Properties */

ve.dm.MWAlienMetaItem.static.name = 'mwAlienMeta';

ve.dm.MWAlienMetaItem.static.matchRdfaTypes = [
	/^mw:/
];

// toDataElement inherited from AlienMetaItem, will return regular alienMeta elements but
// that's fine. This class is only here so that <meta>/<link> tags with an mw: type are correctly
// mapped to AlienMetaItem rather than AlienNode.

/* Registration */

ve.dm.modelRegistry.register( ve.dm.MWAlienMetaItem );
Change MetaNodes to MetaItems Rather than meta-things being special kinds of nodes, they are now a separate class of things (MetaItems) along with Nodes and Annotations. * Created a generic ve.dm.MetaItem that meta items inherit from. There will be actual instances of this class as well in the upcoming meta group code. * Renamed MetaNode to AlienMetaItem, MWMetaNode to MWMetaItem, 'metaBlock'/'metaInline' to 'alienMeta' * Created a MetaItemFactory, handle meta items in the ModelRegistry * Kill ve.dm.Node.static.isMeta, now obsolete ve.dm.Converter: * Pass in the MetaItemFactory * Look up data element types in the ModelRegistry rather than the NodeFactory, because they can be either nodes or meta items * Document createDataElement() and make explicit that modelClass can be either a node or a meta item * Handle meta items in getDataFromDom() * In getDomFromData(), check the MetaItemFactory as well as the NodeFactory Change-Id: I893709c6f3aa00f85c1b905b70f9f4e597bdeada 2013-02-21 23:01:04 +00:00			`/*!`
Add MW-specific meta items for categories and language links Also rename MWMetaItem to MWAlienMetaItem, because that's what it really is. Change-Id: I70695bfa3b8449c936a63f7b2a248b90c49dcea1 2013-03-21 19:18:52 +00:00			`* VisualEditor DataModel MWAlienMetaItem class.`
Change MetaNodes to MetaItems Rather than meta-things being special kinds of nodes, they are now a separate class of things (MetaItems) along with Nodes and Annotations. * Created a generic ve.dm.MetaItem that meta items inherit from. There will be actual instances of this class as well in the upcoming meta group code. * Renamed MetaNode to AlienMetaItem, MWMetaNode to MWMetaItem, 'metaBlock'/'metaInline' to 'alienMeta' * Created a MetaItemFactory, handle meta items in the ModelRegistry * Kill ve.dm.Node.static.isMeta, now obsolete ve.dm.Converter: * Pass in the MetaItemFactory * Look up data element types in the ModelRegistry rather than the NodeFactory, because they can be either nodes or meta items * Document createDataElement() and make explicit that modelClass can be either a node or a meta item * Handle meta items in getDataFromDom() * In getDomFromData(), check the MetaItemFactory as well as the NodeFactory Change-Id: I893709c6f3aa00f85c1b905b70f9f4e597bdeada 2013-02-21 23:01:04 +00:00			`*`
build: Bump file copyright notices for 2017 Change-Id: I3c20809e71cc0da58123e1b5f29c4f3aac945496 2017-01-03 16:58:33 +00:00			`* @copyright 2011-2017 VisualEditor Team and others; see AUTHORS.txt`
Change MetaNodes to MetaItems Rather than meta-things being special kinds of nodes, they are now a separate class of things (MetaItems) along with Nodes and Annotations. * Created a generic ve.dm.MetaItem that meta items inherit from. There will be actual instances of this class as well in the upcoming meta group code. * Renamed MetaNode to AlienMetaItem, MWMetaNode to MWMetaItem, 'metaBlock'/'metaInline' to 'alienMeta' * Created a MetaItemFactory, handle meta items in the ModelRegistry * Kill ve.dm.Node.static.isMeta, now obsolete ve.dm.Converter: * Pass in the MetaItemFactory * Look up data element types in the ModelRegistry rather than the NodeFactory, because they can be either nodes or meta items * Document createDataElement() and make explicit that modelClass can be either a node or a meta item * Handle meta items in getDataFromDom() * In getDomFromData(), check the MetaItemFactory as well as the NodeFactory Change-Id: I893709c6f3aa00f85c1b905b70f9f4e597bdeada 2013-02-21 23:01:04 +00:00			`* @license The MIT License (MIT); see LICENSE.txt`
			`*/`

			`/**`
			`* DataModel MW-specific meta item.`
			`*`
			`* @class`
			`* @abstract`
			`* @extends ve.dm.AlienMetaItem`
			`* @constructor`
			`* @param {Object} element Reference to element in meta-linmod`
			`*/`
Use super property to call parent methods Change-Id: I76982b844cf2871d7583463def4393e5bdc33aa2 2016-08-22 21:44:59 +00:00			`ve.dm.MWAlienMetaItem = function VeDmMWAlienMetaItem() {`
Change MetaNodes to MetaItems Rather than meta-things being special kinds of nodes, they are now a separate class of things (MetaItems) along with Nodes and Annotations. * Created a generic ve.dm.MetaItem that meta items inherit from. There will be actual instances of this class as well in the upcoming meta group code. * Renamed MetaNode to AlienMetaItem, MWMetaNode to MWMetaItem, 'metaBlock'/'metaInline' to 'alienMeta' * Created a MetaItemFactory, handle meta items in the ModelRegistry * Kill ve.dm.Node.static.isMeta, now obsolete ve.dm.Converter: * Pass in the MetaItemFactory * Look up data element types in the ModelRegistry rather than the NodeFactory, because they can be either nodes or meta items * Document createDataElement() and make explicit that modelClass can be either a node or a meta item * Handle meta items in getDataFromDom() * In getDomFromData(), check the MetaItemFactory as well as the NodeFactory Change-Id: I893709c6f3aa00f85c1b905b70f9f4e597bdeada 2013-02-21 23:01:04 +00:00			`// Parent constructor`
Use super property to call parent methods Change-Id: I76982b844cf2871d7583463def4393e5bdc33aa2 2016-08-22 21:44:59 +00:00			`ve.dm.MWAlienMetaItem.super.apply( this, arguments );`
Change MetaNodes to MetaItems Rather than meta-things being special kinds of nodes, they are now a separate class of things (MetaItems) along with Nodes and Annotations. * Created a generic ve.dm.MetaItem that meta items inherit from. There will be actual instances of this class as well in the upcoming meta group code. * Renamed MetaNode to AlienMetaItem, MWMetaNode to MWMetaItem, 'metaBlock'/'metaInline' to 'alienMeta' * Created a MetaItemFactory, handle meta items in the ModelRegistry * Kill ve.dm.Node.static.isMeta, now obsolete ve.dm.Converter: * Pass in the MetaItemFactory * Look up data element types in the ModelRegistry rather than the NodeFactory, because they can be either nodes or meta items * Document createDataElement() and make explicit that modelClass can be either a node or a meta item * Handle meta items in getDataFromDom() * In getDomFromData(), check the MetaItemFactory as well as the NodeFactory Change-Id: I893709c6f3aa00f85c1b905b70f9f4e597bdeada 2013-02-21 23:01:04 +00:00			`};`

			`/* Inheritance */`

Remove ve.{inheritClass,mixinClass} and use OO instead Change-Id: I8df9226a358a76b661eab6e967ff0d63d361f691 2013-10-11 21:44:09 +00:00			`OO.inheritClass( ve.dm.MWAlienMetaItem, ve.dm.AlienMetaItem );`
Change MetaNodes to MetaItems Rather than meta-things being special kinds of nodes, they are now a separate class of things (MetaItems) along with Nodes and Annotations. * Created a generic ve.dm.MetaItem that meta items inherit from. There will be actual instances of this class as well in the upcoming meta group code. * Renamed MetaNode to AlienMetaItem, MWMetaNode to MWMetaItem, 'metaBlock'/'metaInline' to 'alienMeta' * Created a MetaItemFactory, handle meta items in the ModelRegistry * Kill ve.dm.Node.static.isMeta, now obsolete ve.dm.Converter: * Pass in the MetaItemFactory * Look up data element types in the ModelRegistry rather than the NodeFactory, because they can be either nodes or meta items * Document createDataElement() and make explicit that modelClass can be either a node or a meta item * Handle meta items in getDataFromDom() * In getDomFromData(), check the MetaItemFactory as well as the NodeFactory Change-Id: I893709c6f3aa00f85c1b905b70f9f4e597bdeada 2013-02-21 23:01:04 +00:00
			`/* Static Properties */`

Consistent use of mw in HTML classes, and data element and annotation types MWfooBar or MWfoobar should be mwFooBar Change-Id: I30f0ef05960c9df218ef6f1cb161ff6ccd529bc7 2013-05-28 11:31:41 +00:00			`ve.dm.MWAlienMetaItem.static.name = 'mwAlienMeta';`
Change MetaNodes to MetaItems Rather than meta-things being special kinds of nodes, they are now a separate class of things (MetaItems) along with Nodes and Annotations. * Created a generic ve.dm.MetaItem that meta items inherit from. There will be actual instances of this class as well in the upcoming meta group code. * Renamed MetaNode to AlienMetaItem, MWMetaNode to MWMetaItem, 'metaBlock'/'metaInline' to 'alienMeta' * Created a MetaItemFactory, handle meta items in the ModelRegistry * Kill ve.dm.Node.static.isMeta, now obsolete ve.dm.Converter: * Pass in the MetaItemFactory * Look up data element types in the ModelRegistry rather than the NodeFactory, because they can be either nodes or meta items * Document createDataElement() and make explicit that modelClass can be either a node or a meta item * Handle meta items in getDataFromDom() * In getDomFromData(), check the MetaItemFactory as well as the NodeFactory Change-Id: I893709c6f3aa00f85c1b905b70f9f4e597bdeada 2013-02-21 23:01:04 +00:00
Store alien meta items' dom nodes only We don't need to decompose and rebuild alien meta items as they are uneditable, so just store the dom node and return that in toDomElements. Update test cases and several tests now need to use assert.deepEqualWithDomElements. Change-Id: I4d2eed267dac7855cb929a17d7aef566eaf0e287 2013-06-05 17:22:01 +00:00			`ve.dm.MWAlienMetaItem.static.matchRdfaTypes = [`
			`/^mw:/`
			`];`
Change MetaNodes to MetaItems Rather than meta-things being special kinds of nodes, they are now a separate class of things (MetaItems) along with Nodes and Annotations. * Created a generic ve.dm.MetaItem that meta items inherit from. There will be actual instances of this class as well in the upcoming meta group code. * Renamed MetaNode to AlienMetaItem, MWMetaNode to MWMetaItem, 'metaBlock'/'metaInline' to 'alienMeta' * Created a MetaItemFactory, handle meta items in the ModelRegistry * Kill ve.dm.Node.static.isMeta, now obsolete ve.dm.Converter: * Pass in the MetaItemFactory * Look up data element types in the ModelRegistry rather than the NodeFactory, because they can be either nodes or meta items * Document createDataElement() and make explicit that modelClass can be either a node or a meta item * Handle meta items in getDataFromDom() * In getDomFromData(), check the MetaItemFactory as well as the NodeFactory Change-Id: I893709c6f3aa00f85c1b905b70f9f4e597bdeada 2013-02-21 23:01:04 +00:00
			`// toDataElement inherited from AlienMetaItem, will return regular alienMeta elements but`
			`// that's fine. This class is only here so that <meta>/<link> tags with an mw: type are correctly`
			`// mapped to AlienMetaItem rather than AlienNode.`

			`/* Registration */`

Add MW-specific meta items for categories and language links Also rename MWMetaItem to MWAlienMetaItem, because that's what it really is. Change-Id: I70695bfa3b8449c936a63f7b2a248b90c49dcea1 2013-03-21 19:18:52 +00:00			`ve.dm.modelRegistry.register( ve.dm.MWAlienMetaItem );`