Go to file
Timo Tijhof ca40077866 Clean up Target properties
Move target.surface from mw.Target to Target
* All targets use this, let's standardise it.

Move target.$document from mw.ViewPageTarget to Target
* It was initialised with null in mw.ViewPageTarget, but the
  assignment happened in mw.Target. So it should be moved up
  at least to mw.Target.
* Since it is useful to have in sa.Target as well, moved it up
  to the abstract Target, and implemented in sa.Target and
  immediately used in the standalone demo where we were already
  duplicating the find( '.ve-ce-documentNode' ).

Add missing target.setupDone = false; in sa.Target

Add missing target.toolbar to Target
* Was used in all subclasses, but never initialised in any of
  the constructors. Let's standardise this property name as well
  (instead of initialising it in three places).

Move target#event-surfaceReady from mw.Target to Target
* sa.Target uses it as well, and considering Platform#initialize
  is already standardised in the abstract class, Target#setup
  being deferred is most likely to happen in each target as well
  so let's avoid different events being invented for the same
  thing and consistently use 'surfaceReady'.

Change-Id: Ia8bde188a4cde7e1615c2ae9c5b758eefc5d9cb7
2013-12-19 02:16:20 +00:00
.docs Clean up HTML files, Gruntfile and remove index-phantomjs-tmp hack 2013-12-18 07:00:23 +00:00
bin Replace makeStaticLoader with a grunt task 2013-12-17 22:03:01 +01:00
build demo: Convert VisualEditor standalone demo to pure HTML+JS 2013-12-19 03:12:13 +01:00
demos Clean up Target properties 2013-12-19 02:16:20 +00:00
modules Clean up Target properties 2013-12-19 02:16:20 +00:00
.csslintrc
.gitignore Implement Grunt support (grunt jshint,csslint,qunit,watch) 2013-06-05 11:10:23 +00:00
.gitreview
.jscs.json Set up node-jscs, pass it, and configure in local Gruntfile 2013-12-06 10:37:27 -08:00
.jshintignore Add jquery.i18n files and RL module 2013-12-06 22:50:43 +00:00
.jshintrc oojs: Integrate with OOJS v1.0.0 2013-06-06 17:29:55 +02:00
ApiVisualEditor.php Show full language names in the MW language dialog 2013-12-06 13:10:33 +00:00
ApiVisualEditorEdit.php Implement serialization cache in VisualEditor API 2013-11-20 10:26:47 +00:00
AUTHORS.txt Add Moriel Schottlender to AUTHORS.txt and authors string 2013-10-23 11:24:03 -07:00
betafeatures-icon-VisualEditor-formulae-ltr.svg Adapt beta features icons for RTL 2013-11-08 18:33:53 +02:00
betafeatures-icon-VisualEditor-formulae-rtl.svg Adapt beta features icons for RTL 2013-11-08 18:33:53 +02:00
betafeatures-icon-VisualEditor-ltr.svg Adapt beta features icons for RTL 2013-11-08 18:33:53 +02:00
betafeatures-icon-VisualEditor-rtl.svg Adapt beta features icons for RTL 2013-11-08 18:33:53 +02:00
CONTRIBUTING.md doc: Get rid of 'static' property container in jsduck index 2013-11-19 10:21:39 +00:00
Gruntfile.js demo: Convert VisualEditor standalone demo to pure HTML+JS 2013-12-19 03:12:13 +01:00
LICENSE.txt
package.json grunt: Update devDependencies 2013-12-18 08:19:19 +01:00
README.md Updates to README.md and CODING.md 2013-09-17 19:09:25 -04:00
VisualEditor.hooks.php Update jquery.i18n to f6102aa4feddf3623c9fba3a3d31592c58204b58 2013-12-13 12:16:53 -08:00
VisualEditor.i18n.php Rebuild VisualEditor.i18n.php – 2013-12-18 19:57:00 2013-12-18 11:56:51 -08:00
VisualEditor.php Fix mw.util dependencies 2013-12-17 20:56:19 +00:00
VisualEditorDataModule.php Rename misspelled variable $parsedMesssages 2013-12-12 01:30:58 +00:00

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 CODING.md. Patch submissions are reviewed and managed with Gerrit. There is also API documentation available for the VisualEditor.