2010-09-04 04:00:09 +00:00
|
|
|
<?php
|
2012-10-02 20:24:33 +00:00
|
|
|
/**
|
|
|
|
|
* Definition of core ResourceLoader modules.
|
|
|
|
|
*
|
|
|
|
|
* This program is free software; you can redistribute it and/or modify
|
|
|
|
|
* it under the terms of the GNU General Public License as published by
|
|
|
|
|
* the Free Software Foundation; either version 2 of the License, or
|
|
|
|
|
* (at your option) any later version.
|
|
|
|
|
*
|
|
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
|
* GNU General Public License for more details.
|
|
|
|
|
*
|
|
|
|
|
* You should have received a copy of the GNU General Public License along
|
|
|
|
|
* with this program; if not, write to the Free Software Foundation, Inc.,
|
|
|
|
|
* 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
|
|
|
|
|
* http://www.gnu.org/copyleft/gpl.html
|
|
|
|
|
*
|
|
|
|
|
* @file
|
|
|
|
|
*/
|
2010-09-04 04:00:09 +00:00
|
|
|
|
2013-04-15 19:38:16 +00:00
|
|
|
if ( !defined( 'MEDIAWIKI' ) ) {
|
2013-01-17 18:58:13 +00:00
|
|
|
die( 'Not an entry point.' );
|
|
|
|
|
}
|
|
|
|
|
|
2010-09-15 00:58:59 +00:00
|
|
|
return array(
|
2010-09-04 04:00:09 +00:00
|
|
|
|
2013-03-06 01:31:08 +00:00
|
|
|
/**
|
|
|
|
|
* Special modules who have their own classes
|
|
|
|
|
*/
|
2010-11-22 23:55:37 +00:00
|
|
|
|
2012-03-04 22:56:43 +00:00
|
|
|
// Scripts managed by the local wiki (stored in the MediaWiki namespace)
|
* 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' ),
|
2012-03-04 22:56:43 +00:00
|
|
|
'filepage' => array( 'class' => 'ResourceLoaderFilePageModule' ),
|
2011-02-16 19:54:02 +00:00
|
|
|
'user.groups' => array( 'class' => 'ResourceLoaderUserGroupsModule' ),
|
2012-03-04 22:56:43 +00:00
|
|
|
|
|
|
|
|
// Scripts managed by the current user (stored in their user space)
|
|
|
|
|
'user' => array( 'class' => 'ResourceLoaderUserModule' ),
|
|
|
|
|
|
|
|
|
|
// Scripts generated based on the current user's preferences
|
2012-02-09 11:04:24 +00:00
|
|
|
'user.cssprefs' => array( 'class' => 'ResourceLoaderUserCSSPrefsModule' ),
|
2012-03-04 22:56:43 +00:00
|
|
|
|
|
|
|
|
// Populate mediawiki.user placeholders with information about the current user
|
|
|
|
|
'user.options' => array( 'class' => 'ResourceLoaderUserOptionsModule' ),
|
2011-05-21 22:52:32 +00:00
|
|
|
'user.tokens' => array( 'class' => 'ResourceLoaderUserTokensModule' ),
|
2010-11-22 23:55:37 +00:00
|
|
|
|
2012-04-02 13:01:10 +00:00
|
|
|
// Scripts for the dynamic language specific data, like grammar forms.
|
|
|
|
|
'mediawiki.language.data' => array( 'class' => 'ResourceLoaderLanguageDataModule' ),
|
|
|
|
|
|
2013-12-21 01:26:14 +00:00
|
|
|
/**
|
|
|
|
|
* Common skin styles, grouped into three graded levels.
|
|
|
|
|
*
|
|
|
|
|
* Level 1 "elements":
|
|
|
|
|
* The base level that only contains the most basic of common skin styles.
|
|
|
|
|
* Only styles for single elements are included, no styling for complex structures like the TOC
|
|
|
|
|
* is present. This level is for skins that want to implement the entire style of even content area
|
|
|
|
|
* structures like the TOC themselves.
|
|
|
|
|
*
|
|
|
|
|
* Level 2 "content":
|
|
|
|
|
* The most commonly used level for skins implemented from scratch. This level includes all the single
|
|
|
|
|
* element styles from "elements" as well as styles for complex structures such as the TOC that are output
|
|
|
|
|
* in the content area by MediaWiki rather than the skin. Essentially this is the common level that lets
|
|
|
|
|
* skins leave the style of the content area as it is normally styled, while leaving the rest of the skin
|
|
|
|
|
* up to the skin implementation.
|
|
|
|
|
*
|
|
|
|
|
* Level 3 "interface":
|
|
|
|
|
* The highest level, this stylesheet contains extra common styles for classes like .firstHeading, #contentSub,
|
|
|
|
|
* et cetera which are not outputted by MediaWiki but are common to skins like MonoBook, Vector, etc...
|
|
|
|
|
* Essentially this level is for styles that are common to MonoBook clones. And since practically every skin
|
|
|
|
|
* that currently exists within core is a MonoBook clone, all our core skins currently use this level.
|
|
|
|
|
*
|
|
|
|
|
* These modules are typically loaded by addModuleStyles which has absolutely no concept of dependency
|
|
|
|
|
* management. As a result the skins.common.* modules contain duplicate stylesheet references instead of
|
|
|
|
|
* setting 'dependencies' to the lower level the module is based on. For this reason avoid including multiple
|
|
|
|
|
* skins.common.* modules into your skin as this will result in duplicate css.
|
|
|
|
|
*/
|
|
|
|
|
'skins.common.elements' => array(
|
|
|
|
|
'styles' => array(
|
|
|
|
|
'common/commonElements.css' => array( 'media' => 'screen' ),
|
|
|
|
|
),
|
|
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
|
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
|
|
|
|
),
|
|
|
|
|
'skins.common.content' => array(
|
|
|
|
|
'styles' => array(
|
|
|
|
|
'common/commonElements.css' => array( 'media' => 'screen' ),
|
|
|
|
|
'common/commonContent.css' => array( 'media' => 'screen' ),
|
|
|
|
|
),
|
|
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
|
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
|
|
|
|
),
|
|
|
|
|
'skins.common.interface' => array(
|
|
|
|
|
// Used in the web installer. Test it after modifying this definition!
|
|
|
|
|
'styles' => array(
|
|
|
|
|
'common/commonElements.css' => array( 'media' => 'screen' ),
|
|
|
|
|
'common/commonContent.css' => array( 'media' => 'screen' ),
|
|
|
|
|
'common/commonInterface.css' => array( 'media' => 'screen' ),
|
|
|
|
|
),
|
|
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
|
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
|
|
|
|
),
|
|
|
|
|
|
2013-03-06 01:31:08 +00:00
|
|
|
/**
|
|
|
|
|
* Skins
|
|
|
|
|
* Be careful not to add 'scripts' to these modules,
|
|
|
|
|
* since they are loaded with OutputPage::addModuleStyles so that the skin styles
|
|
|
|
|
* apply without javascript.
|
|
|
|
|
* If a skin needs custom js in the interface, register a separate module
|
|
|
|
|
* and add it to the load queue with OutputPage::addModules.
|
|
|
|
|
*
|
|
|
|
|
* See Vector for an example.
|
|
|
|
|
*/
|
2011-11-11 00:17:38 +00:00
|
|
|
'skins.cologneblue' => array(
|
2013-04-06 14:24:21 +00:00
|
|
|
'styles' => array(
|
|
|
|
|
'cologneblue/screen.css' => array( 'media' => 'screen' ),
|
|
|
|
|
'cologneblue/print.css' => array( 'media' => 'print' ),
|
|
|
|
|
),
|
2011-11-11 00:17:38 +00:00
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
|
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
|
|
|
|
),
|
|
|
|
|
'skins.modern' => array(
|
2011-08-31 06:59:15 +00:00
|
|
|
'styles' => array(
|
2011-11-11 00:17:38 +00:00
|
|
|
'modern/main.css' => array( 'media' => 'screen' ),
|
|
|
|
|
'modern/print.css' => array( 'media' => 'print' ),
|
2011-08-31 06:59:15 +00:00
|
|
|
),
|
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
|
|
|
),
|
2013-12-05 01:53:18 +00:00
|
|
|
'skins.vector.styles' => array(
|
|
|
|
|
// Used in the web installer. Test it after modifying this definition!
|
2013-10-03 20:22:14 +00:00
|
|
|
'styles' => array(
|
2013-12-05 01:53:18 +00:00
|
|
|
'vector/styles.less',
|
|
|
|
|
),
|
|
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
|
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
|
|
|
|
),
|
|
|
|
|
'skins.monobook.styles' => array(
|
|
|
|
|
'styles' => array(
|
|
|
|
|
'monobook/main.css' => array( 'media' => 'screen' ),
|
2011-09-17 02:32:36 +00:00
|
|
|
),
|
2013-03-06 01:31:08 +00:00
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
|
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
|
|
|
|
),
|
|
|
|
|
'skins.vector.js' => array(
|
2013-03-24 23:10:35 +00:00
|
|
|
'scripts' => array(
|
|
|
|
|
'vector/collapsibleTabs.js',
|
2013-07-04 00:54:33 +00:00
|
|
|
'vector/vector.js',
|
2013-03-24 23:10:35 +00:00
|
|
|
),
|
|
|
|
|
'position' => 'top',
|
|
|
|
|
'dependencies' => 'jquery.delayedBind',
|
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
|
|
|
),
|
2013-09-09 23:49:39 +00:00
|
|
|
'skins.vector.collapsibleNav' => array(
|
|
|
|
|
'scripts' => array(
|
|
|
|
|
'vector/collapsibleNav.js',
|
|
|
|
|
),
|
|
|
|
|
'messages' => array(
|
|
|
|
|
'vector-collapsiblenav-more',
|
|
|
|
|
),
|
|
|
|
|
'dependencies' => array(
|
|
|
|
|
'jquery.client',
|
|
|
|
|
'jquery.cookie',
|
|
|
|
|
'jquery.tabIndex',
|
|
|
|
|
),
|
|
|
|
|
'remoteBasePath' => $GLOBALS['wgStylePath'],
|
|
|
|
|
'localBasePath' => $GLOBALS['wgStyleDirectory'],
|
|
|
|
|
'position' => 'bottom',
|
|
|
|
|
),
|
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,
|
2012-10-11 22:37:59 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
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
|
|
|
|
2011-05-04 23:26:43 +00:00
|
|
|
'jquery.appear' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.appear.js',
|
|
|
|
|
),
|
2012-01-23 17:02:51 +00:00
|
|
|
'jquery.arrowSteps' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.arrowSteps.js',
|
|
|
|
|
'styles' => 'resources/jquery/jquery.arrowSteps.css',
|
|
|
|
|
),
|
2011-11-11 00:17:38 +00:00
|
|
|
'jquery.async' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.async.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',
|
2013-10-15 22:31:14 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2010-09-09 20:31:19 +00:00
|
|
|
),
|
2012-07-30 21:16:56 +00:00
|
|
|
'jquery.badge' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.badge.js',
|
|
|
|
|
'styles' => 'resources/jquery/jquery.badge.css',
|
2013-02-19 12:38:38 +00:00
|
|
|
'dependencies' => 'mediawiki.language',
|
2012-07-30 21:16:56 +00:00
|
|
|
),
|
2011-06-30 01:06:47 +00:00
|
|
|
'jquery.byteLength' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.byteLength.js',
|
2013-10-11 08:31:00 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2011-06-30 01:06:47 +00:00
|
|
|
),
|
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',
|
2013-10-15 22:31:14 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
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',
|
2013-02-22 23:13:30 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2010-10-27 15:02:18 +00:00
|
|
|
),
|
2013-04-09 07:48:21 +00:00
|
|
|
'jquery.chosen' => array(
|
|
|
|
|
'scripts' => 'resources/jquery.chosen/chosen.jquery.js',
|
|
|
|
|
'styles' => 'resources/jquery.chosen/chosen.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.client' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.client.js',
|
2012-12-17 20:32:19 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
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.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
|
|
|
),
|
2011-11-11 00:17:38 +00:00
|
|
|
'jquery.colorUtil' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.colorUtil.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.cookie' => array(
|
2011-01-10 05:02:05 +00:00
|
|
|
'scripts' => 'resources/jquery/jquery.cookie.js',
|
2012-12-17 20:32:19 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
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-10-15 22:41:45 +00:00
|
|
|
'jquery.farbtastic' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.farbtastic.js',
|
|
|
|
|
'styles' => 'resources/jquery/jquery.farbtastic.css',
|
2011-10-15 23:16:26 +00:00
|
|
|
'dependencies' => 'jquery.colorUtil',
|
2011-10-15 22:41:45 +00:00
|
|
|
),
|
2012-01-04 01:28:01 +00:00
|
|
|
'jquery.footHovzer' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.footHovzer.js',
|
|
|
|
|
'styles' => 'resources/jquery/jquery.footHovzer.css',
|
|
|
|
|
),
|
2011-01-18 18:25:42 +00:00
|
|
|
'jquery.form' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.form.js',
|
|
|
|
|
),
|
2013-12-03 03:52:43 +00:00
|
|
|
'jquery.fullscreen' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.fullscreen.js',
|
|
|
|
|
),
|
2011-07-13 22:46:17 +00:00
|
|
|
'jquery.getAttrs' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.getAttrs.js',
|
2013-03-24 02:18:37 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2011-07-13 22:46:17 +00:00
|
|
|
),
|
Initial stab at responsive images for screen densities.
* adds $wgResponsiveImages setting, defaulting to true, to enable the feature
* adds 'srcset' attribute with 1.5x and 2x URLs to image links and image thumbs
* adds jquery.hidpi plugin to check pixel density and implement partial 'srcset' polyfill
** $.devicePixelRatio() returns window.devicePixelRatio, with compat fallback for IE 10
** $().hidpi() performs a 'srcset' polyfill for browsers with no native 'srcset' support
* adds mediawiki.hidpi RL script to trigger hidpi loads after main images load
Note that this is a work in progress. There will be places where this doesn't yet work which output their imgs differently. If moving from a low to high-DPI screen on a MacBook Pro Retina display, you won't see images load until you reload.
Confirmed basic images and thumbs in wikitext appear to work in Safari 6, Chrome 21, Firefox 18 nightly on MacBook Pro Retina display, and IE 10 in Windows 8 at 150% zoom, 200% zoom, and 140% and 180%-ratio Metro tablet sizes.
Internally this is still a bit of a hack; Linker::makeImageLink and Linker::makeThumbLink explicitly ask for 1.5x and 2x scaled versions and insert their URLs, if different, into the original thumbnail object which (in default handler) outputs the srcset. This means that a number of places that handle images differently won't see the higher-resolution versions, such as <gallery> and the large thumbnail on the File: description page.
At some point we may wish to redo some of how the MediaHandler stuff works so that requesting a single thumbnail automatically produces the extra sizes in all circumstances. We might also consider outputting a 'srcset' or multiple src sizes in 'imageinfo' API requests, which would make ApiForeignRepo/InstantCommons more efficient. (Currently it has to make three requests for each image to get the three sizes.)
Change-Id: Id80ebd07a1a9f401a2c2bfeb21aae987e5aa863b
2012-09-18 07:18:50 +00:00
|
|
|
'jquery.hidpi' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.hidpi.js',
|
2012-10-11 22:37:59 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
Initial stab at responsive images for screen densities.
* adds $wgResponsiveImages setting, defaulting to true, to enable the feature
* adds 'srcset' attribute with 1.5x and 2x URLs to image links and image thumbs
* adds jquery.hidpi plugin to check pixel density and implement partial 'srcset' polyfill
** $.devicePixelRatio() returns window.devicePixelRatio, with compat fallback for IE 10
** $().hidpi() performs a 'srcset' polyfill for browsers with no native 'srcset' support
* adds mediawiki.hidpi RL script to trigger hidpi loads after main images load
Note that this is a work in progress. There will be places where this doesn't yet work which output their imgs differently. If moving from a low to high-DPI screen on a MacBook Pro Retina display, you won't see images load until you reload.
Confirmed basic images and thumbs in wikitext appear to work in Safari 6, Chrome 21, Firefox 18 nightly on MacBook Pro Retina display, and IE 10 in Windows 8 at 150% zoom, 200% zoom, and 140% and 180%-ratio Metro tablet sizes.
Internally this is still a bit of a hack; Linker::makeImageLink and Linker::makeThumbLink explicitly ask for 1.5x and 2x scaled versions and insert their URLs, if different, into the original thumbnail object which (in default handler) outputs the srcset. This means that a number of places that handle images differently won't see the higher-resolution versions, such as <gallery> and the large thumbnail on the File: description page.
At some point we may wish to redo some of how the MediaHandler stuff works so that requesting a single thumbnail automatically produces the extra sizes in all circumstances. We might also consider outputting a 'srcset' or multiple src sizes in 'imageinfo' API requests, which would make ApiForeignRepo/InstantCommons more efficient. (Currently it has to make three requests for each image to get the three sizes.)
Change-Id: Id80ebd07a1a9f401a2c2bfeb21aae987e5aa863b
2012-09-18 07:18:50 +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.highlightText' => array(
|
2011-01-10 05:02:05 +00:00
|
|
|
'scripts' => 'resources/jquery/jquery.highlightText.js',
|
2012-08-27 17:43:14 +00:00
|
|
|
'dependencies' => 'jquery.mwExtension',
|
2013-10-15 22:31:14 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
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-04-21 19:33:53 +00:00
|
|
|
'jquery.json' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.json.js',
|
2013-02-08 01:03:03 +00:00
|
|
|
'targets' => array( 'mobile', 'desktop' ),
|
2011-04-21 19:33:53 +00:00
|
|
|
),
|
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' ),
|
2013-02-22 23:13:30 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
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-11-11 00:17:38 +00:00
|
|
|
'jquery.mw-jump' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.mw-jump.js',
|
2013-02-22 23:13:30 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2011-11-11 00:17:38 +00:00
|
|
|
),
|
2011-08-11 03:12:12 +00:00
|
|
|
'jquery.mwExtension' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.mwExtension.js',
|
2012-12-17 20:32:19 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2011-05-17 17:19:12 +00:00
|
|
|
),
|
2011-11-11 00:17:38 +00:00
|
|
|
'jquery.placeholder' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.placeholder.js',
|
2013-02-22 23:13:30 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2011-11-11 00:17:38 +00:00
|
|
|
),
|
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',
|
2013-02-22 23:13:30 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2011-08-11 14:28:16 +00:00
|
|
|
),
|
2012-01-03 18:33:26 +00:00
|
|
|
'jquery.qunit.completenessTest' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.qunit.completenessTest.js',
|
|
|
|
|
'dependencies' => 'jquery.qunit',
|
2013-02-22 23:13:30 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2012-01-03 18:33:26 +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',
|
|
|
|
|
),
|
2012-08-17 18:36:27 +00:00
|
|
|
'jquery.jStorage' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.jStorage.js',
|
|
|
|
|
'dependencies' => 'jquery.json',
|
|
|
|
|
),
|
* 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' ),
|
2013-03-23 22:21:46 +00:00
|
|
|
'dependencies' => array(
|
|
|
|
|
'jquery.mwExtension',
|
|
|
|
|
'mediawiki.language.months',
|
|
|
|
|
),
|
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',
|
2012-03-02 19:23:58 +00:00
|
|
|
'dependencies' => 'jquery.client',
|
2010-09-09 20:31:19 +00:00
|
|
|
),
|
2011-10-15 23:13:26 +00:00
|
|
|
'jquery.validate' => array(
|
|
|
|
|
'scripts' => 'resources/jquery/jquery.validate.js',
|
|
|
|
|
),
|
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' => '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',
|
2012-04-03 21:23:59 +00:00
|
|
|
'hi' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-hi.js',
|
2010-09-04 04:00:09 +00:00
|
|
|
'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',
|
2012-06-09 14:29:30 +00:00
|
|
|
'ka' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-ka.js',
|
2011-12-08 19:17:59 +00:00
|
|
|
'kk' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-kk.js',
|
2012-04-03 21:23:59 +00:00
|
|
|
'km' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-km.js',
|
2010-09-04 04:00:09 +00:00
|
|
|
'ko' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-ko.js',
|
2011-12-08 19:17:59 +00:00
|
|
|
'lb' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-lb.js',
|
2010-09-04 04:00:09 +00:00
|
|
|
'lt' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-lt.js',
|
|
|
|
|
'lv' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-lv.js',
|
2011-12-08 19:17:59 +00:00
|
|
|
'mk' => 'resources/jquery.ui/i18n/jquery.ui.datepicker-mk.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
|
|
|
),
|
2011-12-08 23:54:06 +00:00
|
|
|
'jquery.effects.fade' => array(
|
|
|
|
|
'scripts' => 'resources/jquery.effects/jquery.effects.fade.js',
|
|
|
|
|
'dependencies' => 'jquery.effects.core',
|
|
|
|
|
'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,
|
2012-10-11 22:37:59 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
* 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-12-09 04:48:39 +00:00
|
|
|
'mediawiki.api' => array(
|
2012-02-06 17:06:10 +00:00
|
|
|
'scripts' => 'resources/mediawiki.api/mediawiki.api.js',
|
2011-12-24 23:09:45 +00:00
|
|
|
'dependencies' => 'mediawiki.util',
|
2013-10-15 22:31:14 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2011-12-09 04:48:39 +00:00
|
|
|
),
|
2012-06-05 22:58:54 +00:00
|
|
|
'mediawiki.api.category' => array(
|
2012-02-06 17:06:10 +00:00
|
|
|
'scripts' => 'resources/mediawiki.api/mediawiki.api.category.js',
|
2012-06-05 22:58:54 +00:00
|
|
|
'dependencies' => array(
|
2011-12-09 04:48:39 +00:00
|
|
|
'mediawiki.api',
|
2012-06-05 22:58:54 +00:00
|
|
|
'mediawiki.Title',
|
2011-12-09 04:48:39 +00:00
|
|
|
),
|
|
|
|
|
),
|
2012-06-05 22:58:54 +00:00
|
|
|
'mediawiki.api.edit' => array(
|
2012-02-06 17:06:10 +00:00
|
|
|
'scripts' => 'resources/mediawiki.api/mediawiki.api.edit.js',
|
2012-06-05 22:58:54 +00:00
|
|
|
'dependencies' => array(
|
2011-12-09 04:48:39 +00:00
|
|
|
'mediawiki.api',
|
2012-06-05 22:58:54 +00:00
|
|
|
'mediawiki.Title',
|
2011-12-09 04:48:39 +00:00
|
|
|
),
|
|
|
|
|
),
|
2013-05-12 15:26:49 +00:00
|
|
|
'mediawiki.api.login' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.api/mediawiki.api.login.js',
|
|
|
|
|
'dependencies' => array(
|
|
|
|
|
'mediawiki.api',
|
|
|
|
|
),
|
|
|
|
|
),
|
2012-06-05 22:58:54 +00:00
|
|
|
'mediawiki.api.parse' => array(
|
2012-02-06 17:06:10 +00:00
|
|
|
'scripts' => 'resources/mediawiki.api/mediawiki.api.parse.js',
|
2011-12-09 04:48:39 +00:00
|
|
|
'dependencies' => 'mediawiki.api',
|
|
|
|
|
),
|
2012-06-05 22:58:54 +00:00
|
|
|
'mediawiki.api.watch' => array(
|
2012-02-06 17:06:10 +00:00
|
|
|
'scripts' => 'resources/mediawiki.api/mediawiki.api.watch.js',
|
2012-02-26 15:57:01 +00:00
|
|
|
'dependencies' => array(
|
|
|
|
|
'mediawiki.api',
|
|
|
|
|
'user.tokens',
|
|
|
|
|
),
|
2011-12-27 00:44:49 +00:00
|
|
|
),
|
2011-12-04 18:29:57 +00:00
|
|
|
'mediawiki.debug' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki/mediawiki.debug.js',
|
|
|
|
|
'styles' => 'resources/mediawiki/mediawiki.debug.css',
|
2012-01-04 01:28:01 +00:00
|
|
|
'dependencies' => 'jquery.footHovzer',
|
2012-02-13 15:25:08 +00:00
|
|
|
'position' => 'bottom',
|
|
|
|
|
),
|
|
|
|
|
'mediawiki.debug.init' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki/mediawiki.debug.init.js',
|
|
|
|
|
'dependencies' => 'mediawiki.debug',
|
|
|
|
|
// Uses a custom mw.config variable that is set in debughtml,
|
|
|
|
|
// must be loaded on the bottom
|
|
|
|
|
'position' => 'bottom',
|
2011-12-04 18:29:57 +00:00
|
|
|
),
|
2011-12-28 15:42:06 +00:00
|
|
|
'mediawiki.feedback' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki/mediawiki.feedback.js',
|
2012-02-23 00:53:29 +00:00
|
|
|
'styles' => 'resources/mediawiki/mediawiki.feedback.css',
|
2012-06-05 22:58:54 +00:00
|
|
|
'dependencies' => array(
|
|
|
|
|
'mediawiki.api.edit',
|
2011-12-28 15:42:06 +00:00
|
|
|
'mediawiki.Title',
|
|
|
|
|
'mediawiki.jqueryMsg',
|
|
|
|
|
'jquery.ui.dialog',
|
|
|
|
|
),
|
2012-06-05 22:58:54 +00:00
|
|
|
'messages' => array(
|
2011-12-28 15:42:06 +00:00
|
|
|
'feedback-bugornote',
|
|
|
|
|
'feedback-subject',
|
|
|
|
|
'feedback-message',
|
|
|
|
|
'feedback-cancel',
|
|
|
|
|
'feedback-submit',
|
|
|
|
|
'feedback-adding',
|
|
|
|
|
'feedback-error1',
|
|
|
|
|
'feedback-error2',
|
|
|
|
|
'feedback-error3',
|
|
|
|
|
'feedback-thanks',
|
|
|
|
|
'feedback-close',
|
|
|
|
|
'feedback-bugcheck',
|
|
|
|
|
'feedback-bugnew',
|
|
|
|
|
),
|
|
|
|
|
),
|
Initial stab at responsive images for screen densities.
* adds $wgResponsiveImages setting, defaulting to true, to enable the feature
* adds 'srcset' attribute with 1.5x and 2x URLs to image links and image thumbs
* adds jquery.hidpi plugin to check pixel density and implement partial 'srcset' polyfill
** $.devicePixelRatio() returns window.devicePixelRatio, with compat fallback for IE 10
** $().hidpi() performs a 'srcset' polyfill for browsers with no native 'srcset' support
* adds mediawiki.hidpi RL script to trigger hidpi loads after main images load
Note that this is a work in progress. There will be places where this doesn't yet work which output their imgs differently. If moving from a low to high-DPI screen on a MacBook Pro Retina display, you won't see images load until you reload.
Confirmed basic images and thumbs in wikitext appear to work in Safari 6, Chrome 21, Firefox 18 nightly on MacBook Pro Retina display, and IE 10 in Windows 8 at 150% zoom, 200% zoom, and 140% and 180%-ratio Metro tablet sizes.
Internally this is still a bit of a hack; Linker::makeImageLink and Linker::makeThumbLink explicitly ask for 1.5x and 2x scaled versions and insert their URLs, if different, into the original thumbnail object which (in default handler) outputs the srcset. This means that a number of places that handle images differently won't see the higher-resolution versions, such as <gallery> and the large thumbnail on the File: description page.
At some point we may wish to redo some of how the MediaHandler stuff works so that requesting a single thumbnail automatically produces the extra sizes in all circumstances. We might also consider outputting a 'srcset' or multiple src sizes in 'imageinfo' API requests, which would make ApiForeignRepo/InstantCommons more efficient. (Currently it has to make three requests for each image to get the three sizes.)
Change-Id: Id80ebd07a1a9f401a2c2bfeb21aae987e5aa863b
2012-09-18 07:18:50 +00:00
|
|
|
'mediawiki.hidpi' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki/mediawiki.hidpi.js',
|
|
|
|
|
'dependencies' => array(
|
|
|
|
|
'jquery.hidpi',
|
|
|
|
|
),
|
2012-10-11 22:37:59 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
Initial stab at responsive images for screen densities.
* adds $wgResponsiveImages setting, defaulting to true, to enable the feature
* adds 'srcset' attribute with 1.5x and 2x URLs to image links and image thumbs
* adds jquery.hidpi plugin to check pixel density and implement partial 'srcset' polyfill
** $.devicePixelRatio() returns window.devicePixelRatio, with compat fallback for IE 10
** $().hidpi() performs a 'srcset' polyfill for browsers with no native 'srcset' support
* adds mediawiki.hidpi RL script to trigger hidpi loads after main images load
Note that this is a work in progress. There will be places where this doesn't yet work which output their imgs differently. If moving from a low to high-DPI screen on a MacBook Pro Retina display, you won't see images load until you reload.
Confirmed basic images and thumbs in wikitext appear to work in Safari 6, Chrome 21, Firefox 18 nightly on MacBook Pro Retina display, and IE 10 in Windows 8 at 150% zoom, 200% zoom, and 140% and 180%-ratio Metro tablet sizes.
Internally this is still a bit of a hack; Linker::makeImageLink and Linker::makeThumbLink explicitly ask for 1.5x and 2x scaled versions and insert their URLs, if different, into the original thumbnail object which (in default handler) outputs the srcset. This means that a number of places that handle images differently won't see the higher-resolution versions, such as <gallery> and the large thumbnail on the File: description page.
At some point we may wish to redo some of how the MediaHandler stuff works so that requesting a single thumbnail automatically produces the extra sizes in all circumstances. We might also consider outputting a 'srcset' or multiple src sizes in 'imageinfo' API requests, which would make ApiForeignRepo/InstantCommons more efficient. (Currently it has to make three requests for each image to get the three sizes.)
Change-Id: Id80ebd07a1a9f401a2c2bfeb21aae987e5aa863b
2012-09-18 07:18:50 +00:00
|
|
|
),
|
2013-11-18 19:28:36 +00:00
|
|
|
'mediawiki.hlist' => array(
|
|
|
|
|
'styles' => 'resources/mediawiki/mediawiki.hlist.css',
|
|
|
|
|
'scripts' => 'resources/mediawiki/mediawiki.hlist.js',
|
|
|
|
|
'dependencies' => array(
|
|
|
|
|
'jquery.client',
|
|
|
|
|
),
|
|
|
|
|
),
|
2011-03-05 12:48:32 +00:00
|
|
|
'mediawiki.htmlform' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki/mediawiki.htmlform.js',
|
2013-04-09 07:48:21 +00:00
|
|
|
'messages' => array( 'htmlform-chosen-placeholder' ),
|
2011-03-05 12:48:32 +00:00
|
|
|
),
|
2013-11-18 20:31:18 +00:00
|
|
|
'mediawiki.icon' => array(
|
2013-12-27 11:43:17 +00:00
|
|
|
'styles' => 'resources/mediawiki/mediawiki.icon.less',
|
2013-11-18 20:31:18 +00:00
|
|
|
),
|
|
|
|
|
'mediawiki.inspect' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki/mediawiki.inspect.js',
|
|
|
|
|
'dependencies' => array(
|
|
|
|
|
'jquery.byteLength',
|
|
|
|
|
'jquery.json',
|
|
|
|
|
),
|
|
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
|
|
|
|
),
|
2012-08-13 06:18:07 +00:00
|
|
|
'mediawiki.notification' => array(
|
|
|
|
|
'styles' => 'resources/mediawiki/mediawiki.notification.css',
|
|
|
|
|
'scripts' => 'resources/mediawiki/mediawiki.notification.js',
|
|
|
|
|
'dependencies' => array(
|
|
|
|
|
'mediawiki.page.startup',
|
|
|
|
|
),
|
2013-10-15 22:31:14 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2012-08-13 06:18:07 +00:00
|
|
|
),
|
|
|
|
|
'mediawiki.notify' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki/mediawiki.notify.js',
|
2012-12-17 20:32:19 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2012-08-13 06:18:07 +00:00
|
|
|
),
|
(bug 40448) Replace legacy mwsuggest with mediawiki.searchSuggest
The module has been broken for a while now, but nobody noticed
because in plain core it is disabled by default, and in the
bundle we ship with Extension:Vector (and its SimpleSearch).
This commit removed the mediawiki.legacy.mwsuggest module (and
related components that become obsolete with its deletion) and
replaces it with the new mediawiki.searchSuggest module, which is
based on SimpleSearch from Extension:Vector (where it will be
removed soon).
The following and all references to it in core have been removed,
I also made sure that they weren't used in any of extensions/*.
Only matches in extensions/Settings and some file that dumped the startup module, and in extensions/Vector which are addressed in
I1d5bf81a8a0266c51c99d41eefacc0f4b3ae4b76.
Had to make a few updates to jquery.suggestions to make it work
in other skins. So far it was only used in Vector, but now that
it is used in mediawiki.searchSuggest, I noticed several issues
in other skins. Most importantly the fact that it assumed the
default offset was from the right corner, which isn't the case in
Monobook where the search bar is on the left (in the sidebar).
It now detects the appropiate origin corner automatically, and
also takes directionality of the page into account.
It also uses the correct font-size automatically. Previously it
used font-size: 0.8; but that only works in Vector. Every skin
seems to have its own way of making a sane font-size. In Monobook
the <body> has an extra small font-size which is then fixed in
div#globalWrapper, and in Vector it is extra large, which is then
fixed as well deeper in the document. Either way, the size on
<body> can't be used, and since this suggestions box is appended
to the <body> (it is a generic jQuery plugin without knowledge of
the document, and even if we could give it knowledge inside
the configuration, it'd have to be per-skin). So I removed the
Vector specific font-size and let it handle it automatically.
This was needed because it is now used in all skins.
Removed modules:
* mediawiki.legacy.mwsuggest:
> Replaced with mediawiki.searchSuggest.
Removed messages:
* search-mwsuggest-enabled
* search-mwsuggest-disabled
> No longer used.
Removed mw.config.values:
* wgMWSuggestTemplate
> Obsolete.
* wgSearchNamespaces
> Obsolete.
Removed server-side settings:
* $wgEnableMWSuggest
> Suggestions are now enabled by default and can be disabled
through the user preference `disablesuggest` still.
They can be disabled by default site-wide or hidden from
prefs through the standard mechanisms for that.
* $wgMWSuggestTemplate
> Obsolete.
Removed methods
* SearchEngine::getMWSuggestTemplate()
> Obsolete.
Filters:
$ ack mwsuggest -i -Q --ignore-dir=languages/messages
$ ack wgSearchNamespaces -Q
Message changes:
* vector-simplesearch-preference
> It was wrong, it didn't activate search suggestions, that
was handled by the Vector extension. This preference in
MediaWiki core controls whether the SimpleSearch bar HTML
and CSS will be used (e.g. the rectangle search box with
the magnifying class instead of the browser-default input
field with the plain submit buttons).
* searchsuggest-search
* searchsuggest-containing
These come from Extension:Vector message and should be imported
by translatewiki:
- vector-simplesearch-search
- vector-simplesearch-containing
Change-Id: Icd721011b40bb8d2c20aefa8b359a3e45413a07f
2012-09-23 01:06:53 +00:00
|
|
|
'mediawiki.searchSuggest' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki/mediawiki.searchSuggest.js',
|
(bug 17808) (bug 21167) use real links for search suggestions
Use real links for search suggestions. This allows the viewer to, for
example, open the search results in a new tab or right-click them
to copy link's address.
We hook up the result.render callback and wrap the entire container
element (.suggestions-results <div>) in an <a>. This is permitted in HTML5
and appears to work even on IE 6. (It has some quirks related to e.g.
backgrounds handling, but thankfully none of them apply here, as we just
need it to be properly clickable - see http://jsbin.com/ejurub/2 for
a minimal test.)
We do the same for the special.render callback, although it has to be
handled slightly differently due to inconsistencies in $.suggestions that
would require a rewrite to fix.
We have to do some pretty ugly mangling to determine the links' hrefs,
but well, that's life.
This required some changes to $.suggestions:
* pass the necessary data to the render callback
* do not interfere with clicks with a mouse button other than left
or with modifier keys active, to allow for the standard link behavior
described above
* adjusting the width of suggestions container and applying autoellipsis
should be done regardless of the render callback being used or not
* add some flexibility to $.suggestions.highlight, so it doesn't break
down when DOM is modified
Also did some good-to-have changes to $.suggestions:
* detect suggestions elements in various places by their classes, not by
them being <div>s
Change-Id: I87940ca86a2b3776969cbcee8cdf93e3c66b0cd9
2012-11-01 13:16:41 +00:00
|
|
|
'styles' => 'resources/mediawiki/mediawiki.searchSuggest.css',
|
(bug 40448) Replace legacy mwsuggest with mediawiki.searchSuggest
The module has been broken for a while now, but nobody noticed
because in plain core it is disabled by default, and in the
bundle we ship with Extension:Vector (and its SimpleSearch).
This commit removed the mediawiki.legacy.mwsuggest module (and
related components that become obsolete with its deletion) and
replaces it with the new mediawiki.searchSuggest module, which is
based on SimpleSearch from Extension:Vector (where it will be
removed soon).
The following and all references to it in core have been removed,
I also made sure that they weren't used in any of extensions/*.
Only matches in extensions/Settings and some file that dumped the startup module, and in extensions/Vector which are addressed in
I1d5bf81a8a0266c51c99d41eefacc0f4b3ae4b76.
Had to make a few updates to jquery.suggestions to make it work
in other skins. So far it was only used in Vector, but now that
it is used in mediawiki.searchSuggest, I noticed several issues
in other skins. Most importantly the fact that it assumed the
default offset was from the right corner, which isn't the case in
Monobook where the search bar is on the left (in the sidebar).
It now detects the appropiate origin corner automatically, and
also takes directionality of the page into account.
It also uses the correct font-size automatically. Previously it
used font-size: 0.8; but that only works in Vector. Every skin
seems to have its own way of making a sane font-size. In Monobook
the <body> has an extra small font-size which is then fixed in
div#globalWrapper, and in Vector it is extra large, which is then
fixed as well deeper in the document. Either way, the size on
<body> can't be used, and since this suggestions box is appended
to the <body> (it is a generic jQuery plugin without knowledge of
the document, and even if we could give it knowledge inside
the configuration, it'd have to be per-skin). So I removed the
Vector specific font-size and let it handle it automatically.
This was needed because it is now used in all skins.
Removed modules:
* mediawiki.legacy.mwsuggest:
> Replaced with mediawiki.searchSuggest.
Removed messages:
* search-mwsuggest-enabled
* search-mwsuggest-disabled
> No longer used.
Removed mw.config.values:
* wgMWSuggestTemplate
> Obsolete.
* wgSearchNamespaces
> Obsolete.
Removed server-side settings:
* $wgEnableMWSuggest
> Suggestions are now enabled by default and can be disabled
through the user preference `disablesuggest` still.
They can be disabled by default site-wide or hidden from
prefs through the standard mechanisms for that.
* $wgMWSuggestTemplate
> Obsolete.
Removed methods
* SearchEngine::getMWSuggestTemplate()
> Obsolete.
Filters:
$ ack mwsuggest -i -Q --ignore-dir=languages/messages
$ ack wgSearchNamespaces -Q
Message changes:
* vector-simplesearch-preference
> It was wrong, it didn't activate search suggestions, that
was handled by the Vector extension. This preference in
MediaWiki core controls whether the SimpleSearch bar HTML
and CSS will be used (e.g. the rectangle search box with
the magnifying class instead of the browser-default input
field with the plain submit buttons).
* searchsuggest-search
* searchsuggest-containing
These come from Extension:Vector message and should be imported
by translatewiki:
- vector-simplesearch-search
- vector-simplesearch-containing
Change-Id: Icd721011b40bb8d2c20aefa8b359a3e45413a07f
2012-09-23 01:06:53 +00:00
|
|
|
'messages' => array(
|
|
|
|
|
'searchsuggest-search',
|
|
|
|
|
'searchsuggest-containing',
|
|
|
|
|
),
|
|
|
|
|
'dependencies' => array(
|
|
|
|
|
'jquery.autoEllipsis',
|
|
|
|
|
'jquery.client',
|
|
|
|
|
'jquery.placeholder',
|
|
|
|
|
'jquery.suggestions',
|
2013-05-26 18:46:04 +00:00
|
|
|
'mediawiki.api',
|
(bug 40448) Replace legacy mwsuggest with mediawiki.searchSuggest
The module has been broken for a while now, but nobody noticed
because in plain core it is disabled by default, and in the
bundle we ship with Extension:Vector (and its SimpleSearch).
This commit removed the mediawiki.legacy.mwsuggest module (and
related components that become obsolete with its deletion) and
replaces it with the new mediawiki.searchSuggest module, which is
based on SimpleSearch from Extension:Vector (where it will be
removed soon).
The following and all references to it in core have been removed,
I also made sure that they weren't used in any of extensions/*.
Only matches in extensions/Settings and some file that dumped the startup module, and in extensions/Vector which are addressed in
I1d5bf81a8a0266c51c99d41eefacc0f4b3ae4b76.
Had to make a few updates to jquery.suggestions to make it work
in other skins. So far it was only used in Vector, but now that
it is used in mediawiki.searchSuggest, I noticed several issues
in other skins. Most importantly the fact that it assumed the
default offset was from the right corner, which isn't the case in
Monobook where the search bar is on the left (in the sidebar).
It now detects the appropiate origin corner automatically, and
also takes directionality of the page into account.
It also uses the correct font-size automatically. Previously it
used font-size: 0.8; but that only works in Vector. Every skin
seems to have its own way of making a sane font-size. In Monobook
the <body> has an extra small font-size which is then fixed in
div#globalWrapper, and in Vector it is extra large, which is then
fixed as well deeper in the document. Either way, the size on
<body> can't be used, and since this suggestions box is appended
to the <body> (it is a generic jQuery plugin without knowledge of
the document, and even if we could give it knowledge inside
the configuration, it'd have to be per-skin). So I removed the
Vector specific font-size and let it handle it automatically.
This was needed because it is now used in all skins.
Removed modules:
* mediawiki.legacy.mwsuggest:
> Replaced with mediawiki.searchSuggest.
Removed messages:
* search-mwsuggest-enabled
* search-mwsuggest-disabled
> No longer used.
Removed mw.config.values:
* wgMWSuggestTemplate
> Obsolete.
* wgSearchNamespaces
> Obsolete.
Removed server-side settings:
* $wgEnableMWSuggest
> Suggestions are now enabled by default and can be disabled
through the user preference `disablesuggest` still.
They can be disabled by default site-wide or hidden from
prefs through the standard mechanisms for that.
* $wgMWSuggestTemplate
> Obsolete.
Removed methods
* SearchEngine::getMWSuggestTemplate()
> Obsolete.
Filters:
$ ack mwsuggest -i -Q --ignore-dir=languages/messages
$ ack wgSearchNamespaces -Q
Message changes:
* vector-simplesearch-preference
> It was wrong, it didn't activate search suggestions, that
was handled by the Vector extension. This preference in
MediaWiki core controls whether the SimpleSearch bar HTML
and CSS will be used (e.g. the rectangle search box with
the magnifying class instead of the browser-default input
field with the plain submit buttons).
* searchsuggest-search
* searchsuggest-containing
These come from Extension:Vector message and should be imported
by translatewiki:
- vector-simplesearch-search
- vector-simplesearch-containing
Change-Id: Icd721011b40bb8d2c20aefa8b359a3e45413a07f
2012-09-23 01:06:53 +00:00
|
|
|
),
|
|
|
|
|
),
|
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',
|
2013-10-04 16:57:35 +00:00
|
|
|
'dependencies' => array(
|
|
|
|
|
'jquery.byteLength',
|
|
|
|
|
'mediawiki.util',
|
|
|
|
|
),
|
2013-10-15 22:31:14 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
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
|
|
|
),
|
2014-01-24 08:36:20 +00:00
|
|
|
'mediawiki.toc' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki/mediawiki.toc.js',
|
|
|
|
|
'dependencies' => array(
|
|
|
|
|
'jquery.cookie',
|
|
|
|
|
),
|
|
|
|
|
'messages' => array( 'showtoc', 'hidetoc' ),
|
|
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
|
|
|
|
),
|
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',
|
2013-10-15 22:31:14 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
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',
|
2012-07-05 16:27:41 +00:00
|
|
|
'mediawiki.api',
|
2012-09-21 00:37:48 +00:00
|
|
|
'user.options',
|
|
|
|
|
'user.tokens',
|
2011-05-16 17:58:54 +00:00
|
|
|
),
|
2013-10-15 22:31:14 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2011-05-16 17:58:54 +00:00
|
|
|
),
|
2011-11-11 00:17:38 +00:00
|
|
|
'mediawiki.util' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki/mediawiki.util.js',
|
|
|
|
|
'dependencies' => array(
|
|
|
|
|
'jquery.client',
|
|
|
|
|
'jquery.mwExtension',
|
2012-08-13 06:18:07 +00:00
|
|
|
'mediawiki.notify',
|
2014-01-24 08:36:20 +00:00
|
|
|
'mediawiki.toc',
|
2011-11-11 00:17:38 +00:00
|
|
|
),
|
2012-01-29 19:40:11 +00:00
|
|
|
'position' => 'top', // For $wgPreloadJavaScriptMwUtil
|
2012-12-17 20:32:19 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2011-11-11 00:17:38 +00:00
|
|
|
),
|
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(
|
2013-07-26 10:08:50 +00:00
|
|
|
'mediawiki.action.edit.styles',
|
2011-08-01 21:46:54 +00:00
|
|
|
'jquery.textSelection',
|
|
|
|
|
'jquery.byteLimit',
|
2011-06-22 21:27:12 +00:00
|
|
|
),
|
mw.toolbar: Clean up the API of the classic toolbar.
* Several methods were added here recently during 1.20 development
that should not have been public methods.
* Also in the creation of this new module (replacing the old
mwCustomEditButtons) a design flaw was made. Instead of using
a key-value pair object, the signature was changed to a tentacle
function with 7 (for callers, unnamed) arguments.
* Changed it back with the compatibility fix the other way around.
So everything is backwards compatible.
* Moved to local scope:
- buttons queue
- $toolbar
- insertButton
These were recently introduced during 1.20 development but not
meant to be public. When used too early or too late from outside
the module it will break or be ignored. For example $toolbar is
false before dom ready, buttons queue is ignored after domready,
insertButton will break if called before dom ready because the
target element doesn't exist yet. These are not bugs, but result
of calling internal methods before they are initialized.
The public API takes care of these state differences by using
the queue and the dom ready handler.
Scripts should (and do) only use the addButton API.
* Kept:
- addButton
- insertTags
- init (empty b/c function, was already there)
* Improved:
- addButton: Now takes an object as well, just like
mwCustomEditButtons used to do.
- Cache Array.prototype.slice instead of re-grabbing from
a new dummy array.
- Store buttons[i] in a local variable in both cases, not just
for legacy. Saves 2 property lookups. Minor gain, but
in this case it was already going to be stored in a local
variable, so might as well do it in the other case.
* Fixes:
- Clear queue array after it has been used. Though in practice
it should never happen that it is iterated over twice, just in
case.
- Added comment to init() function explaining where it is used.
- Updated closure arguments per code conventions.
- Made it a position-top module so that it actually can be used
before the document is ready.
* Example usages tested:
<code>
// Legacy way from wikibits.js:
// Has to be done before document ready
window.mwCustomEditButtons[window.mwCustomEditButtons.length] = {
imageFile: 'http://placehold.it/23x22',
speedTip: 'tool tip',
tagOpen: 'x-',
tagClose: '-y'
};
// mw.toolbar: List of arguments
mw.toolbar.addButton( 'http://placehold.it/23x22', 'tooltip', 'x-', '-y' );
// mw.toolbar: Object
mw.toolbar.addButton({
imageFile: 'http://placehold.it/23x22',
speedTip: 'tool tip',
tagOpen: 'x-',
tagClose: '-y'
});
</code>
Change-Id: Id19819707c937c2c3144ad8177b75baa46f5073c
2012-07-21 23:49:46 +00:00
|
|
|
'position' => 'top',
|
2011-06-22 21:27:12 +00:00
|
|
|
),
|
2013-07-26 10:08:50 +00:00
|
|
|
'mediawiki.action.edit.styles' => array(
|
|
|
|
|
'styles' => 'resources/mediawiki.action/mediawiki.action.edit.styles.css',
|
|
|
|
|
'position' => 'top',
|
|
|
|
|
),
|
2013-03-23 15:36:14 +00:00
|
|
|
'mediawiki.action.edit.collapsibleFooter' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.action/mediawiki.action.edit.collapsibleFooter.js',
|
|
|
|
|
'styles' => 'resources/mediawiki.action/mediawiki.action.edit.collapsibleFooter.css',
|
|
|
|
|
'dependencies' => array(
|
|
|
|
|
'jquery.makeCollapsible',
|
2013-12-29 16:54:01 +00:00
|
|
|
'jquery.cookie',
|
2013-03-23 15:36:14 +00:00
|
|
|
'mediawiki.icon',
|
|
|
|
|
),
|
|
|
|
|
),
|
2012-09-17 17:35:04 +00:00
|
|
|
'mediawiki.action.edit.preview' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.action/mediawiki.action.edit.preview.js',
|
|
|
|
|
'dependencies' => array(
|
|
|
|
|
'jquery.form',
|
|
|
|
|
'jquery.spinner',
|
2013-07-29 00:33:43 +00:00
|
|
|
'mediawiki.action.history.diff',
|
2012-09-17 17:35:04 +00:00
|
|
|
),
|
|
|
|
|
),
|
2011-08-01 21:46:54 +00:00
|
|
|
'mediawiki.action.history' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.action/mediawiki.action.history.js',
|
|
|
|
|
'group' => 'mediawiki.action.history',
|
|
|
|
|
),
|
|
|
|
|
'mediawiki.action.history.diff' => array(
|
|
|
|
|
'styles' => 'resources/mediawiki.action/mediawiki.action.history.diff.css',
|
|
|
|
|
'group' => 'mediawiki.action.history',
|
2013-10-15 22:31:14 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2011-08-01 21:46:54 +00:00
|
|
|
),
|
2011-08-01 22:13:32 +00:00
|
|
|
'mediawiki.action.view.dblClickEdit' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.action/mediawiki.action.view.dblClickEdit.js',
|
2012-09-21 00:37:48 +00:00
|
|
|
'dependencies' => array(
|
|
|
|
|
'mediawiki.util',
|
|
|
|
|
'mediawiki.page.startup',
|
|
|
|
|
),
|
2011-08-01 22:13:32 +00:00
|
|
|
),
|
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',
|
|
|
|
|
),
|
|
|
|
|
),
|
2013-02-23 10:35:22 +00:00
|
|
|
'mediawiki.action.view.postEdit' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.action/mediawiki.action.view.postEdit.js',
|
2013-05-30 18:10:46 +00:00
|
|
|
'styles' => 'resources/mediawiki.action/mediawiki.action.view.postEdit.css',
|
|
|
|
|
'dependencies' => array(
|
|
|
|
|
'jquery.cookie',
|
|
|
|
|
'mediawiki.jqueryMsg'
|
|
|
|
|
),
|
|
|
|
|
'messages' => array(
|
|
|
|
|
'postedit-confirmation',
|
|
|
|
|
),
|
2013-02-23 10:35:22 +00:00
|
|
|
),
|
2013-12-17 18:41:33 +00:00
|
|
|
'mediawiki.action.view.redirectToFragment' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.action/mediawiki.action.view.redirectToFragment.js',
|
|
|
|
|
'dependencies' => array(
|
|
|
|
|
'jquery.client',
|
|
|
|
|
),
|
|
|
|
|
'position' => 'top',
|
|
|
|
|
),
|
2011-08-01 21:46:54 +00:00
|
|
|
'mediawiki.action.view.rightClickEdit' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.action/mediawiki.action.view.rightClickEdit.js',
|
|
|
|
|
),
|
2013-03-31 21:55:52 +00:00
|
|
|
'mediawiki.action.edit.editWarning' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.action/mediawiki.action.edit.editWarning.js',
|
|
|
|
|
'messages' => array(
|
|
|
|
|
'editwarning-warning',
|
|
|
|
|
),
|
|
|
|
|
),
|
2012-06-21 18:23:50 +00:00
|
|
|
// Alias for backwards compatibility
|
|
|
|
|
'mediawiki.action.watch.ajax' => array(
|
|
|
|
|
'dependencies' => 'mediawiki.page.watch.ajax'
|
|
|
|
|
),
|
2011-08-01 21:46:54 +00:00
|
|
|
|
|
|
|
|
/* MediaWiki Language */
|
|
|
|
|
|
|
|
|
|
'mediawiki.language' => array(
|
2013-01-18 15:34:54 +00:00
|
|
|
'scripts' => array(
|
|
|
|
|
'resources/mediawiki.language/mediawiki.language.js',
|
|
|
|
|
'resources/mediawiki.language/mediawiki.language.numbers.js'
|
|
|
|
|
),
|
2011-08-01 21:46:54 +00:00
|
|
|
'languageScripts' => array(
|
|
|
|
|
'bs' => 'resources/mediawiki.language/languages/bs.js',
|
|
|
|
|
'dsb' => 'resources/mediawiki.language/languages/dsb.js',
|
2012-06-04 09:19:35 +00:00
|
|
|
'fi' => 'resources/mediawiki.language/languages/fi.js',
|
2011-08-01 21:46:54 +00:00
|
|
|
'ga' => 'resources/mediawiki.language/languages/ga.js',
|
|
|
|
|
'he' => 'resources/mediawiki.language/languages/he.js',
|
|
|
|
|
'hsb' => 'resources/mediawiki.language/languages/hsb.js',
|
2012-06-04 09:19:35 +00:00
|
|
|
'hu' => 'resources/mediawiki.language/languages/hu.js',
|
2011-08-01 21:46:54 +00:00
|
|
|
'hy' => 'resources/mediawiki.language/languages/hy.js',
|
2012-06-04 09:19:35 +00:00
|
|
|
'la' => 'resources/mediawiki.language/languages/la.js',
|
|
|
|
|
'os' => 'resources/mediawiki.language/languages/os.js',
|
2011-08-01 21:46:54 +00:00
|
|
|
'ru' => 'resources/mediawiki.language/languages/ru.js',
|
|
|
|
|
'sl' => 'resources/mediawiki.language/languages/sl.js',
|
|
|
|
|
'uk' => 'resources/mediawiki.language/languages/uk.js',
|
2011-06-22 21:27:12 +00:00
|
|
|
),
|
2012-08-22 13:15:44 +00:00
|
|
|
'dependencies' => array(
|
|
|
|
|
'mediawiki.language.data',
|
2013-01-18 15:34:54 +00:00
|
|
|
'mediawiki.cldr',
|
2012-08-22 13:15:44 +00:00
|
|
|
),
|
2012-12-17 20:32:19 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2012-08-22 13:15:44 +00:00
|
|
|
),
|
|
|
|
|
|
|
|
|
|
'mediawiki.cldr' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.language/mediawiki.cldr.js',
|
|
|
|
|
'dependencies' => array(
|
|
|
|
|
'mediawiki.libs.pluralruleparser',
|
|
|
|
|
),
|
2012-12-17 20:32:19 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2012-08-22 13:15:44 +00:00
|
|
|
),
|
|
|
|
|
|
|
|
|
|
'mediawiki.libs.pluralruleparser' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.libs/CLDRPluralRuleParser.js',
|
2012-12-17 20:32:19 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2012-06-05 22:58:54 +00:00
|
|
|
),
|
|
|
|
|
|
|
|
|
|
'mediawiki.language.init' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.language/mediawiki.language.init.js',
|
2012-12-17 20:32:19 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2011-06-22 21:27:12 +00:00
|
|
|
),
|
2011-08-01 21:46:54 +00:00
|
|
|
|
2011-12-13 02:44:34 +00:00
|
|
|
'mediawiki.jqueryMsg' => array(
|
2012-06-05 22:58:54 +00:00
|
|
|
'scripts' => 'resources/mediawiki/mediawiki.jqueryMsg.js',
|
|
|
|
|
'dependencies' => array(
|
|
|
|
|
'mediawiki.util',
|
|
|
|
|
'mediawiki.language',
|
|
|
|
|
),
|
2012-12-17 20:32:19 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2011-12-13 02:44:34 +00:00
|
|
|
),
|
|
|
|
|
|
2013-07-02 14:46:25 +00:00
|
|
|
'mediawiki.language.months' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.language/mediawiki.language.months.js',
|
|
|
|
|
'dependencies' => 'mediawiki.language',
|
|
|
|
|
'messages' => array_merge(
|
|
|
|
|
Language::$mMonthMsgs,
|
|
|
|
|
Language::$mMonthGenMsgs,
|
|
|
|
|
Language::$mMonthAbbrevMsgs
|
|
|
|
|
)
|
|
|
|
|
),
|
|
|
|
|
|
2011-08-01 21:46:54 +00:00
|
|
|
/* MediaWiki Libs */
|
|
|
|
|
|
|
|
|
|
'mediawiki.libs.jpegmeta' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.libs/mediawiki.libs.jpegmeta.js',
|
|
|
|
|
),
|
|
|
|
|
|
|
|
|
|
/* MediaWiki Page */
|
|
|
|
|
|
New more slick gallery display
This extension adds a "mode" parameter to the gallery
tag, allowing different formats for the gallery tag
(galleries in the ui can be controlled by a global)
The added modes are:
*traditional - The original gallery
*nolines - Like the original, no borders, less padding
*packed - All images aligned by having same height.
JS also justifies the images.
(I think this one is the one that will go over best
with users.)
*packed-overlay - like packed, but caption goes over
top the image in a transloucent box.
*packed-hover - like packed-overlay, but caption only
visible on hover. Degrades gracefully on screen
readers, and falls back to packed-overlay if
you are using a touch screen. I kind of like
this mode when the caption is not that important
(ex a category where its just the file name).
This also adds a hook to allow people to make their
own gallery version. I believe there would be interest
in this, as different people have done different
experiments. For example:
* Wikia: http://community.wikia.com/wiki/Help:Galleries,_Slideshows,_and_Sliders/wikitext
* Wikinews: https://en.wikinews.org/wiki/Template:Picture_select
What I would like to see for this patch, is first it gets
enabled, with the default still "traditional". After
about a month or two we consult with users. If feedback
is positive, we change the default mode to one of the
others (probably "packed").
Adds a "mode" parameter to gallery for different
mode, including one 'height-constrained-overlay'
which looks much more like other modern websites.
Note: This makes one change to the old gallery format.
It makes Nonexistent files be rendered like thumbnails
(i.e. they are rendered with a little grey border).
One thing I'm slightly worried about with this patch,
is that I added an option to MediaTransformOutput::toHtml
to override the width attribute. I'm not sure if that
is the best approach, and would appreciate thoughts
on that.
This should be merged at the same time as Ie82c1548
Change-Id: I33462a8b52502ed76aeb163b66e3704c8618ba23
2013-06-08 04:47:07 +00:00
|
|
|
'mediawiki.page.gallery' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.page/mediawiki.page.gallery.js',
|
|
|
|
|
),
|
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
|
|
|
),
|
2013-02-22 23:13:30 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
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',
|
2012-02-02 00:47:53 +00:00
|
|
|
'mediawiki.util',
|
2011-05-21 18:33:48 +00:00
|
|
|
),
|
2011-08-01 21:46:54 +00:00
|
|
|
'position' => 'top',
|
2013-02-22 23:13:30 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2010-12-09 21:59:02 +00:00
|
|
|
),
|
2012-10-03 01:33:55 +00:00
|
|
|
'mediawiki.page.patrol.ajax' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.page/mediawiki.page.patrol.ajax.js',
|
|
|
|
|
'dependencies' => array(
|
|
|
|
|
'mediawiki.page.startup',
|
|
|
|
|
'mediawiki.api',
|
|
|
|
|
'mediawiki.util',
|
|
|
|
|
'mediawiki.Title',
|
|
|
|
|
'mediawiki.notify',
|
|
|
|
|
'jquery.spinner',
|
|
|
|
|
'user.tokens'
|
|
|
|
|
),
|
|
|
|
|
'messages' => array(
|
|
|
|
|
'markedaspatrollednotify',
|
|
|
|
|
'markedaspatrollederrornotify',
|
|
|
|
|
'markedaspatrollederror-noautopatrol'
|
|
|
|
|
),
|
|
|
|
|
),
|
2012-06-19 23:00:57 +00:00
|
|
|
'mediawiki.page.watch.ajax' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.page/mediawiki.page.watch.ajax.js',
|
|
|
|
|
'dependencies' => array(
|
|
|
|
|
'mediawiki.page.startup',
|
|
|
|
|
'mediawiki.api.watch',
|
2012-08-13 06:18:07 +00:00
|
|
|
'mediawiki.util',
|
|
|
|
|
'mediawiki.notify',
|
2012-08-27 17:43:14 +00:00
|
|
|
'jquery.mwExtension',
|
2012-06-19 23:00:57 +00:00
|
|
|
),
|
|
|
|
|
'messages' => array(
|
|
|
|
|
'watch',
|
|
|
|
|
'unwatch',
|
|
|
|
|
'watching',
|
|
|
|
|
'unwatching',
|
|
|
|
|
'tooltip-ca-watch',
|
|
|
|
|
'tooltip-ca-unwatch',
|
|
|
|
|
'watcherrortext',
|
|
|
|
|
),
|
|
|
|
|
),
|
2013-05-02 17:41:40 +00:00
|
|
|
'mediawiki.page.image.pagination' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.page/mediawiki.page.image.pagination.js',
|
|
|
|
|
'dependencies' => array( 'jquery.spinner' )
|
|
|
|
|
),
|
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',
|
|
|
|
|
),
|
2011-11-11 00:17:38 +00:00
|
|
|
'mediawiki.special.block' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.special/mediawiki.special.block.js',
|
2013-12-23 11:37:03 +00:00
|
|
|
'styles' => 'resources/mediawiki.special/mediawiki.special.block.css',
|
2012-01-21 13:31:51 +00:00
|
|
|
'dependencies' => array(
|
|
|
|
|
'mediawiki.util',
|
|
|
|
|
),
|
* 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-12-17 18:31:25 +00:00
|
|
|
'mediawiki.special.changeemail' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.special/mediawiki.special.changeemail.js',
|
|
|
|
|
'styles' => 'resources/mediawiki.special/mediawiki.special.changeemail.css',
|
2012-01-21 13:31:51 +00:00
|
|
|
'dependencies' => array(
|
|
|
|
|
'mediawiki.util',
|
|
|
|
|
),
|
|
|
|
|
'messages' => array(
|
|
|
|
|
'email-address-validity-valid',
|
|
|
|
|
'email-address-validity-invalid',
|
|
|
|
|
),
|
2011-12-17 18:31:25 +00:00
|
|
|
),
|
2010-12-27 19:07:28 +00:00
|
|
|
'mediawiki.special.changeslist' => array(
|
|
|
|
|
'styles' => 'resources/mediawiki.special/mediawiki.special.changeslist.css',
|
2013-06-13 23:47:43 +00:00
|
|
|
),
|
2013-12-22 01:01:14 +00:00
|
|
|
'mediawiki.special.changeslist.legend' => array(
|
|
|
|
|
'styles' => 'resources/mediawiki.special/mediawiki.special.changeslist.legend.css',
|
|
|
|
|
),
|
|
|
|
|
'mediawiki.special.changeslist.legend.js' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.special/mediawiki.special.changeslist.legend.js',
|
2013-12-13 20:56:02 +00:00
|
|
|
'dependencies' => array(
|
|
|
|
|
'jquery.makeCollapsible',
|
|
|
|
|
'jquery.cookie',
|
|
|
|
|
),
|
|
|
|
|
),
|
2013-06-13 23:47:43 +00:00
|
|
|
'mediawiki.special.changeslist.enhanced' => array(
|
|
|
|
|
'styles' => 'resources/mediawiki.special/mediawiki.special.changeslist.enhanced.css',
|
2010-12-27 19:07:28 +00:00
|
|
|
),
|
2011-04-25 11:39:30 +00:00
|
|
|
'mediawiki.special.movePage' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.special/mediawiki.special.movePage.js',
|
|
|
|
|
'dependencies' => 'jquery.byteLimit',
|
|
|
|
|
),
|
2013-07-23 20:38:05 +00:00
|
|
|
'mediawiki.special.pagesWithProp' => array(
|
|
|
|
|
'styles' => 'resources/mediawiki.special/mediawiki.special.pagesWithProp.css',
|
|
|
|
|
),
|
2011-11-11 00:17:38 +00:00
|
|
|
'mediawiki.special.preferences' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.special/mediawiki.special.preferences.js',
|
2013-04-15 19:38:16 +00:00
|
|
|
'styles' => 'resources/mediawiki.special/mediawiki.special.preferences.css',
|
2013-06-06 05:40:24 +00:00
|
|
|
'position' => 'top',
|
2013-10-16 17:56:34 +00:00
|
|
|
'skinStyles' => array(
|
|
|
|
|
'vector' => 'skins/vector/special.preferences.less',
|
|
|
|
|
),
|
2013-08-11 07:11:40 +00:00
|
|
|
'messages' => array(
|
|
|
|
|
'prefs-tabs-navigation-hint',
|
|
|
|
|
),
|
2013-12-14 18:07:11 +00:00
|
|
|
'dependencies' => array(
|
|
|
|
|
'mediawiki.language',
|
|
|
|
|
),
|
2011-11-11 00:17:38 +00:00
|
|
|
),
|
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
|
|
|
),
|
2011-11-11 00:17:38 +00:00
|
|
|
'mediawiki.special.search' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.special/mediawiki.special.search.js',
|
|
|
|
|
'styles' => 'resources/mediawiki.special/mediawiki.special.search.css',
|
2012-05-17 04:17:31 +00:00
|
|
|
'messages' => array(
|
|
|
|
|
'powersearch-togglelabel',
|
|
|
|
|
'powersearch-toggleall',
|
|
|
|
|
'powersearch-togglenone',
|
|
|
|
|
),
|
2011-11-11 00:17:38 +00:00
|
|
|
),
|
|
|
|
|
'mediawiki.special.undelete' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.special/mediawiki.special.undelete.js',
|
|
|
|
|
),
|
2010-12-26 22:01:26 +00:00
|
|
|
'mediawiki.special.upload' => array(
|
2013-05-15 01:12:35 +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
|
|
|
),
|
2013-11-07 17:35:24 +00:00
|
|
|
'dependencies' => array(
|
|
|
|
|
'mediawiki.libs.jpegmeta',
|
|
|
|
|
'mediawiki.util',
|
|
|
|
|
),
|
2010-12-26 22:01:26 +00:00
|
|
|
),
|
2013-12-02 19:29:03 +00:00
|
|
|
'mediawiki.special.userlogin.common.styles' => array(
|
2013-03-05 03:13:39 +00:00
|
|
|
'styles' => array(
|
2013-12-02 19:29:03 +00:00
|
|
|
'resources/mediawiki.special/mediawiki.special.userlogin.common.css',
|
2013-03-05 03:13:39 +00:00
|
|
|
),
|
|
|
|
|
'position' => 'top',
|
|
|
|
|
),
|
2013-12-02 19:29:03 +00:00
|
|
|
'mediawiki.special.userlogin.signup.styles' => array(
|
2013-04-06 01:57:03 +00:00
|
|
|
'styles' => array(
|
2013-12-02 19:29:03 +00:00
|
|
|
'resources/mediawiki.special/mediawiki.special.userlogin.signup.css',
|
2013-04-06 01:57:03 +00:00
|
|
|
),
|
2013-12-02 19:29:03 +00:00
|
|
|
'position' => 'top',
|
|
|
|
|
),
|
|
|
|
|
'mediawiki.special.userlogin.login.styles' => array(
|
|
|
|
|
'styles' => array(
|
|
|
|
|
'resources/mediawiki.special/mediawiki.special.userlogin.login.css',
|
|
|
|
|
),
|
|
|
|
|
'position' => 'top',
|
2013-04-06 01:57:03 +00:00
|
|
|
),
|
2013-12-02 19:29:03 +00:00
|
|
|
'mediawiki.special.userlogin.common.js' => array(
|
|
|
|
|
'scripts' => array(
|
|
|
|
|
'resources/mediawiki.special/mediawiki.special.userlogin.common.js',
|
|
|
|
|
),
|
2013-04-06 01:57:03 +00:00
|
|
|
'messages' => array(
|
|
|
|
|
'createacct-captcha',
|
2013-12-02 19:29:03 +00:00
|
|
|
'createacct-imgcaptcha-ph',
|
|
|
|
|
),
|
|
|
|
|
),
|
|
|
|
|
'mediawiki.special.userlogin.signup.js' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.special/mediawiki.special.userlogin.signup.js',
|
|
|
|
|
'messages' => array(
|
2013-04-26 00:12:49 +00:00
|
|
|
'createacct-emailrequired',
|
2013-04-06 01:57:03 +00:00
|
|
|
),
|
|
|
|
|
'dependencies' => 'mediawiki.jqueryMsg',
|
|
|
|
|
),
|
2012-01-03 18:33:26 +00:00
|
|
|
'mediawiki.special.javaScriptTest' => array(
|
|
|
|
|
'scripts' => 'resources/mediawiki.special/mediawiki.special.javaScriptTest.js',
|
|
|
|
|
'messages' => array_merge( Skin::getSkinNameMessages(), array(
|
|
|
|
|
'colon-separator',
|
|
|
|
|
'javascripttest-pagetext-skins',
|
|
|
|
|
) ),
|
|
|
|
|
'dependencies' => array( 'jquery.qunit' ),
|
|
|
|
|
'position' => 'top',
|
2013-02-22 23:13:30 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2012-01-03 18:33:26 +00:00
|
|
|
),
|
2013-05-29 02:52:05 +00:00
|
|
|
'mediawiki.special.version' => array(
|
|
|
|
|
'styles' => 'resources/mediawiki.special/mediawiki.special.version.css',
|
|
|
|
|
),
|
2012-01-03 18:33:26 +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'],
|
2012-01-21 13:31:51 +00:00
|
|
|
'dependencies' => array(
|
|
|
|
|
'mediawiki.util',
|
|
|
|
|
'mediawiki.legacy.wikibits',
|
|
|
|
|
),
|
2012-02-09 14:14:45 +00:00
|
|
|
'position' => 'top', // Temporary hack for legacy support
|
* 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(
|
2013-10-14 01:34:58 +00:00
|
|
|
// Used in the web installer. Test it after modifying this definition!
|
2011-02-08 12:06:32 +00:00
|
|
|
'scripts' => 'common/config.js',
|
2013-10-14 01:34:58 +00:00
|
|
|
'styles' => array( 'common/config.css' ),
|
2011-02-08 12:06:32 +00:00
|
|
|
'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(
|
|
|
|
|
'jquery.byteLimit',
|
|
|
|
|
),
|
2012-01-22 02:51:06 +00:00
|
|
|
'position' => 'top',
|
* 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(
|
2013-10-14 01:34:58 +00:00
|
|
|
// Used in the web installer. Test it after modifying this definition!
|
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'],
|
2012-01-21 13:31:51 +00:00
|
|
|
'dependencies' => array(
|
2013-11-07 17:35:24 +00:00
|
|
|
'jquery.spinner',
|
2013-05-26 16:25:30 +00:00
|
|
|
'mediawiki.api',
|
|
|
|
|
'mediawiki.Title',
|
2012-01-21 13:31:51 +00:00
|
|
|
'mediawiki.util',
|
|
|
|
|
),
|
* 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'],
|
2012-01-21 13:31:51 +00:00
|
|
|
'dependencies' => array(
|
|
|
|
|
'mediawiki.util',
|
|
|
|
|
),
|
2012-01-06 12:03:06 +00:00
|
|
|
'position' => 'top',
|
* 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
|
|
|
),
|
2013-03-05 03:13:39 +00:00
|
|
|
'mediawiki.ui' => array(
|
|
|
|
|
'skinStyles' => array(
|
2013-11-04 20:12:14 +00:00
|
|
|
'default' => 'resources/mediawiki.ui/default.less',
|
|
|
|
|
'vector' => 'resources/mediawiki.ui/vector.less',
|
2013-03-05 03:13:39 +00:00
|
|
|
),
|
|
|
|
|
'position' => 'top',
|
2013-12-03 19:12:32 +00:00
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
|
|
|
|
),
|
|
|
|
|
// Lightweight module for button styles
|
|
|
|
|
'mediawiki.ui.button' => array(
|
|
|
|
|
'skinStyles' => array(
|
|
|
|
|
'default' => 'resources/mediawiki.ui/components/default/buttons.less',
|
|
|
|
|
'vector' => 'resources/mediawiki.ui/components/vector/buttons.less',
|
|
|
|
|
),
|
|
|
|
|
'position' => 'top',
|
|
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
2013-03-05 03:13:39 +00:00
|
|
|
),
|
2013-12-03 19:48:24 +00:00
|
|
|
|
|
|
|
|
/* OOJS */
|
|
|
|
|
// WARNING: oojs is NOT COMPATIBLE with older browsers and
|
|
|
|
|
// WILL BREAK if loaded in browsers that don't support ES5
|
|
|
|
|
'oojs' => array(
|
|
|
|
|
'scripts' => array(
|
|
|
|
|
'resources/oojs/oojs.js',
|
|
|
|
|
),
|
|
|
|
|
'targets' => array( 'desktop', 'mobile' ),
|
|
|
|
|
),
|
2010-10-28 21:01:56 +00:00
|
|
|
);
|
