0.8.0
Changelog for Nord JetBrains — An arctic, north-bluish clean and elegant JetBrains IDE UI and editor color theme
This version mainly focused on supporting the latest JetBrains product versions 2019.2 that introduced some breaking changes for UI theme keys and the changes in Go's syntax highlighting for the default bundled color schemes.
Features
Go syntax highlighting support for IntelliJ/Goland 2019.2 — #69 ⇄ #70 (⊶ adbea3b) by @smonv
↠ IntelliJ/Goland version 2019.2 introduced support for 20+ languages out-of-the-box by integrating TextMate schemes as well as changes in Go's syntax highlight for the default bundled color schemes.
Unfortunately this resulted in a change for existing theme definitions where some editor color scheme keys that previously inherited the best matching global key now used the attributes defined by the parent theme Darcula. Therefore Nord's highlighting for Go broke and required to explicitly define the values for some attributes in order to achieve the same highlight like in previous versions that are matching Nord's style guidelines.
Before
After
Support 2019.2 deprecation replacement UI theme keys — #86 ⇄ #87 (⊶ 990c2d2)
↠ The latest JetBrains product versions 2019.2 deprecated some UI theme keys in favour of new keys that (can be found through the auto-completion and quick documentation thanks to the also new @since
doc tag support for theme schemes). This broke the styles when using the Nord plugin with the latest product versions due to the missing new keys.
In order to support both versions <2019.2
as well as >=2019.2
the new keys have been added while also keeping the deprecated ones until they'll be removed from the UI theme API.
- Editor tabs using new keys for the active background (
underlinedTabBackground
) and when hovered (hoverMaskColor
) and also now support customization of the bottom stripe when not focused (inactiveUnderlineColor
). - Debugger tabs are now using a new key for the background color (
underlinedTabBackground
) when active. - The auto-completion popup now uses the same color like the
DOCUMENTATION_COLOR
attribute of the editor color scheme as well as a new key for the currently active selection (selectionBackground
). - The components of the status bar now using a new key to for the background color when hovered (
hoverBackground
).
Editor Tabs
Before
After
Auto Completion Popup
Before
After
Debugger Tabs
Before
After
Status Bar Components
Before
After
Hovering Editor Tabs & Status Bar Components
Before
Hovering Editor Tabs & Status Bar Components
Console log output — #73 ⇄ #74 (⊶ b9ab18c)
↠ The JetBrains theme API in version 2019.2 introduced new keys to customize log output in the console that have been added:
LOG_DEBUG_OUTPUT
— syntax color for output of the DEBUG level usingnord15
LOG_INFO_OUTPUT
— syntax color for output of the INFO level usingnord8
LOG_VERBOSE_OUTPUT
— syntax color for verbose output usingnord7
Before
After
Diagram Theme Support — #75 ⇄ #76 (⊶ e7dd070)
↠ JetBrains core product version 2019.2 introduced theme support for Diagrams in order to prevent unreadable output due to „hardcoded“ color values not matching the currently active UI theme. The available theme keys have been added to better match Nord's style.
Before
After
JavaScript syntax highlighting support for product versions 2019.2 — #77 ⇄ #78 (⊶ 7884fd3)
↠ ↠ The JetBrains theme API in version 2019.2 introduced new keys for JavaScript global variables as well as instance functions that have been added:
JS.GLOBAL_FUNCTION
— mapped toDEFAULT_FUNCTION_DECLARATION
JS.GLOBAL_VARIABLE
— mapped toDEFAULT_GLOBAL_VARIABLE
JS.INSTANCE_MEMBER_FUNCTION
— mapped toDEFAULT_INSTANCE_METHOD
Before
After
Normal styles for TypeScript "type guarded" variables — #81 ⇄ #82 (⊶ 48bf488)
↠ Variables for TypeScript that are "type guarded" previously used a greenish background color inherited from the parent Darcula scheme and have been changed to use the default variables style instead since there is no need to explicitly highlight these syntax elements.
Before
After
Normal styles for TypeScript "type guarded" variables — #35 ⇄ #83 (⊶ 12200f3)
↠ Added support for the official Python plugin that adds syntax highlighting for Python as well as Jupyter and Mako Templates and is equal to the PyCharm Professional Edition.
Before
Python
Jupyter
Mako Templates
After
Python
Jupyter
Mako Templates
Improvements
No italic font for user input in console — #71 ⇄ #72 (⊶ 607a35e)
↠ Previously the font style for console user input was italic that has been changed to use a normal style.
Use nord8
for Markdown link titles — #79 ⇄ #80 (⊶ 399af75)
↠ The color of Markdown link titles was highlighted with nord14
and has been changed to nord8
in order to match Nord's Markdown syntax styles.
Before
After
No more editor color scheme font configurations — #84 ⇄ #85 (⊶ 69942bc)
↠ In previous JetBrains product versions the editor color scheme allowed to provide configurations for the font rendering like the font family and size the user can apply by enabling checkbox through the editor font preferences labelled with „Use color scheme font instead of default“.
In the latest versions like 2019.x these settings applied by default, overriding the user-defined font configuration which led to unintended font rendering.
In order to prevent such problems as well as unexpected styles when the color scheme font family is not installed on the system, the configured font configurations has been removed completely.
Not defining font configurations is also recommended for shared color schemes (plugins) like mentioned in the official documentations:
Customize the color scheme font
This is not recommended if you are planning to share your scheme or use it on other platforms, which may not support the selected font. In such cases, use the default global font settings.
Copyright © 2016-present Arctic Ice Studio and Sven Greb
The full changelog ist available here.