2010-09-04 04:00:09 +00:00
|
|
|
<?php
|
|
|
|
|
|
2010-09-15 00:58:59 +00:00
|
|
|
return array(
|
2010-09-04 04:00:09 +00:00
|
|
|
|
2011-08-01 21:46:54 +00:00
|
|
|
/* Special modules who have their own classes */
|
2010-11-22 23:55:37 +00:00
|
|
|
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'site' => array( 'class' => 'ResourceLoaderSiteModule' ),
|
2011-03-05 16:01:25 +00:00
|
|
|
'noscript' => array( 'class' => 'ResourceLoaderNoscriptModule' ),
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'startup' => array( 'class' => 'ResourceLoaderStartUpModule' ),
|
|
|
|
|
'user' => array( 'class' => 'ResourceLoaderUserModule' ),
|
2011-02-16 19:54:02 +00:00
|
|
|
'user.groups' => array( 'class' => 'ResourceLoaderUserGroupsModule' ),
|
2011-05-21 22:52:32 +00:00
|
|
|
'user.options' => array( 'class' => 'ResourceLoaderUserOptionsModule' ),
|
|
|
|
|
'user.tokens' => array( 'class' => 'ResourceLoaderUserTokensModule' ),
|
2011-06-29 00:08:25 +00:00
|
|
|
'filepage' => array( 'class' => 'ResourceLoaderFilePageModule' ),
|
2010-11-22 23:55:37 +00:00
|
|
|
|
2010-09-04 04:00:09 +00:00
|
|
|
/* Skins */
|
2010-11-22 23:55:37 +00:00
|
|
|
|
|
|
|
|
'skins.vector' => array(
|
2011-08-31 06:59:15 +00:00
|
|
|
'styles' => array(
|
|
|
|
|
'common/commonElements.css' => array( 'media' => 'screen' ),
|
|
|
|
|
'common/commonContent.css' => array( 'media' => 'screen' ),
|
|
|
|
|
'common/commonInterface.css' => array( 'media' => 'screen' ),
|
|
|
|
|
'vector/screen.css' => array( 'media' => 'screen' ),
|
|
|
|
|
),
|
2011-04-25 14:08:01 +00:00
|
|
|
'scripts' => 'vector/vector.js',
|
2011-02-08 12:06:32 +00:00
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
2011-06-06 22:08:52 +00:00
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'skins.monobook' => array(
|
|
|
|
|
'styles' => array(
|
2011-08-31 06:59:15 +00:00
|
|
|
'common/commonElements.css' => array( 'media' => 'screen' ),
|
|
|
|
|
'common/commonContent.css' => array( 'media' => 'screen' ),
|
|
|
|
|
'common/commonInterface.css' => array( 'media' => 'screen' ),
|
2011-02-08 12:06:32 +00:00
|
|
|
'monobook/main.css' => array( 'media' => 'screen' ),
|
2011-01-10 05:02:05 +00:00
|
|
|
),
|
2011-02-08 12:06:32 +00:00
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
2011-06-06 22:08:52 +00:00
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
2010-10-18 20:35:56 +00:00
|
|
|
),
|
2011-01-22 21:16:34 +00:00
|
|
|
'skins.simple' => array(
|
2011-02-08 12:06:32 +00:00
|
|
|
'styles' => array( 'simple/main.css' => array( 'media' => 'screen' ) ),
|
|
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
2011-06-06 22:08:52 +00:00
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
2011-01-22 21:16:34 +00:00
|
|
|
),
|
2011-01-22 21:29:39 +00:00
|
|
|
'skins.chick' => array(
|
2011-02-08 12:06:32 +00:00
|
|
|
'styles' => array( 'chick/main.css' => array( 'media' => 'screen,handheld' ) ),
|
|
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
2011-06-06 22:08:52 +00:00
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
2011-01-22 21:29:39 +00:00
|
|
|
),
|
2011-01-22 22:46:33 +00:00
|
|
|
'skins.modern' => array(
|
2011-09-17 02:32:36 +00:00
|
|
|
'styles' => array(
|
|
|
|
|
'modern/main.css' => array( 'media' => 'screen' ),
|
|
|
|
|
'modern/print.css' => array( 'media' => 'print' ),
|
|
|
|
|
),
|
2011-02-08 12:06:32 +00:00
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
2011-06-06 22:08:52 +00:00
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
2011-01-22 22:46:33 +00:00
|
|
|
),
|
2011-01-23 01:41:13 +00:00
|
|
|
'skins.cologneblue' => array(
|
2011-07-08 20:17:46 +00:00
|
|
|
'styles' => array( 'cologneblue/screen.css' => array( 'media' => 'screen' ) ),
|
2011-02-08 12:06:32 +00:00
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
2011-06-06 22:08:52 +00:00
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
2011-01-23 01:41:13 +00:00
|
|
|
),
|
|
|
|
|
'skins.nostalgia' => array(
|
2011-07-08 20:17:46 +00:00
|
|
|
'styles' => array( 'nostalgia/screen.css' => array( 'media' => 'screen' ) ),
|
2011-02-08 12:06:32 +00:00
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
2011-06-06 22:08:52 +00:00
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
2011-01-23 01:41:13 +00:00
|
|
|
),
|
|
|
|
|
'skins.standard' => array(
|
2011-02-08 12:06:32 +00:00
|
|
|
'styles' => array( 'common/wikistandard.css' => array( 'media' => 'screen' ) ),
|
|
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
2011-06-06 22:08:52 +00:00
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
2011-01-23 01:41:13 +00:00
|
|
|
),
|
2010-11-22 23:55:37 +00:00
|
|
|
|
2010-09-04 04:00:09 +00:00
|
|
|
/* jQuery */
|
2010-11-22 23:55:37 +00:00
|
|
|
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'jquery' => array(
|
2010-11-22 23:55:37 +00:00
|
|
|
'scripts' => 'resources/jquery/jquery.js',
|
2011-08-01 21:46:54 +00:00
|
|
|
'debugRaw' => false,
|
2010-11-05 06:53:14 +00:00
|
|
|
),
|
2010-11-22 23:55:37 +00:00
|
|
|
|
2010-09-04 04:00:09 +00:00
|
|
|
/* jQuery Plugins */
|
2010-11-22 23:55:37 +00:00
|
|
|
|
|
|
|
|
'jquery.async' => array(
|
2011-01-10 05:02:05 +00:00
|
|
|
'scripts' => 'resources/jquery/jquery.async.js',
|
2010-09-09 20:31:19 +00:00
|
|
|
),
|
2011-05-04 23:26:43 +00:00
|
|
|
'jquery.appear' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.appear.js',
|
|
|
|
|
),
|
2010-11-22 23:55:37 +00:00
|
|
|
'jquery.autoEllipsis' => array(
|
2010-12-23 14:16:20 +00:00
|
|
|
'scripts' => 'resources/jquery/jquery.autoEllipsis.js',
|
|
|
|
|
'dependencies' => 'jquery.highlightText',
|
2010-09-09 20:31:19 +00:00
|
|
|
),
|
2011-06-30 01:06:47 +00:00
|
|
|
'jquery.byteLength' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.byteLength.js',
|
|
|
|
|
),
|
2011-04-22 10:58:58 +00:00
|
|
|
'jquery.byteLimit' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.byteLimit.js',
|
2011-06-30 01:06:47 +00:00
|
|
|
'dependencies' => 'jquery.byteLength',
|
2011-04-22 10:58:58 +00:00
|
|
|
),
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'jquery.checkboxShiftClick' => array(
|
2011-01-10 05:02:05 +00:00
|
|
|
'scripts' => 'resources/jquery/jquery.checkboxShiftClick.js',
|
2010-10-27 15:02:18 +00:00
|
|
|
),
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'jquery.client' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.client.js',
|
2010-09-15 01:03:53 +00:00
|
|
|
),
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'jquery.collapsibleTabs' => array(
|
2011-01-10 05:02:05 +00:00
|
|
|
'scripts' => 'resources/jquery/jquery.collapsibleTabs.js',
|
2010-09-15 02:03:24 +00:00
|
|
|
),
|
2011-01-05 23:24:07 +00:00
|
|
|
'jquery.colorUtil' => array(
|
2011-01-10 05:02:05 +00:00
|
|
|
'scripts' => 'resources/jquery/jquery.colorUtil.js',
|
2011-01-05 23:24:07 +00:00
|
|
|
),
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'jquery.color' => array(
|
2011-01-05 23:24:07 +00:00
|
|
|
'scripts' => 'resources/jquery/jquery.color.js',
|
2011-01-10 05:02:05 +00:00
|
|
|
'dependencies' => 'jquery.colorUtil',
|
2010-09-09 20:31:19 +00:00
|
|
|
),
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'jquery.cookie' => array(
|
2011-01-10 05:02:05 +00:00
|
|
|
'scripts' => 'resources/jquery/jquery.cookie.js',
|
2010-09-09 20:31:19 +00:00
|
|
|
),
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'jquery.delayedBind' => array(
|
2011-01-10 05:02:05 +00:00
|
|
|
'scripts' => 'resources/jquery/jquery.delayedBind.js',
|
2010-09-09 20:31:19 +00:00
|
|
|
),
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'jquery.expandableField' => array(
|
2011-01-10 05:02:05 +00:00
|
|
|
'scripts' => 'resources/jquery/jquery.expandableField.js',
|
2011-07-14 17:26:32 +00:00
|
|
|
'dependencies' => 'jquery.delayedBind',
|
2010-09-09 20:31:19 +00:00
|
|
|
),
|
2011-01-18 18:25:42 +00:00
|
|
|
'jquery.form' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.form.js',
|
|
|
|
|
),
|
2011-07-13 22:46:17 +00:00
|
|
|
'jquery.getAttrs' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.getAttrs.js',
|
|
|
|
|
),
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'jquery.highlightText' => array(
|
2011-01-10 05:02:05 +00:00
|
|
|
'scripts' => 'resources/jquery/jquery.highlightText.js',
|
2010-09-09 20:31:19 +00:00
|
|
|
),
|
2010-12-26 20:41:08 +00:00
|
|
|
'jquery.hoverIntent' => array(
|
2011-01-10 05:02:05 +00:00
|
|
|
'scripts' => 'resources/jquery/jquery.hoverIntent.js',
|
2010-12-26 20:41:08 +00:00
|
|
|
),
|
2011-02-08 00:20:41 +00:00
|
|
|
'jquery.messageBox' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.messageBox.js',
|
|
|
|
|
'styles' => 'resources/jquery/jquery.messageBox.css',
|
Making a start with $.jsMessage. A more flexible way for messages. Supports grouping them and making the replacing of previous messages into option (the current jsMsg() function always replaces older messages. Time has shown that there is need for the ability to show older messages as well and grouping to avoid different scripts from erasing or clearing eachother's output (current Commons and a few other wikis have created similar functions to enable keeping previous messages)
* See also bug 26888. Not resolving the bug yet, this plugins needs a little more testing and should then be called from within mw.util.jsMessage with some wiki specific things.
Examples:
// Show a simple message in the default group
$.jsMessage( {
message: 'Hello',
target: 'mw-js-message'
} );
// Add a new message this time stating the defaults
$.jsMessage( {
message: 'World',
group: 'default',
replace: false,
target: 'mw-js-message'
} );
// Post a new message, replacing the previous ones
$.jsMessage( {
message: 'New',
group: 'default',
replace: true,
target: 'mw-js-message'
} );
// Add a messages in a new group (groups separated by a line)
$.jsMessage( {
message: 'A new group',
group: 'something',
target: 'mw-js-message'
} );
// Clear the default group
// See code comments for more info
$.jsMessage( {
message: '',
replace: true,
target: 'mw-js-message'
} );
// Clear the 'something'-group
// Since this leaves no visible groups, the main box will hide (slideUp) right after
$.jsMessage( {
message: '',
group: 'something',
replace: true,
target: 'mw-js-message'
} );
If testing goes well, mw.util.jsMsg(message, className, replace) will call
$.jsMessage( { message: message, group: className, replace: replace, target: $.jsMessage(ge' );
So it's more a backend plugin, not used directly by core modules.
But this way extensions or third party sites can easily re-use this plugin and/or create multiple message boxes
on one page, by calling $.jsMessageNew and giving an id and location for it on the page.
2011-02-04 02:17:14 +00:00
|
|
|
),
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'jquery.placeholder' => array(
|
2011-01-10 05:02:05 +00:00
|
|
|
'scripts' => 'resources/jquery/jquery.placeholder.js',
|
2010-10-05 23:24:56 +00:00
|
|
|
),
|
2011-04-21 19:33:53 +00:00
|
|
|
'jquery.json' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.json.js',
|
|
|
|
|
),
|
2010-12-06 16:09:50 +00:00
|
|
|
'jquery.localize' => array(
|
2011-01-10 05:02:05 +00:00
|
|
|
'scripts' => 'resources/jquery/jquery.localize.js',
|
2010-12-06 16:09:50 +00:00
|
|
|
),
|
2010-12-23 19:25:16 +00:00
|
|
|
'jquery.makeCollapsible' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.makeCollapsible.js',
|
|
|
|
|
'styles' => 'resources/jquery/jquery.makeCollapsible.css',
|
2010-12-23 23:34:32 +00:00
|
|
|
'messages' => array( 'collapsible-expand', 'collapsible-collapse' ),
|
2010-12-23 19:25:16 +00:00
|
|
|
),
|
2011-08-04 20:52:40 +00:00
|
|
|
'jquery.mockjax' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.mockjax.js',
|
|
|
|
|
),
|
2011-08-11 03:12:12 +00:00
|
|
|
'jquery.mwExtension' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.mwExtension.js',
|
2011-05-17 17:19:12 +00:00
|
|
|
),
|
2011-09-25 00:49:39 +00:00
|
|
|
'jquery.mw-jump' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.mw-jump.js',
|
|
|
|
|
),
|
2011-05-10 21:54:42 +00:00
|
|
|
'jquery.qunit' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.qunit.js',
|
|
|
|
|
'styles' => 'resources/jquery/jquery.qunit.css',
|
2011-08-11 14:28:16 +00:00
|
|
|
'position' => 'top',
|
|
|
|
|
),
|
|
|
|
|
'jquery.qunit.completenessTest' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.qunit.completenessTest.js',
|
2011-05-10 21:54:42 +00:00
|
|
|
),
|
2011-08-24 21:08:39 +00:00
|
|
|
'jquery.spinner' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.spinner.js',
|
|
|
|
|
'styles' => 'resources/jquery/jquery.spinner.css',
|
|
|
|
|
),
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'jquery.suggestions' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.suggestions.js',
|
|
|
|
|
'styles' => 'resources/jquery/jquery.suggestions.css',
|
2011-06-03 09:51:48 +00:00
|
|
|
'dependencies' => 'jquery.autoEllipsis',
|
2010-09-09 20:31:19 +00:00
|
|
|
),
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'jquery.tabIndex' => array(
|
2011-01-10 05:02:05 +00:00
|
|
|
'scripts' => 'resources/jquery/jquery.tabIndex.js',
|
2010-09-09 20:31:19 +00:00
|
|
|
),
|
Completely rewritten table sorting script.
Fixes Bug 8028, Bug 8115, Bug 15406, Bug 17141, Bug 8732
1. Sites can specify custom collations.
The script accepts an object "tableSorterCollation" which contains a lookup
table, how specific characters should be treated.
For example, after setting "tableSorterCollation={'ä':'ae', 'ß':'ss'};" in the
site's common.js any string containing an ä or Ä will be sorted as if it were a
'ae'.
2. Table rows can be forced to use a specific data type.
By setting class="sort-{Parsername}", the row will be parsed with the specified
algorithm. class="sort-date" would force date sorting etc.
The following parsers are available: text, IPAddress, number, url, currency,
date, isoDate, usLongDate, time
3. Execution time is reduced by half or more.
Sorting a 935 row * 8 columns table:
Browser Before After
-------- ------ -----
Chrome 10 90ms 42ms
Safari 5 115ms 48ms
Firefox 4 412ms 87ms
IE8 720ms 115ms
4. Based on the content language and the mdy vs dmy preference, the parser can
understand dates such as "17. März '11". wgMonthNames=[] and
wgMonthNamesShort=[]
in the content language and the mdy vs dmy preference are exported to js; A
table containing the following dates would be sorted correctly:
17. Jan. 01
23 Feb 1992
9.02.05
13 November 2001
14 Oktober '76
Was tested in ie6-8, chrome, safari 5, ff3 & ff4
2011-04-14 21:47:00 +00:00
|
|
|
'jquery.tablesorter' => array(
|
2011-05-03 11:44:35 +00:00
|
|
|
'scripts' => 'resources/jquery/jquery.tablesorter.js',
|
2011-10-02 11:08:12 +00:00
|
|
|
'styles' => 'resources/jquery/jquery.tablesorter.css',
|
2011-05-03 11:44:35 +00:00
|
|
|
'messages' => array( 'sort-descending', 'sort-ascending' ),
|
Completely rewritten table sorting script.
Fixes Bug 8028, Bug 8115, Bug 15406, Bug 17141, Bug 8732
1. Sites can specify custom collations.
The script accepts an object "tableSorterCollation" which contains a lookup
table, how specific characters should be treated.
For example, after setting "tableSorterCollation={'ä':'ae', 'ß':'ss'};" in the
site's common.js any string containing an ä or Ä will be sorted as if it were a
'ae'.
2. Table rows can be forced to use a specific data type.
By setting class="sort-{Parsername}", the row will be parsed with the specified
algorithm. class="sort-date" would force date sorting etc.
The following parsers are available: text, IPAddress, number, url, currency,
date, isoDate, usLongDate, time
3. Execution time is reduced by half or more.
Sorting a 935 row * 8 columns table:
Browser Before After
-------- ------ -----
Chrome 10 90ms 42ms
Safari 5 115ms 48ms
Firefox 4 412ms 87ms
IE8 720ms 115ms
4. Based on the content language and the mdy vs dmy preference, the parser can
understand dates such as "17. März '11". wgMonthNames=[] and
wgMonthNamesShort=[]
in the content language and the mdy vs dmy preference are exported to js; A
table containing the following dates would be sorted correctly:
17. Jan. 01
23 Feb 1992
9.02.05
13 November 2001
14 Oktober '76
Was tested in ie6-8, chrome, safari 5, ff3 & ff4
2011-04-14 21:47:00 +00:00
|
|
|
),
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'jquery.textSelection' => array(
|
2011-01-10 05:02:05 +00:00
|
|
|
'scripts' => 'resources/jquery/jquery.textSelection.js',
|
2010-09-09 20:31:19 +00:00
|
|
|
),
|
2011-08-04 20:52:40 +00:00
|
|
|
'jquery.xmldom' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.xmldom.js',
|
|
|
|
|
),
|
2011-08-01 21:46:54 +00:00
|
|
|
|
|
|
|
|
/* jQuery Tipsy */
|
|
|
|
|
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'jquery.tipsy' => array(
|
|
|
|
|
'scripts' => 'resources/jquery.tipsy/jquery.tipsy.js',
|
|
|
|
|
'styles' => 'resources/jquery.tipsy/jquery.tipsy.css',
|
2010-11-18 00:27:32 +00:00
|
|
|
),
|
2010-11-22 23:55:37 +00:00
|
|
|
|
2010-09-04 04:00:09 +00:00
|
|
|
/* jQuery UI */
|
2010-11-22 23:55:37 +00:00
|
|
|
|
2010-09-04 04:00:09 +00:00
|
|
|
// Core
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'jquery.ui.core' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.ui/jquery.ui.core.js',
|
|
|
|
|
'skinStyles' => array(
|
|
|
|
|
'default' => array(
|
|
|
|
|
'resources/jquery.ui/themes/default/jquery.ui.core.css',
|
|
|
|
|
'resources/jquery.ui/themes/default/jquery.ui.theme.css',
|
|
|
|
|
),
|
|
|
|
|
'vector' => array(
|
|
|
|
|
'resources/jquery.ui/themes/vector/jquery.ui.core.css',
|
|
|
|
|
'resources/jquery.ui/themes/vector/jquery.ui.theme.css',
|
|
|
|
|
),
|
|
|
|
|
),
|
|
|
|
|
'dependencies' => 'jquery',
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.ui.widget' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.ui/jquery.ui.widget.js',
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.ui.mouse' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.ui/jquery.ui.mouse.js',
|
2010-09-16 20:53:06 +00:00
|
|
|
'dependencies' => 'jquery.ui.widget',
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.ui.position' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.ui/jquery.ui.position.js',
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
2010-09-04 04:00:09 +00:00
|
|
|
// Interactions
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'jquery.ui.draggable' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.ui/jquery.ui.draggable.js',
|
2010-09-16 20:53:06 +00:00
|
|
|
'dependencies' => array( 'jquery.ui.core', 'jquery.ui.mouse', 'jquery.ui.widget' ),
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.ui.droppable' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.ui/jquery.ui.droppable.js',
|
2010-11-22 23:55:37 +00:00
|
|
|
'dependencies' => array(
|
2011-01-10 05:02:05 +00:00
|
|
|
'jquery.ui.core', 'jquery.ui.mouse', 'jquery.ui.widget', 'jquery.ui.draggable',
|
2010-11-05 06:53:14 +00:00
|
|
|
),
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.ui.resizable' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.ui/jquery.ui.resizable.js',
|
|
|
|
|
'skinStyles' => array(
|
|
|
|
|
'default' => 'resources/jquery.ui/themes/default/jquery.ui.resizable.css',
|
|
|
|
|
'vector' => 'resources/jquery.ui/themes/vector/jquery.ui.resizable.css',
|
|
|
|
|
),
|
2010-09-16 20:53:06 +00:00
|
|
|
'dependencies' => array( 'jquery.ui.core', 'jquery.ui.widget', 'jquery.ui.mouse' ),
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.ui.selectable' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.ui/jquery.ui.selectable.js',
|
|
|
|
|
'skinStyles' => array(
|
|
|
|
|
'default' => 'resources/jquery.ui/themes/default/jquery.ui.selectable.css',
|
|
|
|
|
'vector' => 'resources/jquery.ui/themes/vector/jquery.ui.selectable.css',
|
|
|
|
|
),
|
2010-09-16 20:53:06 +00:00
|
|
|
'dependencies' => array( 'jquery.ui.core', 'jquery.ui.widget', 'jquery.ui.mouse' ),
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.ui.sortable' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.ui/jquery.ui.sortable.js',
|
2010-09-16 20:53:06 +00:00
|
|
|
'dependencies' => array( 'jquery.ui.core', 'jquery.ui.widget', 'jquery.ui.mouse' ),
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
2010-09-04 04:00:09 +00:00
|
|
|
// Widgets
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'jquery.ui.accordion' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.ui/jquery.ui.accordion.js',
|
2010-09-16 20:53:06 +00:00
|
|
|
'dependencies' => array( 'jquery.ui.core', 'jquery.ui.widget' ),
|
2010-09-04 04:00:09 +00:00
|
|
|
'skinStyles' => array(
|
|
|
|
|
'default' => 'resources/jquery.ui/themes/default/jquery.ui.accordion.css',
|
|
|
|
|
'vector' => 'resources/jquery.ui/themes/vector/jquery.ui.accordion.css',
|
|
|
|
|
),
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.ui.autocomplete' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.ui/jquery.ui.autocomplete.js',
|
|
|
|
|
'dependencies' => array( 'jquery.ui.core', 'jquery.ui.widget', 'jquery.ui.position' ),
|
|
|
|
|
'skinStyles' => array(
|
|
|
|
|
'default' => 'resources/jquery.ui/themes/default/jquery.ui.autocomplete.css',
|
|
|
|
|
'vector' => 'resources/jquery.ui/themes/vector/jquery.ui.autocomplete.css',
|
|
|
|
|
),
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.ui.button' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.ui/jquery.ui.button.js',
|
|
|
|
|
'dependencies' => array( 'jquery.ui.core', 'jquery.ui.widget' ),
|
|
|
|
|
'skinStyles' => array(
|
|
|
|
|
'default' => 'resources/jquery.ui/themes/default/jquery.ui.button.css',
|
|
|
|
|
'vector' => 'resources/jquery.ui/themes/vector/jquery.ui.button.css',
|
|
|
|
|
),
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.ui.datepicker' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.ui/jquery.ui.datepicker.js',
|
|
|
|
|
'dependencies' => 'jquery.ui.core',
|
|
|
|
|
'skinStyles' => array(
|
|
|
|
|
'default' => 'resources/jquery.ui/themes/default/jquery.ui.datepicker.css',
|
|
|
|
|
'vector' => 'resources/jquery.ui/themes/vector/jquery.ui.datepicker.css',
|
|
|
|
|
),
|
|
|
|
|
'languageScripts' => array(
|
|
|
|
|
'af' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-af.js',
|
|
|
|
|
'ar' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-ar.js',
|
|
|
|
|
'az' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-az.js',
|
|
|
|
|
'bg' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-bg.js',
|
|
|
|
|
'bs' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-bs.js',
|
|
|
|
|
'ca' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-ca.js',
|
|
|
|
|
'cs' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-cs.js',
|
|
|
|
|
'da' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-da.js',
|
|
|
|
|
'de' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-de.js',
|
|
|
|
|
'el' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-el.js',
|
|
|
|
|
'en-gb' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-en-GB.js',
|
|
|
|
|
'eo' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-eo.js',
|
|
|
|
|
'es' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-es.js',
|
|
|
|
|
'et' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-et.js',
|
|
|
|
|
'eu' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-eu.js',
|
|
|
|
|
'fa' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-fa.js',
|
|
|
|
|
'fi' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-fi.js',
|
|
|
|
|
'fo' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-fo.js',
|
|
|
|
|
'fr-ch' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-fr-CH.js',
|
|
|
|
|
'fr' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-fr.js',
|
2011-10-03 22:41:27 +00:00
|
|
|
'gl' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-gl.js',
|
2010-09-04 04:00:09 +00:00
|
|
|
'he' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-he.js',
|
|
|
|
|
'hr' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-hr.js',
|
|
|
|
|
'hu' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-hu.js',
|
|
|
|
|
'hy' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-hy.js',
|
|
|
|
|
'id' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-id.js',
|
|
|
|
|
'is' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-is.js',
|
|
|
|
|
'it' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-it.js',
|
|
|
|
|
'ja' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-ja.js',
|
|
|
|
|
'ko' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-ko.js',
|
|
|
|
|
'lt' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-lt.js',
|
|
|
|
|
'lv' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-lv.js',
|
2011-10-03 22:41:27 +00:00
|
|
|
'ml' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-ml.js',
|
2010-09-04 04:00:09 +00:00
|
|
|
'ms' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-ms.js',
|
|
|
|
|
'nl' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-nl.js',
|
|
|
|
|
'no' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-no.js',
|
|
|
|
|
'pl' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-pl.js',
|
2011-10-03 22:41:27 +00:00
|
|
|
'pt' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-pt.js',
|
2010-09-04 04:00:09 +00:00
|
|
|
'pt-br' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-pt-BR.js',
|
2011-10-03 22:41:27 +00:00
|
|
|
'rm' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-rm.js',
|
2010-09-04 04:00:09 +00:00
|
|
|
'ro' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-ro.js',
|
|
|
|
|
'ru' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-ru.js',
|
|
|
|
|
'sk' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-sk.js',
|
|
|
|
|
'sl' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-sl.js',
|
|
|
|
|
'sq' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-sq.js',
|
|
|
|
|
'sr-sr' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-sr-SR.js',
|
|
|
|
|
'sr' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-sr.js',
|
|
|
|
|
'sv' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-sv.js',
|
|
|
|
|
'ta' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-ta.js',
|
|
|
|
|
'th' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-th.js',
|
|
|
|
|
'tr' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-tr.js',
|
|
|
|
|
'uk' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-uk.js',
|
|
|
|
|
'vi' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-vi.js',
|
|
|
|
|
'zh-cn' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-zh-CN.js',
|
|
|
|
|
'zh-hk' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-zh-HK.js',
|
2011-01-10 05:02:05 +00:00
|
|
|
'zh-tw' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-zh-TW.js',
|
2010-09-04 04:00:09 +00:00
|
|
|
),
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.ui.dialog' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.ui/jquery.ui.dialog.js',
|
2010-09-16 20:53:06 +00:00
|
|
|
'dependencies' => array(
|
|
|
|
|
'jquery.ui.core',
|
|
|
|
|
'jquery.ui.widget',
|
|
|
|
|
'jquery.ui.button',
|
|
|
|
|
'jquery.ui.draggable',
|
|
|
|
|
'jquery.ui.mouse',
|
|
|
|
|
'jquery.ui.position',
|
|
|
|
|
'jquery.ui.resizable',
|
|
|
|
|
),
|
2010-09-04 04:00:09 +00:00
|
|
|
'skinStyles' => array(
|
|
|
|
|
'default' => 'resources/jquery.ui/themes/default/jquery.ui.dialog.css',
|
|
|
|
|
'vector' => 'resources/jquery.ui/themes/vector/jquery.ui.dialog.css',
|
|
|
|
|
),
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.ui.progressbar' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.ui/jquery.ui.progressbar.js',
|
2010-09-16 20:53:06 +00:00
|
|
|
'dependencies' => array( 'jquery.ui.core', 'jquery.ui.widget' ),
|
2010-09-04 04:00:09 +00:00
|
|
|
'skinStyles' => array(
|
|
|
|
|
'default' => 'resources/jquery.ui/themes/default/jquery.ui.progressbar.css',
|
|
|
|
|
'vector' => 'resources/jquery.ui/themes/vector/jquery.ui.progressbar.css',
|
|
|
|
|
),
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.ui.slider' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.ui/jquery.ui.slider.js',
|
|
|
|
|
'dependencies' => array( 'jquery.ui.core', 'jquery.ui.widget', 'jquery.ui.mouse' ),
|
|
|
|
|
'skinStyles' => array(
|
|
|
|
|
'default' => 'resources/jquery.ui/themes/default/jquery.ui.slider.css',
|
|
|
|
|
'vector' => 'resources/jquery.ui/themes/vector/jquery.ui.slider.css',
|
|
|
|
|
),
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.ui.tabs' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.ui/jquery.ui.tabs.js',
|
2010-09-16 20:53:06 +00:00
|
|
|
'dependencies' => array( 'jquery.ui.core', 'jquery.ui.widget' ),
|
2010-09-04 04:00:09 +00:00
|
|
|
'skinStyles' => array(
|
|
|
|
|
'default' => 'resources/jquery.ui/themes/default/jquery.ui.tabs.css',
|
|
|
|
|
'vector' => 'resources/jquery.ui/themes/vector/jquery.ui.tabs.css',
|
|
|
|
|
),
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
2010-09-04 04:00:09 +00:00
|
|
|
// Effects
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'jquery.effects.core' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.effects/jquery.effects.core.js',
|
|
|
|
|
'dependencies' => 'jquery',
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.effects.blind' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.effects/jquery.effects.blind.js',
|
|
|
|
|
'dependencies' => 'jquery.effects.core',
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.effects.bounce' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.effects/jquery.effects.bounce.js',
|
|
|
|
|
'dependencies' => 'jquery.effects.core',
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.effects.clip' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.effects/jquery.effects.clip.js',
|
|
|
|
|
'dependencies' => 'jquery.effects.core',
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.effects.drop' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.effects/jquery.effects.drop.js',
|
|
|
|
|
'dependencies' => 'jquery.effects.core',
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.effects.explode' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.effects/jquery.effects.explode.js',
|
|
|
|
|
'dependencies' => 'jquery.effects.core',
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.effects.fold' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.effects/jquery.effects.fold.js',
|
|
|
|
|
'dependencies' => 'jquery.effects.core',
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.effects.highlight' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.effects/jquery.effects.highlight.js',
|
|
|
|
|
'dependencies' => 'jquery.effects.core',
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.effects.pulsate' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.effects/jquery.effects.pulsate.js',
|
|
|
|
|
'dependencies' => 'jquery.effects.core',
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.effects.scale' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.effects/jquery.effects.scale.js',
|
|
|
|
|
'dependencies' => 'jquery.effects.core',
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.effects.shake' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.effects/jquery.effects.shake.js',
|
|
|
|
|
'dependencies' => 'jquery.effects.core',
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.effects.slide' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.effects/jquery.effects.slide.js',
|
|
|
|
|
'dependencies' => 'jquery.effects.core',
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'jquery.effects.transfer' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/jquery.effects/jquery.effects.transfer.js',
|
|
|
|
|
'dependencies' => 'jquery.effects.core',
|
2011-05-14 13:45:07 +00:00
|
|
|
'group' => 'jquery.ui',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
2010-11-22 23:55:37 +00:00
|
|
|
|
2010-09-04 04:00:09 +00:00
|
|
|
/* MediaWiki */
|
2010-11-22 23:55:37 +00:00
|
|
|
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'mediawiki' => array(
|
2010-09-04 04:00:09 +00:00
|
|
|
'scripts' => 'resources/mediawiki/mediawiki.js',
|
|
|
|
|
'debugScripts' => 'resources/mediawiki/mediawiki.log.js',
|
2011-01-22 23:17:29 +00:00
|
|
|
'debugRaw' => false,
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
2011-03-05 12:48:32 +00:00
|
|
|
'mediawiki.htmlform' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki/mediawiki.htmlform.js',
|
|
|
|
|
),
|
Implement mw.Title in core
* Based on UploadWizard/resources/mw.Title.js
* Refactored to use local scope and prototypes instead of re-declaring them per-instance in the private scope through 'this' (re-use by reference, faster instantiation and performance)
* Fix potential ReferenceError in the check for wgArticlePath (inline if statements will fail for undeclared variables, needs typeof undefined check). Using mw.config instead to avoid this problem.
* The following two methods were not ported from UploadWizard because they were or became redundant and/or merged with another method:
-- setNameText (redundant with the improved setName)
-- setPrefix (redundant wit the improved setNamespace)
* Ported all jasmine tests to QUnit. Left them exactly the same to make sure it's compatible with UploadWizard. Perhaps I'll expand or adjust the suite later to be less file-specific, but for now make letting this revision go through TestSwarm to be sure it's compatible and behaves exactly the same.
* Added getName() method instead, replacing direct access to '_name' This in order to check for wgCaseSensitiveNamespaces (bug 29441; r90234)
-- Prevents breakages on wiktionary and other wikis with case sensitivity. ie. on a Wiktionary:
new mw.Title('apple').toString()
> "Apple"
-- This fix will make it return 'apple' instead of 'Apple' (that is, if 0 is in wgCaseSensitiveNamespaces).
* There used to be a strip-bug in scenarios where a namespace-like string appears inside of a title. Imagine pagename: "Category:Wikipedia:Foo bar" (exist on several wikis; NS_CATEGORY= 14)
new mw.Title( 'Wikipedia:Foo bar', 14 ).toString()
> "Category:Foo_bar" // Stripped "Wikipedia:" !!
In order to fix this:
-- Removed assumption that every title has a namespace prefix. UploadWizard/mw.Title has one initialization RegExp (which was ported as-is to "setAll"). In addition there is now a "setNameAndExtension" method (which doesn't extract or set the namespace). Now the above case:
new mw.Title( 'Wikipedia:Foo bar', 14 ).toString()
> "Category:Wikipedia_Foo_bar" // Better, but now the colon is gone..
-- In order to fix that, "\x3a" was removed from the clean() function. Colons are valid in MediaWiki titles, no need to escape.
new mw.Title( 'Wikipedia:Foo bar', 14 ).toString()
> "Category:Wikipedia:Foo_bar" // Yay!
* Last but not least, another little bug fixed due to the previous point. It also fixed a thrown exception in case a colon is part of the title in the main namespace (not rare for movies and books):
new mw.Title( 'The Wiki: Awesomeness')
> Error: mw.Title> Unrecognized canonical namespace: the_wiki
This exception is thrown from setNamespace(). That exception would make sense if setNamespace() was called by the user direcly, but when called from setAll() it should gracefully fallback by putting the prefix in the name instead and assuming NS_MAIN (just like the server side does). To achieve this I added a try/catch around setAll() and fallback to the new setNameAndExtension().
* Passes JSHint.
* Additional feature: exists(). Return true/false if known, otherwise null. Extensions can populate this for titles they are interested in and the front-end can construct url's and UI elements with correct redlink-status. Gadgets can populate it as well but that would require an API-request to get the information. A bit of a stub for later use, although I think it works fine.
* Bugfix in jquery.qunit.completenessTest.js (first triggered by the introduction of mw.Title). Don't traverse the 'constructor' property (recursive loop, ouch!)
---
(bug 29397) Implement mw.Title module in core
2011-06-18 09:17:09 +00:00
|
|
|
'mediawiki.Title' => array(
|
2011-08-29 23:36:48 +00:00
|
|
|
'scripts' => 'resources/mediawiki/mediawiki.Title.js',
|
2011-08-16 15:32:08 +00:00
|
|
|
'dependencies' => 'mediawiki.util',
|
Implement mw.Title in core
* Based on UploadWizard/resources/mw.Title.js
* Refactored to use local scope and prototypes instead of re-declaring them per-instance in the private scope through 'this' (re-use by reference, faster instantiation and performance)
* Fix potential ReferenceError in the check for wgArticlePath (inline if statements will fail for undeclared variables, needs typeof undefined check). Using mw.config instead to avoid this problem.
* The following two methods were not ported from UploadWizard because they were or became redundant and/or merged with another method:
-- setNameText (redundant with the improved setName)
-- setPrefix (redundant wit the improved setNamespace)
* Ported all jasmine tests to QUnit. Left them exactly the same to make sure it's compatible with UploadWizard. Perhaps I'll expand or adjust the suite later to be less file-specific, but for now make letting this revision go through TestSwarm to be sure it's compatible and behaves exactly the same.
* Added getName() method instead, replacing direct access to '_name' This in order to check for wgCaseSensitiveNamespaces (bug 29441; r90234)
-- Prevents breakages on wiktionary and other wikis with case sensitivity. ie. on a Wiktionary:
new mw.Title('apple').toString()
> "Apple"
-- This fix will make it return 'apple' instead of 'Apple' (that is, if 0 is in wgCaseSensitiveNamespaces).
* There used to be a strip-bug in scenarios where a namespace-like string appears inside of a title. Imagine pagename: "Category:Wikipedia:Foo bar" (exist on several wikis; NS_CATEGORY= 14)
new mw.Title( 'Wikipedia:Foo bar', 14 ).toString()
> "Category:Foo_bar" // Stripped "Wikipedia:" !!
In order to fix this:
-- Removed assumption that every title has a namespace prefix. UploadWizard/mw.Title has one initialization RegExp (which was ported as-is to "setAll"). In addition there is now a "setNameAndExtension" method (which doesn't extract or set the namespace). Now the above case:
new mw.Title( 'Wikipedia:Foo bar', 14 ).toString()
> "Category:Wikipedia_Foo_bar" // Better, but now the colon is gone..
-- In order to fix that, "\x3a" was removed from the clean() function. Colons are valid in MediaWiki titles, no need to escape.
new mw.Title( 'Wikipedia:Foo bar', 14 ).toString()
> "Category:Wikipedia:Foo_bar" // Yay!
* Last but not least, another little bug fixed due to the previous point. It also fixed a thrown exception in case a colon is part of the title in the main namespace (not rare for movies and books):
new mw.Title( 'The Wiki: Awesomeness')
> Error: mw.Title> Unrecognized canonical namespace: the_wiki
This exception is thrown from setNamespace(). That exception would make sense if setNamespace() was called by the user direcly, but when called from setAll() it should gracefully fallback by putting the prefix in the name instead and assuming NS_MAIN (just like the server side does). To achieve this I added a try/catch around setAll() and fallback to the new setNameAndExtension().
* Passes JSHint.
* Additional feature: exists(). Return true/false if known, otherwise null. Extensions can populate this for titles they are interested in and the front-end can construct url's and UI elements with correct redlink-status. Gadgets can populate it as well but that would require an API-request to get the information. A bit of a stub for later use, although I think it works fine.
* Bugfix in jquery.qunit.completenessTest.js (first triggered by the introduction of mw.Title). Don't traverse the 'constructor' property (recursive loop, ouch!)
---
(bug 29397) Implement mw.Title module in core
2011-06-18 09:17:09 +00:00
|
|
|
),
|
2011-10-03 22:41:27 +00:00
|
|
|
'mediawiki.Uri' => array(
|
2011-08-29 23:36:48 +00:00
|
|
|
'scripts' => 'resources/mediawiki/mediawiki.Uri.js',
|
2011-08-11 04:09:34 +00:00
|
|
|
),
|
2011-05-16 17:58:54 +00:00
|
|
|
'mediawiki.user' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki/mediawiki.user.js',
|
|
|
|
|
'dependencies' => array(
|
|
|
|
|
'jquery.cookie',
|
|
|
|
|
),
|
|
|
|
|
),
|
2011-08-01 21:46:54 +00:00
|
|
|
|
|
|
|
|
/* MediaWiki Action */
|
|
|
|
|
|
|
|
|
|
'mediawiki.action.edit' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.action/mediawiki.action.edit.js',
|
2011-06-22 21:27:12 +00:00
|
|
|
'dependencies' => array(
|
2011-08-01 21:46:54 +00:00
|
|
|
'jquery.textSelection',
|
|
|
|
|
'jquery.byteLimit',
|
2011-06-22 21:27:12 +00:00
|
|
|
),
|
|
|
|
|
),
|
2011-08-01 21:46:54 +00:00
|
|
|
'mediawiki.action.history' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.action/mediawiki.action.history.js',
|
|
|
|
|
'dependencies' => 'jquery.ui.button',
|
|
|
|
|
'group' => 'mediawiki.action.history',
|
|
|
|
|
),
|
|
|
|
|
'mediawiki.action.history.diff' => array(
|
|
|
|
|
'styles' => 'resources/mediawiki.action/mediawiki.action.history.diff.css',
|
|
|
|
|
'group' => 'mediawiki.action.history',
|
|
|
|
|
),
|
2011-08-01 22:13:32 +00:00
|
|
|
'mediawiki.action.view.dblClickEdit' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.action/mediawiki.action.view.dblClickEdit.js',
|
|
|
|
|
'dependencies' => 'mediawiki.util',
|
|
|
|
|
),
|
2011-08-01 21:46:54 +00:00
|
|
|
'mediawiki.action.view.metadata' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.action/mediawiki.action.view.metadata.js',
|
|
|
|
|
'messages' => array(
|
|
|
|
|
'metadata-expand',
|
|
|
|
|
'metadata-collapse',
|
|
|
|
|
),
|
|
|
|
|
),
|
|
|
|
|
'mediawiki.action.view.rightClickEdit' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.action/mediawiki.action.view.rightClickEdit.js',
|
|
|
|
|
),
|
|
|
|
|
'mediawiki.action.watch.ajax' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.action/mediawiki.action.watch.ajax.js',
|
|
|
|
|
'messages' => array(
|
|
|
|
|
'watch',
|
|
|
|
|
'unwatch',
|
|
|
|
|
'watching',
|
|
|
|
|
'unwatching',
|
|
|
|
|
'tooltip-ca-watch',
|
|
|
|
|
'tooltip-ca-unwatch',
|
|
|
|
|
'watcherrortext',
|
|
|
|
|
),
|
|
|
|
|
),
|
|
|
|
|
|
|
|
|
|
/* MediaWiki Language */
|
|
|
|
|
|
|
|
|
|
'mediawiki.language' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.language/mediawiki.language.js',
|
|
|
|
|
'languageScripts' => array(
|
|
|
|
|
'am' => 'resources/mediawiki.language/languages/am.js',
|
|
|
|
|
'ar' => 'resources/mediawiki.language/languages/ar.js',
|
|
|
|
|
'bat-smg' => 'resources/mediawiki.language/languages/bat-smg.js',
|
|
|
|
|
'be' => 'resources/mediawiki.language/languages/be.js',
|
|
|
|
|
'be-tarask' => 'resources/mediawiki.language/languages/be-tarask.js',
|
|
|
|
|
'bh' => 'resources/mediawiki.language/languages/bh.js',
|
|
|
|
|
'bs' => 'resources/mediawiki.language/languages/bs.js',
|
|
|
|
|
'cs' => 'resources/mediawiki.language/languages/cs.js',
|
|
|
|
|
'cu' => 'resources/mediawiki.language/languages/cu.js',
|
|
|
|
|
'cy' => 'resources/mediawiki.language/languages/cy.js',
|
|
|
|
|
'dsb' => 'resources/mediawiki.language/languages/dsb.js',
|
|
|
|
|
'fr' => 'resources/mediawiki.language/languages/fr.js',
|
|
|
|
|
'ga' => 'resources/mediawiki.language/languages/ga.js',
|
|
|
|
|
'gd' => 'resources/mediawiki.language/languages/gd.js',
|
|
|
|
|
'gv' => 'resources/mediawiki.language/languages/gv.js',
|
|
|
|
|
'he' => 'resources/mediawiki.language/languages/he.js',
|
|
|
|
|
'hi' => 'resources/mediawiki.language/languages/hi.js',
|
|
|
|
|
'hr' => 'resources/mediawiki.language/languages/hr.js',
|
|
|
|
|
'hsb' => 'resources/mediawiki.language/languages/hsb.js',
|
|
|
|
|
'hy' => 'resources/mediawiki.language/languages/hy.js',
|
|
|
|
|
'ksh' => 'resources/mediawiki.language/languages/ksh.js',
|
|
|
|
|
'ln' => 'resources/mediawiki.language/languages/ln.js',
|
|
|
|
|
'lt' => 'resources/mediawiki.language/languages/lt.js',
|
|
|
|
|
'lv' => 'resources/mediawiki.language/languages/lv.js',
|
|
|
|
|
'mg' => 'resources/mediawiki.language/languages/mg.js',
|
|
|
|
|
'mk' => 'resources/mediawiki.language/languages/mk.js',
|
|
|
|
|
'mo' => 'resources/mediawiki.language/languages/mo.js',
|
|
|
|
|
'mt' => 'resources/mediawiki.language/languages/mt.js',
|
2011-09-26 06:08:46 +00:00
|
|
|
'nl' => 'resources/mediawiki.language/languages/nl.js',
|
2011-08-01 21:46:54 +00:00
|
|
|
'nso' => 'resources/mediawiki.language/languages/nso.js',
|
|
|
|
|
'pl' => 'resources/mediawiki.language/languages/pl.js',
|
2011-09-26 06:08:46 +00:00
|
|
|
'pt' => 'resources/mediawiki.language/languages/pt.js',
|
2011-08-01 21:46:54 +00:00
|
|
|
'pt-br' => 'resources/mediawiki.language/languages/pt-br.js',
|
|
|
|
|
'ro' => 'resources/mediawiki.language/languages/ro.js',
|
|
|
|
|
'ru' => 'resources/mediawiki.language/languages/ru.js',
|
|
|
|
|
'se' => 'resources/mediawiki.language/languages/se.js',
|
|
|
|
|
'sh' => 'resources/mediawiki.language/languages/sh.js',
|
|
|
|
|
'sk' => 'resources/mediawiki.language/languages/sk.js',
|
|
|
|
|
'sl' => 'resources/mediawiki.language/languages/sl.js',
|
|
|
|
|
'sma' => 'resources/mediawiki.language/languages/sma.js',
|
|
|
|
|
'sr-ec' => 'resources/mediawiki.language/languages/sr-ec.js',
|
|
|
|
|
'sr-el' => 'resources/mediawiki.language/languages/sr-el.js',
|
|
|
|
|
'sr' => 'resources/mediawiki.language/languages/sr.js',
|
|
|
|
|
'ti' => 'resources/mediawiki.language/languages/ti.js',
|
|
|
|
|
'tl' => 'resources/mediawiki.language/languages/tl.js',
|
|
|
|
|
'uk' => 'resources/mediawiki.language/languages/uk.js',
|
|
|
|
|
'wa' => 'resources/mediawiki.language/languages/wa.js',
|
2011-06-22 21:27:12 +00:00
|
|
|
),
|
|
|
|
|
),
|
2011-08-01 21:46:54 +00:00
|
|
|
|
|
|
|
|
/* MediaWiki Libs */
|
|
|
|
|
|
|
|
|
|
'mediawiki.libs.jpegmeta' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.libs/mediawiki.libs.jpegmeta.js',
|
|
|
|
|
),
|
|
|
|
|
|
|
|
|
|
/* MediaWiki Page */
|
|
|
|
|
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'mediawiki.util' => array(
|
2011-06-14 17:44:02 +00:00
|
|
|
'scripts' => 'resources/mediawiki/mediawiki.util.js',
|
2011-01-22 23:17:29 +00:00
|
|
|
'dependencies' => array(
|
|
|
|
|
'jquery.client',
|
|
|
|
|
'jquery.cookie',
|
2011-02-08 00:20:41 +00:00
|
|
|
'jquery.messageBox',
|
2011-08-11 03:12:12 +00:00
|
|
|
'jquery.mwExtension',
|
2011-01-22 23:17:29 +00:00
|
|
|
),
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
2011-08-01 21:46:54 +00:00
|
|
|
'mediawiki.page.ready' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.page/mediawiki.page.ready.js',
|
2011-04-22 10:58:58 +00:00
|
|
|
'dependencies' => array(
|
2011-08-01 21:46:54 +00:00
|
|
|
'jquery.checkboxShiftClick',
|
|
|
|
|
'jquery.makeCollapsible',
|
|
|
|
|
'jquery.placeholder',
|
2011-09-25 00:49:39 +00:00
|
|
|
'jquery.mw-jump',
|
2011-09-02 21:17:54 +00:00
|
|
|
'mediawiki.util',
|
2011-04-22 10:58:58 +00:00
|
|
|
),
|
2011-01-19 03:59:11 +00:00
|
|
|
),
|
2011-08-01 21:46:54 +00:00
|
|
|
'mediawiki.page.startup' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.page/mediawiki.page.startup.js',
|
|
|
|
|
'dependencies' => array(
|
|
|
|
|
'jquery.client',
|
2011-05-21 18:33:48 +00:00
|
|
|
),
|
2011-08-01 21:46:54 +00:00
|
|
|
'position' => 'top',
|
2010-12-09 21:59:02 +00:00
|
|
|
),
|
2011-10-03 22:41:27 +00:00
|
|
|
|
2011-03-12 22:42:58 +00:00
|
|
|
|
2011-08-01 21:46:54 +00:00
|
|
|
/* MediaWiki Special pages */
|
2011-03-12 22:42:58 +00:00
|
|
|
|
|
|
|
|
'mediawiki.special' => array(
|
2011-06-28 14:28:11 +00:00
|
|
|
'scripts' => 'resources/mediawiki.special/mediawiki.special.js',
|
2011-03-12 22:42:58 +00:00
|
|
|
'styles' => 'resources/mediawiki.special/mediawiki.special.css',
|
|
|
|
|
),
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'mediawiki.special.preferences' => array(
|
2010-11-18 22:02:53 +00:00
|
|
|
'scripts' => 'resources/mediawiki.special/mediawiki.special.preferences.js',
|
|
|
|
|
'styles' => 'resources/mediawiki.special/mediawiki.special.preferences.css',
|
2011-01-10 04:40:57 +00:00
|
|
|
'messages' => array( 'email-address-validity-valid', 'email-address-validity-invalid' ),
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
2010-12-27 19:07:28 +00:00
|
|
|
'mediawiki.special.changeslist' => array(
|
|
|
|
|
'styles' => 'resources/mediawiki.special/mediawiki.special.changeslist.css',
|
|
|
|
|
'dependencies' => array( 'jquery.makeCollapsible' ),
|
|
|
|
|
),
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'mediawiki.special.search' => array(
|
2010-11-18 22:02:53 +00:00
|
|
|
'scripts' => 'resources/mediawiki.special/mediawiki.special.search.js',
|
2011-07-08 17:20:56 +00:00
|
|
|
'styles' => 'resources/mediawiki.special/mediawiki.special.search.css',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
2011-03-03 23:54:39 +00:00
|
|
|
'mediawiki.special.block' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.special/mediawiki.special.block.js',
|
|
|
|
|
),
|
2011-06-18 19:57:17 +00:00
|
|
|
'mediawiki.special.undelete' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.special/mediawiki.special.undelete.js',
|
|
|
|
|
),
|
2011-04-25 11:39:30 +00:00
|
|
|
'mediawiki.special.movePage' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.special/mediawiki.special.movePage.js',
|
|
|
|
|
'dependencies' => 'jquery.byteLimit',
|
|
|
|
|
),
|
2011-06-28 06:40:49 +00:00
|
|
|
'mediawiki.special.recentchanges' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.special/mediawiki.special.recentchanges.js',
|
|
|
|
|
'dependencies' => array( 'mediawiki.special' ),
|
2011-06-28 17:56:56 +00:00
|
|
|
'position' => 'top',
|
2011-06-28 06:40:49 +00:00
|
|
|
),
|
2010-12-26 22:01:26 +00:00
|
|
|
'mediawiki.special.upload' => array(
|
2011-01-22 23:17:29 +00:00
|
|
|
// @TODO: merge in remainder of mediawiki.legacy.upload
|
2010-12-26 22:01:26 +00:00
|
|
|
'scripts' => 'resources/mediawiki.special/mediawiki.special.upload.js',
|
2011-01-22 23:17:29 +00:00
|
|
|
'messages' => array(
|
|
|
|
|
'widthheight',
|
|
|
|
|
'size-bytes',
|
|
|
|
|
'size-kilobytes',
|
|
|
|
|
'size-megabytes',
|
|
|
|
|
'size-gigabytes',
|
2011-03-04 15:38:37 +00:00
|
|
|
'largefileserver',
|
2011-01-22 23:17:29 +00:00
|
|
|
),
|
2011-05-29 03:13:54 +00:00
|
|
|
'dependencies' => array( 'mediawiki.libs.jpegmeta' ),
|
2010-12-26 22:01:26 +00:00
|
|
|
),
|
2011-03-12 22:42:58 +00:00
|
|
|
|
2011-08-01 21:46:54 +00:00
|
|
|
/* MediaWiki Legacy */
|
2010-11-22 23:55:37 +00:00
|
|
|
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'mediawiki.legacy.ajax' => array(
|
2011-02-08 12:06:32 +00:00
|
|
|
'scripts' => 'common/ajax.js',
|
|
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
2011-06-06 22:08:52 +00:00
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
2010-09-04 04:00:09 +00:00
|
|
|
'dependencies' => 'mediawiki.legacy.wikibits',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'mediawiki.legacy.commonPrint' => array(
|
2011-02-08 12:06:32 +00:00
|
|
|
'styles' => array( 'common/commonPrint.css' => array( 'media' => 'print' ) ),
|
|
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
2011-06-06 22:08:52 +00:00
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'mediawiki.legacy.config' => array(
|
2011-02-08 12:06:32 +00:00
|
|
|
'scripts' => 'common/config.js',
|
|
|
|
|
'styles' => array( 'common/config.css', 'common/config-cc.css' ),
|
|
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
2011-06-06 22:08:52 +00:00
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
2010-09-04 04:00:09 +00:00
|
|
|
'dependencies' => 'mediawiki.legacy.wikibits',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'mediawiki.legacy.IEFixes' => array(
|
2011-02-08 12:06:32 +00:00
|
|
|
'scripts' => 'common/IEFixes.js',
|
|
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
2011-06-06 22:08:52 +00:00
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
2010-09-04 04:00:09 +00:00
|
|
|
'dependencies' => 'mediawiki.legacy.wikibits',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
2011-08-24 18:22:53 +00:00
|
|
|
'mediawiki.legacy.mwsuggest' => array(
|
|
|
|
|
'scripts' => 'common/mwsuggest.js',
|
|
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
|
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
|
|
|
|
'dependencies' => array( 'mediawiki.legacy.wikibits', 'jquery.client' ),
|
|
|
|
|
'messages' => array( 'search-mwsuggest-enabled', 'search-mwsuggest-disabled' ),
|
|
|
|
|
),
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
'mediawiki.legacy.preview' => array(
|
2011-02-08 12:06:32 +00:00
|
|
|
'scripts' => 'common/preview.js',
|
|
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
2011-06-06 22:08:52 +00:00
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
2010-09-04 04:00:09 +00:00
|
|
|
'dependencies' => 'mediawiki.legacy.wikibits',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'mediawiki.legacy.protect' => array(
|
2011-02-08 12:06:32 +00:00
|
|
|
'scripts' => 'common/protect.js',
|
|
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
2011-06-06 22:08:52 +00:00
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
2011-04-25 11:39:30 +00:00
|
|
|
'dependencies' => array(
|
|
|
|
|
'mediawiki.legacy.wikibits',
|
|
|
|
|
'jquery.byteLimit',
|
|
|
|
|
),
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'mediawiki.legacy.shared' => array(
|
2011-02-08 12:06:32 +00:00
|
|
|
'styles' => array( 'common/shared.css' => array( 'media' => 'screen' ) ),
|
|
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
2011-06-06 22:08:52 +00:00
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'mediawiki.legacy.oldshared' => array(
|
2011-02-08 12:06:32 +00:00
|
|
|
'styles' => array( 'common/oldshared.css' => array( 'media' => 'screen' ) ),
|
|
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
2011-06-06 22:08:52 +00:00
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'mediawiki.legacy.upload' => array(
|
2011-02-08 12:06:32 +00:00
|
|
|
'scripts' => 'common/upload.js',
|
|
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
2011-06-06 22:08:52 +00:00
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
2010-09-04 04:00:09 +00:00
|
|
|
'dependencies' => 'mediawiki.legacy.wikibits',
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'mediawiki.legacy.wikibits' => array(
|
2011-02-08 12:06:32 +00:00
|
|
|
'scripts' => 'common/wikibits.js',
|
|
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
2011-06-06 22:08:52 +00:00
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
2010-10-26 23:40:26 +00:00
|
|
|
'dependencies' => 'mediawiki.language',
|
2010-09-04 04:00:09 +00:00
|
|
|
'messages' => array( 'showtoc', 'hidetoc' ),
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
|
|
|
|
'mediawiki.legacy.wikiprintable' => array(
|
2011-02-08 12:06:32 +00:00
|
|
|
'styles' => array( 'common/wikiprintable.css' => array( 'media' => 'print' ) ),
|
|
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
2011-06-06 22:08:52 +00:00
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
* Made Resources.php return a pure-data array instead of an ugly mix of data and code. This allows the class code to be lazy-loaded with the autoloader, for a performance advantage especially on non-APC installs. And using the convention where if the class is omitted, ResourceLoaderFileModule is assumed, the registration code becomes shorter and simpler.
* Modified ResourceLoader to lazy-initialise module objects, for a further performance advantage.
* Deleted ResourceLoader::getModules(), provided getModuleNames() instead. Although the startup module needs this functionality, it's slow to generate, so to avoid misuse, it's better to provide a foolproof fast interface and let the startup module do the slow thing itself.
* Modified ResourceLoader::register() to optionally accept an info array instead of an object.
* Added $wgResourceModules, allowing extensions to efficiently define their own resource loader modules. The trouble with hooks is that they contain code, and code is slow. We've been through all this before with i18n. Hooks are useful as a performance tool only if you call them very rarely.
* Moved ResourceLoader settings to their own section in DefaultSettings.php
* Added options to ResourceLoaderFileModule equivalent to the $localBasePath and $remoteBasePath parameters, to allow it to be instantiated via the new array style. Also added remoteExtPath, which allows modules to be registered before $wgExtensionAssetsPath is known.
* Added OutputPage::getResourceLoader(), mostly for debugging.
* The time saving at the moment is about 5ms per request with no extensions, which is significant already with 6 load.php requests for a cold cache page view. This is a much more scalable interface; the relative saving will grow as more extensions are added which use this interface, especially for non-APC installs.
Although the interface is backwards compatible, extension updates will follow in a subsequent commit.
2010-11-19 10:41:06 +00:00
|
|
|
),
|
2010-10-28 21:01:56 +00:00
|
|
|
);
|
