mirror of
https://gerrit.wikimedia.org/r/mediawiki/extensions/VisualEditor
synced 2024-11-15 18:39:52 +00:00
35080a8646
This is really only about the methods name, but doesn't change any behavior. I realized we work with several different definitions of what "empty" means. There are at least two significant definitions: 1. When a parameter's value is the empty string or identical to the default value, the behavior of the template is the same. It will use the default value just as if the user entered it. The auto-value is a meaningful value in this scenario and can't be considered equal to the empty string. 2. The context here is when the user presses the back button. This will destroy all user input. But an auto-value is not user input. It will appear again when the user realizes they made a mistake. Nothing is lost. Personally, I would not use the word "empty" to describe this concept. Things like "containsUserProvidedValue", "isCustomValue", "isMeaningfulValue", … come to mind. These are all still a big vague. A "user provided" value can be identical to the default or auto-value. "Custom" how? I went for "containsValuableData" for now. Bug: T274551 Change-Id: I2912a35556795c867a6b2396cbad291e947f0ed6 |
||
---|---|---|
.jsduck | ||
.phan | ||
bin | ||
build | ||
i18n | ||
images | ||
includes | ||
lib | ||
maintenance | ||
modules | ||
screenshots | ||
.eslintrc.json | ||
.gitignore | ||
.gitmodules | ||
.gitreview | ||
.mailmap | ||
.phpcs.xml | ||
.stylelintrc.json | ||
AUTHORS.txt | ||
composer.json | ||
CONTRIBUTING.md | ||
extension.json | ||
Gruntfile.js | ||
jsduck.json | ||
LICENSE.txt | ||
package-lock.json | ||
package.json | ||
Rakefile | ||
README.md | ||
VisualEditor.i18n.alias.php |
VisualEditor
VisualEditor provides a visual editor for wiki pages. It is written in JavaScript and runs in a web browser.
It uses the Parsoid parser to convert wikitext documents to annotated HTML which the VisualEditor is able to load, modify and emit back to Parsoid at which point it is converted back into wikitext.
For more information about these projects, check out the VisualEditor and Parsoid pages on mediawiki.
Developing and installing
For information on installing VisualEditor on a local wiki, please see https://www.mediawiki.org/wiki/Extension:VisualEditor
For information about running tests and contributing code to VisualEditor, see CONTRIBUTING.md. Patch submissions are reviewed and managed with Gerrit. There is also API documentation available for the VisualEditor.
Terminology
- Apex: See https://www.mediawiki.org/wiki/Skin:Apex
- CE: ContentEditable
- DM: Data model
- Invocation: Here the act of calling a template from a page, visible as e.g.
{{reflist}}
in the wikitext. - MW: MediaWiki
- Page: See https://www.mediawiki.org/wiki/OOUI/Layouts/Booklets_and_Pages
- Parameter: A template parameter. Can be known (i.e. documented via TemplateData) or unknown.
- Part: A template-level entity in a transclusion, i.e. either a template, template placeholder, or wikitext snippet.
- SA: Standalone
- Template: See https://www.mediawiki.org/wiki/Help:Templates
- Transclusion: A sequence of one or more template invocations, possibly mixed with raw wikitext snippets.
- UI: User interface
- VE: VisualEditor
- WT: Wikitext