chipmunkmc/mediawiki-skins-Insurgency
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
mediawiki-skins-Insurgency/skin.json

150 lines
3.3 KiB
JSON
Raw Normal View History

Add skin.json Change-Id: Id93e8290ee75b319974ef12041bba48c428e77b5
2015-02-06 16:21:29 -05:00
{
"name": "MonoBook",
"author": [
"Gabriel Wicke",
Responsive support, noJS version * Add screen-mobile.css with basic mobile styles * Force loading of screen-desktop on IE8- due to lack of @media width support * Add some new divs and a set of spoof cactions for jumping around the page (what's js?) * Replace cactions label with a more descriptive string (was previously set to display:none regardless) * Also add a set of icons for fixed widths for tabs and things (icons-source.svg is the source file for the set, and includes a few others that ultimately weren't used here) Cutoff 850px. Desktop styles should remain unchanged, with mobile remaining stylistically consistent. Change-Id: I737a7447db1e44e0d6abaa4c07813295a5ac73a6
2018-05-01 15:44:43 -04:00
"Isarra Yos",
Add skin.json Change-Id: Id93e8290ee75b319974ef12041bba48c428e77b5
2015-02-06 16:21:29 -05:00
"..."
],
"url": "https://www.mediawiki.org/wiki/Skin:MonoBook",
"descriptionmsg": "monobook-desc",
Revert "Update namemsg to convention" My bad... skinname-<skinname> is used in core to get the skin name. This reverts commit 7e619a456487506e6cf0e9ded9ff806152b22874. Change-Id: If38a19aceb46c0205a39aa7f27b98ceaa056c0f2
2015-09-28 05:42:33 -04:00
"namemsg": "skinname-monobook",
Use valid SPDX-3 license identifier Change-Id: Ib29500f6df89f30646a9587d01a8681e5f1297da
2018-02-15 16:12:47 -05:00
"license-name": "GPL-2.0-or-later",
Add skin.json Change-Id: Id93e8290ee75b319974ef12041bba48c428e77b5
2015-02-06 16:21:29 -05:00
"type": "skin",
Add MediaWiki version requirement to skin.json Change-Id: I0ad6147b55ed1316555371feb88de26dfa8583ca
2015-09-23 11:33:50 -04:00
"requires": {
Drop responsive Monobook IE8 support Bug: T259316 Change-Id: I85c198601291327bb5edff6d440ce143b8887756
2020-08-04 17:25:06 -04:00
"MediaWiki": ">= 1.36.0"
Add MediaWiki version requirement to skin.json Change-Id: I0ad6147b55ed1316555371feb88de26dfa8583ca
2015-09-23 11:33:50 -04:00
},
Fix skin.json ValidSkinNames is actually a registration setting, not a configuration one. Change-Id: I61c085fd89e81969eef6065b28cb24cbe0b366c9
2015-03-25 18:54:17 -04:00
"ValidSkinNames": {
"monobook": "MonoBook"
},
Use the "Apex" OOjs UI theme Change-Id: I0b18b9990795467059dc86ccb8632f9bd529800e
2015-05-23 09:29:16 -04:00
"SkinOOUIThemes": {
Use canonical theme name case for SkinOOUIThemes Depends on I489922dab303320bfecfbadd26069abbad7d2c53 in MediaWiki core. Change-Id: I1a88092f0ceb210c642bbee875e368ded3c186f8
2015-07-23 13:19:13 -04:00
"monobook": "Apex"
Use the "Apex" OOjs UI theme Change-Id: I0b18b9990795467059dc86ccb8632f9bd529800e
2015-05-23 09:29:16 -04:00
},
Add user preference to control responsive MonoBook This provides a device agnostic, persistent opt-out for the new responsive functionality. The preference will show up under the skin selector if the user has their skin already set to MonoBook. I considered adding a new skin option to the radio selector of skins, but that is probably unnecessary for the majority of users, in addition to complicating how to differentiate the two modes (Classic MonoBook vs. Modern MonoBook?). Wikis that want to make this opt-in can control the default in the standard way ($wgDefaultUserOptions), or hide it entirely ($wgHiddenPrefs). Change-Id: Id22f8e5199ff2b15fd03c94097db5cdc7188f8b1
2018-06-03 18:50:36 -04:00
"DefaultUserOptions": {
"monobook-responsive": true
},
Responsive support: Echo hacks Have echo just show the numbers instead of the badges, and add a text link to special:notifications in the dropdown, as opposed to entirely reimplementing the flyout layout Change-Id: I072dbc2b7bf70b6675469e09e3beb3927e06d0f7
2018-05-19 14:42:05 -04:00
"Hooks": {
Refactor: Simplify responsive Monobook's optional dependencies Having module definitions living inside SkinMonobook makes them less discoverable. It also shouldn't be necessary - even if there are soft dependencies on other modules. A new file resources/optional-enhancements.js is added which will load the two optional dependencies based on whether they have been installed on the client. Bug: T203023 Change-Id: If9a88db52deb0cc91d58cbb40693d4cd448eabbc
2020-08-04 17:39:18 -04:00
"GetPreferences": "SkinMonoBook::onGetPreferences"
Responsive support: Echo hacks Have echo just show the numbers instead of the badges, and add a text link to special:notifications in the dropdown, as opposed to entirely reimplementing the flyout layout Change-Id: I072dbc2b7bf70b6675469e09e3beb3927e06d0f7
2018-05-19 14:42:05 -04:00
},
Add skin.json Change-Id: Id93e8290ee75b319974ef12041bba48c428e77b5
2015-02-06 16:21:29 -05:00
"MessagesDirs": {
"MonoBook": [
"i18n"
]
},
"ResourceModules": {
"skins.monobook.styles": {
Drop mediawiki.skinning.interface in preparation for its deprecation Since MonoBook is never cached on Wikimedia wikis, we don't need to do anything about both modules being loaded in cached HTML. There should be no differences before and after this change. The change must apply to skins.monobook.styles and skins.monobook.responsive as these modules never load at the same time (see setupSkinUserCss). Bug: T242177 Change-Id: I5e69cd7f37f7b7a2b6325177b6688a426d92d57f
2020-02-05 01:23:16 -05:00
"class": "ResourceLoaderSkinModule",
Monobook should use opt-in policy for ResourceLoaderSkinModule features Bug: T252774 Change-Id: If9283742a83ecfbe8c4246e3624022a56be8f161
2020-09-14 18:17:35 -04:00
"features": {
"normalize": true,
"elements": true,
"content": true,
"interface": true,
"logo": true,
"legacy": true
},
Add user preference to control responsive MonoBook This provides a device agnostic, persistent opt-out for the new responsive functionality. The preference will show up under the skin selector if the user has their skin already set to MonoBook. I considered adding a new skin option to the radio selector of skins, but that is probably unnecessary for the majority of users, in addition to complicating how to differentiate the two modes (Classic MonoBook vs. Modern MonoBook?). Wikis that want to make this opt-in can control the default in the standard way ($wgDefaultUserOptions), or hide it entirely ($wgHiddenPrefs). Change-Id: Id22f8e5199ff2b15fd03c94097db5cdc7188f8b1
2018-06-03 18:50:36 -04:00
"styles": {
"resources/screen-common.less": {
"media": "screen"
},
"resources/screen-desktop.css": {
"media": "screen"
Print: Hide accessibility jump links and cookie statement Hide the accessibility jump navigation links when printing Also only show the last modified and copyright footer info and hide all the footer 'places' links by default. Bug: T250232 Bug: T136786 Change-Id: I039b523d009ddb4f5948dff456ef2845a93439fa
2020-08-15 05:15:26 -04:00
},
"resources/print-common.less": {
"media": "print"
Add user preference to control responsive MonoBook This provides a device agnostic, persistent opt-out for the new responsive functionality. The preference will show up under the skin selector if the user has their skin already set to MonoBook. I considered adding a new skin option to the radio selector of skins, but that is probably unnecessary for the majority of users, in addition to complicating how to differentiate the two modes (Classic MonoBook vs. Modern MonoBook?). Wikis that want to make this opt-in can control the default in the standard way ($wgDefaultUserOptions), or hide it entirely ($wgHiddenPrefs). Change-Id: Id22f8e5199ff2b15fd03c94097db5cdc7188f8b1
2018-06-03 18:50:36 -04:00
}
}
},
"skins.monobook.responsive": {
Drop mediawiki.skinning.interface in preparation for its deprecation Since MonoBook is never cached on Wikimedia wikis, we don't need to do anything about both modules being loaded in cached HTML. There should be no differences before and after this change. The change must apply to skins.monobook.styles and skins.monobook.responsive as these modules never load at the same time (see setupSkinUserCss). Bug: T242177 Change-Id: I5e69cd7f37f7b7a2b6325177b6688a426d92d57f
2020-02-05 01:23:16 -05:00
"class": "ResourceLoaderSkinModule",
Monobook should use opt-in policy for ResourceLoaderSkinModule features Bug: T252774 Change-Id: If9283742a83ecfbe8c4246e3624022a56be8f161
2020-09-14 18:17:35 -04:00
"features": {
"normalize": true,
"elements": true,
"content": true,
"interface": true,
"legacy": true,
"logo": true
},
Upgrade skin.json schema to manifest_version 2 Bug: T242502 Change-Id: I0c12363d8bfffef32305cf7190c90231f0adefa1
2020-01-10 23:47:16 -05:00
"targets": [
"desktop",
"mobile"
],
Add skin.json Change-Id: Id93e8290ee75b319974ef12041bba48c428e77b5
2015-02-06 16:21:29 -05:00
"styles": {
Rename main.less to screen-common.less to prepare for splitting Part of the move toward responsiveness. Change-Id: I6ca7c87fff7a65b05b2310885aedaeede9647c78
2018-03-24 14:01:41 -04:00
"resources/screen-common.less": {
Add skin.json Change-Id: Id93e8290ee75b319974ef12041bba48c428e77b5
2015-02-06 16:21:29 -05:00
"media": "screen"
Separate desktop and common styles, clean things up a bit Part of the move toward responsiveness. * Use mixins and variables! * Vectorise existing icons * Delete a rule or two that don't apply to the source anymore * Consolidate similar colours into the same ones using variables Change-Id: I2f0eb2b79cba01d8fa3a06298711e8af4d5508ba
2018-03-23 22:40:02 -04:00
},
Convert screen-desktop.less back to .css A proposed change (I737a7447db1e44e0d6abaa4c07813295a5ac73a6) requires this not to require Less parsing. It was unnecessary to convert this to Less when I could have just removed an `/* @embed */` annotation. Follow-up to ac8b055693c9bb64f1a499aa016454f791536ca2. Change-Id: Iba82f57d4ba3e65c61a5ef795b3b8d9c3f164a39
2018-04-18 19:02:36 -04:00
"resources/screen-desktop.css": {
Set mobile width cutoff to 550px Should avoid more of the issues with unwanted appearance of mobile layouts. Cutoff results in layout switch when sidebar becomes ~a third of the total window width. bug: T196213 Change-Id: I9b8baee5fe53316128f864e732c86750b4e5470e
2018-06-05 05:19:01 -04:00
"media": "screen and (min-width: 551px)"
Responsive support, noJS version * Add screen-mobile.css with basic mobile styles * Force loading of screen-desktop on IE8- due to lack of @media width support * Add some new divs and a set of spoof cactions for jumping around the page (what's js?) * Replace cactions label with a more descriptive string (was previously set to display:none regardless) * Also add a set of icons for fixed widths for tabs and things (icons-source.svg is the source file for the set, and includes a few others that ultimately weren't used here) Cutoff 850px. Desktop styles should remain unchanged, with mobile remaining stylistically consistent. Change-Id: I737a7447db1e44e0d6abaa4c07813295a5ac73a6
2018-05-01 15:44:43 -04:00
},
"resources/screen-mobile.less": {
Set mobile width cutoff to 550px Should avoid more of the issues with unwanted appearance of mobile layouts. Cutoff results in layout switch when sidebar becomes ~a third of the total window width. bug: T196213 Change-Id: I9b8baee5fe53316128f864e732c86750b4e5470e
2018-06-05 05:19:01 -04:00
"media": "screen and (max-width: 550px)"
Print: Hide accessibility jump links and cookie statement Hide the accessibility jump navigation links when printing Also only show the last modified and copyright footer info and hide all the footer 'places' links by default. Bug: T250232 Bug: T136786 Change-Id: I039b523d009ddb4f5948dff456ef2845a93439fa
2020-08-15 05:15:26 -04:00
},
"resources/print-common.less": {
"media": "print"
Add skin.json Change-Id: Id93e8290ee75b319974ef12041bba48c428e77b5
2015-02-06 16:21:29 -05:00
}
Fix skin.json ValidSkinNames is actually a registration setting, not a configuration one. Change-Id: I61c085fd89e81969eef6065b28cb24cbe0b366c9
2015-03-25 18:54:17 -04:00
}
Responsive support, JS edition Dropdown menus and js interactiveness for people who like to pretend we live in a modern era or something. Does not actually support newfangled tapping and swiping stuff. Does not properly support echo. (will follow up) Change-Id: I27d50c320b1526b9d158016a0e8022567f78ccc1
2018-05-03 15:45:10 -04:00
},
Refactor: Simplify responsive Monobook's optional dependencies Having module definitions living inside SkinMonobook makes them less discoverable. It also shouldn't be necessary - even if there are soft dependencies on other modules. A new file resources/optional-enhancements.js is added which will load the two optional dependencies based on whether they have been installed on the client. Bug: T203023 Change-Id: If9a88db52deb0cc91d58cbb40693d4cd448eabbc
2020-08-04 17:39:18 -04:00
"skins.monobook.mobile.uls": {
"targets": [ "desktop", "mobile" ],
"scripts": [ "resources/mobile-uls.js" ]
},
"skins.monobook.mobile.echohack": {
"targets": [ "desktop", "mobile" ],
"scripts": [ "resources/mobile-echo.js" ],
"styles": {
"resources/mobile-echo.less": {
"media": "screen and (max-width: 550px)"
}
},
"dependencies": [
"oojs-ui.styles.icons-alerts",
"mediawiki.util"
],
"messages": [
"monobook-notifications-link",
"monobook-notifications-link-none"
]
},
Responsive support, JS edition Dropdown menus and js interactiveness for people who like to pretend we live in a modern era or something. Does not actually support newfangled tapping and swiping stuff. Does not properly support echo. (will follow up) Change-Id: I27d50c320b1526b9d158016a0e8022567f78ccc1
2018-05-03 15:45:10 -04:00
"skins.monobook.mobile": {
Get legacy styles from ResourceLoaderSkinModule Instead of relying on Skin::getDefaultModules to get `mediawiki.legacy.styles` make the legacy style feature an explicit opt in choice by including it in the features list. This is done on the assumption that Icb910a563273bde92a09b1bb92857d5b6e348baa will shortly be merged to deprecate this module to avoid double loading the styles. Bug: T242177 Depends-On: Icb910a563273bde92a09b1bb92857d5b6e348baa Change-Id: I6471bc169f3c2a1f51e17b8ee26ac245b0374c18
2020-02-24 17:15:03 -05:00
"class": "ResourceLoaderSkinModule",
Monobook should use opt-in policy for ResourceLoaderSkinModule features Bug: T252774 Change-Id: If9283742a83ecfbe8c4246e3624022a56be8f161
2020-09-14 18:17:35 -04:00
"features": {
"normalize": true,
"elements": true,
"content": true,
"interface": true,
"logo": true,
"legacy": true
},
Get legacy styles from ResourceLoaderSkinModule Instead of relying on Skin::getDefaultModules to get `mediawiki.legacy.styles` make the legacy style feature an explicit opt in choice by including it in the features list. This is done on the assumption that Icb910a563273bde92a09b1bb92857d5b6e348baa will shortly be merged to deprecate this module to avoid double loading the styles. Bug: T242177 Depends-On: Icb910a563273bde92a09b1bb92857d5b6e348baa Change-Id: I6471bc169f3c2a1f51e17b8ee26ac245b0374c18
2020-02-24 17:15:03 -05:00
"targets": [ "desktop", "mobile" ],
Refactor: Simplify responsive Monobook's optional dependencies Having module definitions living inside SkinMonobook makes them less discoverable. It also shouldn't be necessary - even if there are soft dependencies on other modules. A new file resources/optional-enhancements.js is added which will load the two optional dependencies based on whether they have been installed on the client. Bug: T203023 Change-Id: If9a88db52deb0cc91d58cbb40693d4cd448eabbc
2020-08-04 17:39:18 -04:00
"packageFiles": [
"resources/mobile.js",
"resources/optional-enhancements.js"
Responsive support, JS edition Dropdown menus and js interactiveness for people who like to pretend we live in a modern era or something. Does not actually support newfangled tapping and swiping stuff. Does not properly support echo. (will follow up) Change-Id: I27d50c320b1526b9d158016a0e8022567f78ccc1
2018-05-03 15:45:10 -04:00
],
"styles": {
"resources/mobile.js.less": {
Set mobile width cutoff to 550px Should avoid more of the issues with unwanted appearance of mobile layouts. Cutoff results in layout switch when sidebar becomes ~a third of the total window width. bug: T196213 Change-Id: I9b8baee5fe53316128f864e732c86750b4e5470e
2018-06-05 05:19:01 -04:00
"media": "screen and (max-width: 550px)"
Responsive support, JS edition Dropdown menus and js interactiveness for people who like to pretend we live in a modern era or something. Does not actually support newfangled tapping and swiping stuff. Does not properly support echo. (will follow up) Change-Id: I27d50c320b1526b9d158016a0e8022567f78ccc1
2018-05-03 15:45:10 -04:00
}
},
"dependencies": [
"mediawiki.util"
]
Add skin.json Change-Id: Id93e8290ee75b319974ef12041bba48c428e77b5
2015-02-06 16:21:29 -05:00
}
},
Fix skin.json ValidSkinNames is actually a registration setting, not a configuration one. Change-Id: I61c085fd89e81969eef6065b28cb24cbe0b366c9
2015-03-25 18:54:17 -04:00
"ResourceFileModulePaths": {
"localBasePath": "",
"remoteSkinPath": "MonoBook"
},
Rework Monobook style of Preferences to prevent FOUC Also split preferences styles out from the main css file Depends on: I24d9b16 Bug: T115692 Change-Id: Ic0b3c18dde64fcd7b9f87baa866abd0a5a9c98d4
2015-11-08 09:02:01 -05:00
"ResourceModuleSkinStyles": {
"monobook": {
Restructure files according to modern skin practices Also delete unused images, since even if something is somewhere using them anyway (looked, couldn't find anything), it wouldn't be able to find them in the new image location regardless. Wiki.png, magnify, and link are all part of core and have been for some time. Change-Id: Id7a02155a5f1b207908c9c0c8f7519b6d3f9a886
2018-03-21 16:57:23 -04:00
"+mediawiki.action.view.redirectPage": "resources/skinStyles/mediawiki.action.view.redirectPage.css",
"+mediawiki.notification": "resources/skinStyles/mediawiki.notification.less",
Responsive support, JS edition Dropdown menus and js interactiveness for people who like to pretend we live in a modern era or something. Does not actually support newfangled tapping and swiping stuff. Does not properly support echo. (will follow up) Change-Id: I27d50c320b1526b9d158016a0e8022567f78ccc1
2018-05-03 15:45:10 -04:00
"+oojs-ui-core.styles": "resources/skinStyles/ooui.less",
Style RelatedArticle cards If RelatedArtcles uses the SkinAfterContent hook (depends-on patch) and we move the hook out of the main content block (parent patch), it needs some styles to remain consistent. Bug: T181242 Change-Id: I9fc00c22fb5e5b7d363455abe9d85062e67c7dfa Depends-On: Iebd759c0d1a536768d18953f372664df762d9e04
2019-06-20 14:08:43 -04:00
"+ext.uls.interface": "resources/skinStyles/ext.uls.interface.less",
"+ext.relatedArticles.readMore": "resources/skinStyles/ext.relatedArticles.readMore.less"
Rework Monobook style of Preferences to prevent FOUC Also split preferences styles out from the main css file Depends on: I24d9b16 Bug: T115692 Change-Id: Ic0b3c18dde64fcd7b9f87baa866abd0a5a9c98d4
2015-11-08 09:02:01 -05:00
}
},
Add skin.json Change-Id: Id93e8290ee75b319974ef12041bba48c428e77b5
2015-02-06 16:21:29 -05:00
"AutoloadClasses": {
Restructure files according to modern skin practices Also delete unused images, since even if something is somewhere using them anyway (looked, couldn't find anything), it wouldn't be able to find them in the new image location regardless. Wiki.png, magnify, and link are all part of core and have been for some time. Change-Id: Id7a02155a5f1b207908c9c0c8f7519b6d3f9a886
2018-03-21 16:57:23 -04:00
"SkinMonoBook": "includes/SkinMonoBook.php",
"MonoBookTemplate": "includes/MonoBookTemplate.php"
Set manifest_version in skin.json Bug: T100745 Change-Id: Ib2d5a91c6a2db1533fbf6d9b767b1dacb3207658
2015-06-02 02:54:10 -04:00
},
Upgrade skin.json schema to manifest_version 2 Bug: T242502 Change-Id: I0c12363d8bfffef32305cf7190c90231f0adefa1
2020-01-10 23:47:16 -05:00
"manifest_version": 2
Add skin.json Change-Id: Id93e8290ee75b319974ef12041bba48c428e77b5
2015-02-06 16:21:29 -05:00
}
Reference in a new issue Copy permalink