Skip to content
This repository has been archived by the owner on Apr 18, 2022. It is now read-only.

Version 8.0.0

Latest
Latest
Compare
Choose a tag to compare
@HM100 HM100 released this 17 Mar 21:50
· 2 commits to main since this release
8.0.0
b9ff3b9
This commit was created on github.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
  • Added dependency to Evelution Skin as some of its Configuration settings are now usable on Tunic as well
    • Evelution 66.0.0 or newer is required IN ADDITION TO MediaWiki 1.36 or newer in order to install Tunic 8.0.0
  • Added back localization to Color Modes, Visual Styles and Visual Colors
  • OOUI icons now display the same as Material Icons (With the exception of Wikimedia Icons). Some icons differ from the previous OOUI versions
  • Added new Generic Colors (Progress and Pause) and tweaked the hues of the three existing ones
    • All generic colors generated have contrast of 3 or above (Depending on the contrast level set)
    • Buttons and banners with these colors can also be made as well
  • Recent Changes filters color highlighting is now properly themed
  • Tweaked fadeout colors
  • Progress bars, unlike range inputs now use generic colors for its filler (Progress for general, Success for completed, Pause for halted and Alert for Failed. Warning and Message colors are never used as filler colors)
  • Stub links are now themed using the Progress color
  • Renamed some banner notification classes (i.e. cpe-alert becomes ``is-alert`)
  • Introduced the ability to use a custom color for dropdown menus (Both Backgrond and Text Colors)
    • This requires a client with Servelution 3.3.0 or higher
  • Some adjustments to Disabled Color Management and Forced Colors mode
    • Improved how Disabled Color Management works
      • Those don't apply in Chrome while in forced colors mode as they are fixed to a specific color
  • Tweaks to Inactive Title and Generic Colors
  • Changed default rounded corners value to 5px
  • Icon font is now done using a variable, to reduce code
  • Updated Material Icons fonts
  • Added the ability to control themes using PHP:
    • $wgEvelutionThemeA is for Theme A
    • $wgEvelutionThemeB is for Theme B
    • $wgEvelutionThemeC is for Theme C
    • $wgEvelutionThemeD is for Theme D
    • $wgEvelutionThemeE is for Theme E
    • $wgEvelutionThemeF is for Theme F
    • $wgEvelutionThemeG is for Theme G
    • $wgEvelutionThemeH is for Theme H
    • See here for a theming template example that can be used to base yours
  • You can now omit the url() notation in the --desktop-background-image customization and will be automatically added by the Theming Engine compilation
  • Redesigned Banner Notifications to look like the ones found in recent Fandom Design System updates (Fandomdesktop). Changes include:
    • Limited width to 480px maximum
    • They now float to the bottom left corner instead of being placed above the taskbar
    • Border radius position in the icons have been swapped
    • The entire container no longer has box shadow in it, the banners have it instead.
    • Borders are now placed around the banners and they have a bottom margin instead of being separated by borders
    • Banners now slide to the left when they disappear instead of scaling down to 0 height in addition of becoming fully transparent
    • When a lot of banners appear, they no longer overflow, instead you can scroll to see the rest of them
    • A new button called Clear all has been added atop the banners. Click on that button to dismiss all displayed banners at once
  • More bug fixes on OOUI including
    • Button Groups and Comboboxes now have proper margins, sizing and border radius
    • Some icon misalignment fixes
    • Select Dropdown Boxes no longer have giant margin compared to text input boxes
  • Improvements to Calendar widget theming
  • When Selecting a Color Pack in where the theme has errors or a Theme slot that has errors in the code, instead of leaving the site unusable after reload, it instead alerts the user and rolls back the change that would happen
  • Added the ability to force plain cpe-button be secondary or tertiary by default. Just put the force-secondary and force-tertiary classes respectively in the element that houses the CPE buttons. You can add to an inner button the is-primary class to make buttons inside that containers primary such as:
<div class="cpe-button-group force-secondary">
    <button class="cpe-button">Test</button>
    <button class="cpe-button is-primary">Test 2</button>
    <button class="cpe-button">Test 3</button>
</div>
Assets 2
Loading