Timo Tijhof 93b5e174f1 ve.init: Fix broken dependency between ve.js and ve.init.platform ... Depencency tree looked like this * ext.visualEditor.viewPageTarget - ve.init.platform - ve.init.target ** ext.visualEditor.core - (most ve.* classes) *** ext.visualEditor.base - ve.js Some of the ve classes are calling ve.msg from the global scope at load time (e.g. in the definition of static properties or in constructors of classes that were immediately instantiated in the same file). Platform needs to be initialised in the base module. ve.init.Platform.js was already there, but that's just an abstract base class. The the ve.init.platform property is set from the implementation classes' files. Updated makeStaticLoader.php and re-ran for test and demo html. The fake "Standalone Init" module is now gone, which shows that this was needed as test/ and demo/ already put their platform code in/after the 'ext.visualEditor.base' module in the html. Bug: 45175 Change-Id: I47d7d92495974572194700c98a219d22ecbfaf4b		2013-04-03 05:47:40 +02:00
..
makeStaticLoader.php	ve.init: Fix broken dependency between ve.js and ve.init.platform	2013-04-03 05:47:40 +02:00