Roan Kattouw ee743f869d Use submodule for VisualEditor core ... * Add lib/ve. * Remove modules provided by VisualEditor core. * Update paths. * Remove VisualEditor core specific things from Gruntfile. * Remove entries from external.js already in lib/ve/.docs/external.js. * Implement build script to compose a jsduck index that includes all of VisualEditor core. Right now it includes VisualEditor's index as-is, and because those patterns (e.g. ve.dm.*Node) will also MW subclasses this means our category page will include MW classes under "VisualEditor (core)" (before the repo split, this was intentional). This is inevitable unless we list every class individually, or (the plan) until we move the MW subclasses out of the ve.* namespace and into mw.* somewhere. Bug: 45342 Change-Id: Iff45cd555430634c9fc341fd3b177c1e0625300b		2013-12-20 09:18:41 +00:00
..
categories.json	Use submodule for VisualEditor core	2013-12-20 09:18:41 +00:00
config.json	Use submodule for VisualEditor core	2013-12-20 09:18:41 +00:00
CustomTags.rb	Rename @emits to @fires so we're forward compatible with JSDuck 5	2013-10-22 19:11:16 +00:00
eg-iframe.html	Use submodule for VisualEditor core	2013-12-20 09:18:41 +00:00
eg-iframe.html.template	Clean up HTML files, Gruntfile and remove index-phantomjs-tmp hack	2013-12-18 07:00:23 +00:00
external.js	Use submodule for VisualEditor core	2013-12-20 09:18:41 +00:00
generate.sh	Add bin/ directory with updateStaticLoaders and generateDocs	2013-10-22 23:51:51 +02:00
MetaTags.rb	Rename @emits to @fires so we're forward compatible with JSDuck 5	2013-10-22 19:11:16 +00:00
mw-categories.json	Use submodule for VisualEditor core	2013-12-20 09:18:41 +00:00