wikimedia/mediawiki-extensions-VisualEditor
1
0
Fork 0
mirror of https://gerrit.wikimedia.org/r/mediawiki/extensions/VisualEditor synced 2024-10-01 06:06:47 +00:00
Code Issues Packages Projects Releases Wiki Activity
mediawiki-extensions-Visual.../modules/ve-mw/ui/tools/dropdowns/ve.ui.MWFormatDropdownTool.js

54 lines
2.1 KiB
JavaScript
Raw Normal View History

Create MediaWiki specific nodes to contain MW specific rules. Heading and Preformatted nodes have rules that should only exist under a document node in MediaWiki. Two new node types have been created as has a new DropdownTool which uses these. The MW init options have been changed to use the new DropdownTool. Bug: 45295 Change-Id: I3f47e1ae1f5c1415bde58a75385e4bf5f4b8fffc
2013-03-01 01:17:02 +00:00
/*!
* VisualEditor UserInterface MWFormatDropdownTool class.
*
* @copyright 2011-2013 VisualEditor Team and others; see AUTHORS.txt
* @license The MIT License (MIT); see LICENSE.txt
*/
/**
* UserInterface format dropdown tool.
*
* @class
* @extends ve.ui.FormatDropdownTool
* @constructor
* @param {ve.ui.Toolbar} toolbar
*/
clean up: Consistently use MW instead of Mw in constructor names Most of 'em already do. Fixed the remaining ones. Change-Id: I1a7ccb27dd66a33265dcaddaa7d34953d328ff87
2013-08-07 09:45:48 +00:00
ve.ui.MWFormatDropdownTool = function VeUiMWFormatDropdownTool( toolbar, config ) {
Create MediaWiki specific nodes to contain MW specific rules. Heading and Preformatted nodes have rules that should only exist under a document node in MediaWiki. Two new node types have been created as has a new DropdownTool which uses these. The MW init options have been changed to use the new DropdownTool. Bug: 45295 Change-Id: I3f47e1ae1f5c1415bde58a75385e4bf5f4b8fffc
2013-03-01 01:17:02 +00:00
// Parent constructor
ve.ui.FormatDropdownTool.call( this, toolbar, config );
Toolbar API Objectives: * Make it possible to add items to toolbars without having to have all toolbars know about the items in advance * Make it possible to specialize an existing tool and have it be used instead of the base implementation Approach: * Tools are named using a path-style category/id/ext system, making them selectable, the latter component being used to differentiate extended tools from their base classes, but is ignored during selection * Toolbars have ToolGroups, which include or exclude tools by category or category/id, and order them by promoting and demoting selections of tools by category or category/id Future: * Add a way to place available but not yet placed tools in an "overflow" group * Add a mode to ToolGroup to make the tools a multi-column drop-down style list with labels so tools with less obvious icons are easier to identify - and probably use this as the overflow group Change-Id: I7625f861435a99ce3d7a2b1ece9731aaab1776f8
2013-08-09 18:29:09 +00:00
// Initialize
this.$.addClass( 've-ui-mwFormatDropdownTool' );
Create MediaWiki specific nodes to contain MW specific rules. Heading and Preformatted nodes have rules that should only exist under a document node in MediaWiki. Two new node types have been created as has a new DropdownTool which uses these. The MW init options have been changed to use the new DropdownTool. Bug: 45295 Change-Id: I3f47e1ae1f5c1415bde58a75385e4bf5f4b8fffc
2013-03-01 01:17:02 +00:00
};
/* Inheritance */
ve.inheritClass( ve.ui.MWFormatDropdownTool, ve.ui.FormatDropdownTool );
/* Static Properties */
Toolbar API Objectives: * Make it possible to add items to toolbars without having to have all toolbars know about the items in advance * Make it possible to specialize an existing tool and have it be used instead of the base implementation Approach: * Tools are named using a path-style category/id/ext system, making them selectable, the latter component being used to differentiate extended tools from their base classes, but is ignored during selection * Toolbars have ToolGroups, which include or exclude tools by category or category/id, and order them by promoting and demoting selections of tools by category or category/id Future: * Add a way to place available but not yet placed tools in an "overflow" group * Add a mode to ToolGroup to make the tools a multi-column drop-down style list with labels so tools with less obvious icons are easier to identify - and probably use this as the overflow group Change-Id: I7625f861435a99ce3d7a2b1ece9731aaab1776f8
2013-08-09 18:29:09 +00:00
ve.ui.MWFormatDropdownTool.static.name = 'format/convert/mw';
Create MediaWiki specific nodes to contain MW specific rules. Heading and Preformatted nodes have rules that should only exist under a document node in MediaWiki. Two new node types have been created as has a new DropdownTool which uses these. The MW init options have been changed to use the new DropdownTool. Bug: 45295 Change-Id: I3f47e1ae1f5c1415bde58a75385e4bf5f4b8fffc
2013-03-01 01:17:02 +00:00
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.ui.MWFormatDropdownTool.static.items[1].data.type = 'mwHeading';
Discourage (ab)use of H1s, and relabel them Re-label the headings in the MWFormatDropdownTool with MW-specific headings per bug 43334, reduce the size of the dropdown's contents a little to make the headings less vibrant, and move the H1 option to the end of the list to further discourage its use. Note that there are some issues with the underlying structure here and our ability to split the repos into VE-core and VE-MW will need this to be refactored. Bug: 43334 Change-Id: I5a58b4dcebd6ceae0ffcd24f663429f25bdc3db9
2013-06-20 21:56:54 +00:00
ve.ui.MWFormatDropdownTool.static.items[1].label = 'visualeditor-formatdropdown-format-mw-heading1';
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.ui.MWFormatDropdownTool.static.items[2].data.type = 'mwHeading';
Discourage (ab)use of H1s, and relabel them Re-label the headings in the MWFormatDropdownTool with MW-specific headings per bug 43334, reduce the size of the dropdown's contents a little to make the headings less vibrant, and move the H1 option to the end of the list to further discourage its use. Note that there are some issues with the underlying structure here and our ability to split the repos into VE-core and VE-MW will need this to be refactored. Bug: 43334 Change-Id: I5a58b4dcebd6ceae0ffcd24f663429f25bdc3db9
2013-06-20 21:56:54 +00:00
ve.ui.MWFormatDropdownTool.static.items[2].label = 'visualeditor-formatdropdown-format-mw-heading2';
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.ui.MWFormatDropdownTool.static.items[3].data.type = 'mwHeading';
Discourage (ab)use of H1s, and relabel them Re-label the headings in the MWFormatDropdownTool with MW-specific headings per bug 43334, reduce the size of the dropdown's contents a little to make the headings less vibrant, and move the H1 option to the end of the list to further discourage its use. Note that there are some issues with the underlying structure here and our ability to split the repos into VE-core and VE-MW will need this to be refactored. Bug: 43334 Change-Id: I5a58b4dcebd6ceae0ffcd24f663429f25bdc3db9
2013-06-20 21:56:54 +00:00
ve.ui.MWFormatDropdownTool.static.items[3].label = 'visualeditor-formatdropdown-format-mw-heading3';
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.ui.MWFormatDropdownTool.static.items[4].data.type = 'mwHeading';
Discourage (ab)use of H1s, and relabel them Re-label the headings in the MWFormatDropdownTool with MW-specific headings per bug 43334, reduce the size of the dropdown's contents a little to make the headings less vibrant, and move the H1 option to the end of the list to further discourage its use. Note that there are some issues with the underlying structure here and our ability to split the repos into VE-core and VE-MW will need this to be refactored. Bug: 43334 Change-Id: I5a58b4dcebd6ceae0ffcd24f663429f25bdc3db9
2013-06-20 21:56:54 +00:00
ve.ui.MWFormatDropdownTool.static.items[4].label = 'visualeditor-formatdropdown-format-mw-heading4';
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.ui.MWFormatDropdownTool.static.items[5].data.type = 'mwHeading';
Discourage (ab)use of H1s, and relabel them Re-label the headings in the MWFormatDropdownTool with MW-specific headings per bug 43334, reduce the size of the dropdown's contents a little to make the headings less vibrant, and move the H1 option to the end of the list to further discourage its use. Note that there are some issues with the underlying structure here and our ability to split the repos into VE-core and VE-MW will need this to be refactored. Bug: 43334 Change-Id: I5a58b4dcebd6ceae0ffcd24f663429f25bdc3db9
2013-06-20 21:56:54 +00:00
ve.ui.MWFormatDropdownTool.static.items[5].label = 'visualeditor-formatdropdown-format-mw-heading5';
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.ui.MWFormatDropdownTool.static.items[6].data.type = 'mwHeading';
Discourage (ab)use of H1s, and relabel them Re-label the headings in the MWFormatDropdownTool with MW-specific headings per bug 43334, reduce the size of the dropdown's contents a little to make the headings less vibrant, and move the H1 option to the end of the list to further discourage its use. Note that there are some issues with the underlying structure here and our ability to split the repos into VE-core and VE-MW will need this to be refactored. Bug: 43334 Change-Id: I5a58b4dcebd6ceae0ffcd24f663429f25bdc3db9
2013-06-20 21:56:54 +00:00
ve.ui.MWFormatDropdownTool.static.items[6].label = 'visualeditor-formatdropdown-format-mw-heading6';
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.ui.MWFormatDropdownTool.static.items[7].data.type = 'mwPreformatted';
Create MediaWiki specific nodes to contain MW specific rules. Heading and Preformatted nodes have rules that should only exist under a document node in MediaWiki. Two new node types have been created as has a new DropdownTool which uses these. The MW init options have been changed to use the new DropdownTool. Bug: 45295 Change-Id: I3f47e1ae1f5c1415bde58a75385e4bf5f4b8fffc
2013-03-01 01:17:02 +00:00
Toolbar API Objectives: * Make it possible to add items to toolbars without having to have all toolbars know about the items in advance * Make it possible to specialize an existing tool and have it be used instead of the base implementation Approach: * Tools are named using a path-style category/id/ext system, making them selectable, the latter component being used to differentiate extended tools from their base classes, but is ignored during selection * Toolbars have ToolGroups, which include or exclude tools by category or category/id, and order them by promoting and demoting selections of tools by category or category/id Future: * Add a way to place available but not yet placed tools in an "overflow" group * Add a mode to ToolGroup to make the tools a multi-column drop-down style list with labels so tools with less obvious icons are easier to identify - and probably use this as the overflow group Change-Id: I7625f861435a99ce3d7a2b1ece9731aaab1776f8
2013-08-09 18:29:09 +00:00
// Move H1 (index 0) to the end (index 7) so as to make it less prominent and tempting to users
ve.ui.MWFormatDropdownTool.static.items.splice(
7, 0, ve.ui.MWFormatDropdownTool.static.items.splice( 1, 1 )[0]
);
Discourage (ab)use of H1s, and relabel them Re-label the headings in the MWFormatDropdownTool with MW-specific headings per bug 43334, reduce the size of the dropdown's contents a little to make the headings less vibrant, and move the H1 option to the end of the list to further discourage its use. Note that there are some issues with the underlying structure here and our ability to split the repos into VE-core and VE-MW will need this to be refactored. Bug: 43334 Change-Id: I5a58b4dcebd6ceae0ffcd24f663429f25bdc3db9
2013-06-20 21:56:54 +00:00
Create MediaWiki specific nodes to contain MW specific rules. Heading and Preformatted nodes have rules that should only exist under a document node in MediaWiki. Two new node types have been created as has a new DropdownTool which uses these. The MW init options have been changed to use the new DropdownTool. Bug: 45295 Change-Id: I3f47e1ae1f5c1415bde58a75385e4bf5f4b8fffc
2013-03-01 01:17:02 +00:00
/* Registration */
Toolbar API Objectives: * Make it possible to add items to toolbars without having to have all toolbars know about the items in advance * Make it possible to specialize an existing tool and have it be used instead of the base implementation Approach: * Tools are named using a path-style category/id/ext system, making them selectable, the latter component being used to differentiate extended tools from their base classes, but is ignored during selection * Toolbars have ToolGroups, which include or exclude tools by category or category/id, and order them by promoting and demoting selections of tools by category or category/id Future: * Add a way to place available but not yet placed tools in an "overflow" group * Add a mode to ToolGroup to make the tools a multi-column drop-down style list with labels so tools with less obvious icons are easier to identify - and probably use this as the overflow group Change-Id: I7625f861435a99ce3d7a2b1ece9731aaab1776f8
2013-08-09 18:29:09 +00:00
ve.ui.toolFactory.register( 'format/convert/mw', ve.ui.MWFormatDropdownTool );
Reference in a new issue Copy permalink