hxuanyu/intellij-sdk-code-samples
1
0
Fork 0
mirror of https://github.com/JetBrains/intellij-sdk-code-samples.git synced 2025-07-28 01:07:49 +08:00
Code Issues Packages Projects Releases Wiki Activity

color_scheme_management.md: Cleanup

Browse Source
This commit is contained in:
Karol Lewandowski 2023-07-12 15:43:50 +02:00
parent fa43442e0b
commit 4a79d68a12
1 changed files with 21 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
topics/reference_guide/color_scheme_management.md
View File

@ -5,14 +5,14 @@
<link-summary>Developing new color schemes for existing and custom languages.</link-summary>
Color scheme management in IntelliJ IDEA 12.1 was changed to ease scheme designers' work and make schemes look equally well for different programming languages even if not designed specifically for these languages.
Previously, language plug-ins were using fixed default colors incompatible, for example, with dark schemes.
Previously, language plugins were using fixed default colors incompatible, for example, with dark schemes.
The new implementation allows specifying a dependency on a set of standard text attributes linked to a scheme but not to any specific language.
Language-specific attributes still can be set by a scheme designer if needed, but it's optional.
New color schemes have got a new <path>.icls</path> (Idea CoLor Scheme) extension to avoid confusion about compatibility problems with older platform versions:
if only standard attributes are set, they will not be used by the version before 12.1, resulting in different highlighting colors.
## Plug-in Developers
## Plugin Developers
### Text Attribute Key Dependency
@ -43,11 +43,11 @@ The rule is the same: if text attributes can not be found by the `MY_PREDEFINED_
If you are unsure which base key to use, it's better to pick the most generic one, for example, `DefaultLanguageHighlighterColors.IDENTIFIER`.
Remember that using fixed default attributes *will force* a scheme designer to explicitly set up a color for this element.
Otherwise, its default colors may visually conflict with a color scheme.
If the scheme designer doesn't have a language plug-in, he will not be able to fix this at all.
If the scheme designer doesn't have a language plugin, he will not be able to fix this at all.
### Providing Attributes for Specific Schemes
A language plug-in may provide default text attributes for "Default" and "Darcula" bundled schemes or basically for any other scheme if the scheme's name is known.
A language plugin may provide default text attributes for "Default" and "Darcula" bundled schemes or basically for any other scheme if the scheme's name is known.
This can be done in <path>[plugin.xml](plugin_configuration_file.md)</path> by adding an `com.intellij.additionalTextAttributes` extension providing the name of the file containing desired text attributes, for example:
```xml
@ -84,29 +84,32 @@ The file itself is an extract from a color scheme with required attributes, for
</list>
```
*Note:* When the scheme is copied via "Save as..." all its attributes, including the ones defined in the extension, will be copied to the new scheme.
A scheme designer may need to check that these copied attributes do not conflict with his/her color scheme, although in this case, the plug-in is installed, and it should not cause any problems.
*Note:* When the scheme is copied via <control>Save as...</control> all its attributes, including the ones defined in the extension, will be copied to the new scheme.
A scheme designer may need to check that these copied attributes do not conflict with their color scheme, although in this case, the plugin is installed, and it should not cause any problems.
Anyway, try to stick with a simple key dependency if possible (note that it works well for "Darcula") and provide explicit attributes only if necessary.
## Scheme Designers
### A Typical Workflow for a New Scheme Creation
<procedure title="A Typical Workflow for a New Scheme Creation">
* Choose a scheme which will be used as a base, for example, "Default"
* Click "Save As..." and give a name for the new scheme
* First set attributes in the *General* section and proceed with *Language Defaults*
* Check all the languages and adjust language-specific text attributes if necessary.
1. Choose a scheme which will be used as a base, for example, "Default".
2. Click <control>Save As...</control> and give a name for the new scheme.
3. First set attributes in the <control>General</control> section and proceed with <control>Language Defaults</control>.
4. Check all the languages and adjust language-specific text attributes if necessary.
In most cases, this may not be needed, but two cases may require an extra action:
* There is an obsolete plug-in which does not use the new color scheme management API and therefore does not utilize the attributes set in "Language Defaults".
Ideally, a report must be created for the language plug-in so that its author will fix it eventually.
* A plug-in intentionally sets some default colors and, if the scheme was created from a default one, the colors are copied to the newly created scheme.
This can be fixed either by resetting all the attributes to restore the inheritance from Language Defaults (see below) or by setting other colors suitable for the scheme.
The first way is preferable since it will require less effort to change the color scheme later.
* There is an obsolete plugin which does not use the new color scheme management API and therefore does not utilize the attributes set in <control>Language Defaults</control>.
Ideally, a report must be created for the language plugin so that its author will fix it eventually.
* A plugin intentionally sets some default colors and, if the scheme was created from a default one, the colors are copied to the newly created scheme.
This can be fixed either by resetting all the attributes to restore the inheritance from <control>Language Defaults</control> (see below) or by setting other colors suitable for the scheme.
The first way is preferable since it will require less effort to change the color scheme later.
</procedure>
### Text Attributes Inheritance
For many language text attributes that do not have any values, there will be a line indicating that the attributes are inherited from a specific section/attributes, such as "Keyword (Language Defaults)".
For many language text attributes that do not have any values, there will be a line indicating that the attributes are inherited from a specific section/attributes, such as <control>Keyword</control> in <control>Language Defaults</control>.
If an element has *any* attributes set, only these attributes are used.
All attributes from the base element are ignored.
To *restore* the inheritance, uncheck all the boxes, and click *Apply*.
To *restore* the inheritance, uncheck all the boxes, and click <control>Apply</control>.