wikimedia/mediawiki-extensions-VisualEditor
1
0
Fork 0
mirror of https://gerrit.wikimedia.org/r/mediawiki/extensions/VisualEditor synced 2024-11-05 22:22:54 +00:00
Code Issues Packages Projects Releases Wiki Activity
mediawiki-extensions-Visual.../modules/ve-mw/ui/tools/buttons/ve.ui.MWMediaEditButtonTool.js

43 lines
1.2 KiB
JavaScript
Raw Normal View History

Support for editing captions of block images Bug: 38129 Change-Id: I02207e78f5c28eaccd9bc97a48baa78280192255
2013-06-18 22:58:10 +00:00
/*!
* VisualEditor UserInterface MWMediaEditButtonTool class.
*
* @copyright 2011-2013 VisualEditor Team and others; see AUTHORS.txt
* @license The MIT License (MIT); see LICENSE.txt
*/
/**
Consistency in MW*ButtonTool comments and naming Change-Id: Id71c7f862e43125599ecfc6eeb27719e1891489d
2013-07-26 11:04:19 +00:00
* UserInterface MediaWiki media edit button tool.
Support for editing captions of block images Bug: 38129 Change-Id: I02207e78f5c28eaccd9bc97a48baa78280192255
2013-06-18 22:58:10 +00:00
*
* @class
* @extends ve.ui.DialogButtonTool
* @constructor
* @param {ve.ui.Toolbar} toolbar
* @param {Object} [config] Config options
*/
ve.ui.MWMediaEditButtonTool = function VeUiMWMediaEditButtonTool( toolbar, config ) {
// Parent constructor
ve.ui.DialogButtonTool.call( this, toolbar, config );
};
/* Inheritance */
ve.inheritClass( ve.ui.MWMediaEditButtonTool, ve.ui.DialogButtonTool );
/* 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.MWMediaEditButtonTool.static.name = 'object/mediaEdit/mw';
Support for editing captions of block images Bug: 38129 Change-Id: I02207e78f5c28eaccd9bc97a48baa78280192255
2013-06-18 22:58:10 +00:00
ve.ui.MWMediaEditButtonTool.static.icon = 'picture';
ve.ui.MWMediaEditButtonTool.static.titleMessage = 'visualeditor-dialogbutton-media-tooltip';
ve.ui.MWMediaEditButtonTool.static.dialog = 'mwMediaEdit';
ve.ui.ViewRegistry annihilation Objectives: * Associate models with tools, rather than dialogs and inspectors * Move tool/model association utilities to ve.ui.ToolFactory * Obliterate the view registry Notes: The only special case for leaving modelClasses definitions in place is for the linkInspector. It uses these for selection expansion. Because tools can now override the static canEditModel method, we can dynamically evaluate a model, rather than be restricted to only comparing classes. This will be useful for disabling editors for models that are for some reason incomplete or otherwise broken and cannot be safely edited. Change-Id: I7adf254990112d90f1f808593a9111afc7a116b5
2013-06-26 21:54:51 +00:00
ve.ui.MWMediaEditButtonTool.static.modelClasses = [ ve.dm.MWBlockImageNode ];
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.MWMediaEditButtonTool.static.autoAdd = false;
Support for editing captions of block images Bug: 38129 Change-Id: I02207e78f5c28eaccd9bc97a48baa78280192255
2013-06-18 22:58:10 +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( 'object/mediaEdit/mw', ve.ui.MWMediaEditButtonTool );
Reference in a new issue Copy permalink