vscode-cpptools/Themes
Charles Milette 928a5d4b03
Update Theme extension image previews to work in the store (#7977)
2021-08-17 14:54:10 -07:00
..
.vscode VS Code themes that match VS Light and Dark, including semantic tokens (#4019) 2019-08-06 10:41:25 -07:00
assets Minor reorganization of theme assets (#4149) 2019-08-27 10:38:47 -07:00
themes Switch to Semantic Tokens API (#5401) 2020-07-01 14:48:26 -07:00
.vscodeignore Minor reorganization of theme assets (#4149) 2019-08-27 10:38:47 -07:00
LICENSE.txt Add readme and license to Themes directory (#4111) 2019-08-26 13:59:48 -07:00
README.md Update Theme extension image previews to work in the store (#7977) 2021-08-17 14:54:10 -07:00
package-lock.json Minor reorganization of theme assets (#4149) 2019-08-27 10:38:47 -07:00
package.json Minor reorganization of theme assets (#4149) 2019-08-27 10:38:47 -07:00

README.md

C/C++ Extension UI Themes

Semantic colorization was added to the C/C++ Extension in version 0.24.0. At the time, colorization in VS Code was purely syntactic/lexical and leveraged TextMate grammar to associate named 'scopes' with syntactic elements. Themes and settings can be used to associate colors with these scopes. Our original implementation of semantic colorization leveraged the same system of associating colors with named scopes. But, some tokens that can be colored by semantic colorization in C/C++ did not have existing analogs in VS Code's TextMate grammar. So, new named scopes are required. Because these scopes were new, existing themes did not include colors for them either.

We created C/C++ Extension UI Themes to closely match Visual Studio themes and include colors for many of the new scopes.

VS Code has since provided an API for semantic colorization. The C/C++ Extension has transitioned from its own implementation to this new API. These themes now include colors for some of the new semantic token scopes.

Example

Light Theme

Light Theme example

Dark Theme

Dark Theme example

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.