diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..722d5e7 --- /dev/null +++ b/.gitignore @@ -0,0 +1 @@ +.vscode diff --git a/.vscode/launch.json b/.vscode/launch.json index 8384213..5901239 100644 --- a/.vscode/launch.json +++ b/.vscode/launch.json @@ -10,4 +10,4 @@ "args": ["--extensionDevelopmentPath=${workspaceRoot}" ] } ] -} \ No newline at end of file +} diff --git a/CHANGELOG.md b/CHANGELOG.md index 6a63185..031092b 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,7 +1,4 @@ # Change Log -All notable changes to the "calamity-vscode" extension will be documented in this file. -Check [Keep a Changelog](http://keepachangelog.com/) for recommendations on how to structure this file. - -## [Unreleased] +## [1.0.0] - 2017-07-23 - Initial release diff --git a/LICENSE.md b/LICENSE.md new file mode 100644 index 0000000..8c860ae --- /dev/null +++ b/LICENSE.md @@ -0,0 +1,20 @@ +Copyright (c) 2017 + +Permission is hereby granted, free of charge, to any person obtaining +a copy of this software and associated documentation files (the +"Software"), to deal in the Software without restriction, including +without limitation the rights to use, copy, modify, merge, publish, +distribute, sublicense, and/or sell copies of the Software, and to +permit persons to whom the Software is furnished to do so, subject to +the following conditions: + +The above copyright notice and this permission notice shall be +included in all copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, +EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND +NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE +LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION +OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION +WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. diff --git a/README.md b/README.md index 78078e0..b55097c 100644 --- a/README.md +++ b/README.md @@ -1,13 +1,36 @@ -# README -## This is the README for your extension "calamity-vscode" -You can author your README using Visual Studio Code. Here are some useful editor keyboard shortcuts: +# [Calamity Theme for VSCode](https://marketplace.visualstudio.com/items?itemName=pustur.calamity-vscode) +> A purple dark theme with medium to high contrast for [Visual Studio Code](https://code.visualstudio.com) -* Split the editor (`Cmd+\` on OSX or `Ctrl+\` on Windows and Linux) -* Toggle preview (`Shift+CMD+V` on OSX or `Shift+Ctrl+V` on Windows and Linux) -* Press `Ctrl+Space` (Windows, Linux) or `Cmd+Space` (OSX) to see a list of Markdown snippets +![calamity-logotype](images/logotype.png) -### For more information -* [Visual Studio Code's Markdown Support](http://code.visualstudio.com/docs/languages/markdown) -* [Markdown Syntax Reference](https://help.github.com/articles/markdown-basics/) +![calamity-screenshot](images/screenshot.png) -**Enjoy!** \ No newline at end of file +## Supported languages + +- JavaScript +- CSS + - SCSS + - Sass + - Less +- PHP +- SQL +- Pug / Jade +- Python +- HTML / XML +- Markdown +- JSON +- YAML + +## Supported editors + +Also available for: + +- [Atom](https://atom.io/themes/calamity-syntax) + +## Contributing + +If you want more languages a PR is always welcome! 🙂 + +## License + +[MIT](https://github.com/Pustur/calamity-vscode/blob/master/LICENSE.md) diff --git a/images/logo.png b/images/logo.png new file mode 100644 index 0000000..bd1890d Binary files /dev/null and b/images/logo.png differ diff --git a/images/logotype.png b/images/logotype.png new file mode 100644 index 0000000..a0185da Binary files /dev/null and b/images/logotype.png differ diff --git a/images/screenshot.png b/images/screenshot.png new file mode 100644 index 0000000..7e80d0e Binary files /dev/null and b/images/screenshot.png differ diff --git a/package.json b/package.json index 5715a88..2752832 100644 --- a/package.json +++ b/package.json @@ -1,9 +1,19 @@ { "name": "calamity-vscode", - "displayName": "Calamity VSCode", + "displayName": "Calamity", "description": "A purple dark theme with medium to high contrast", - "version": "0.0.1", - "publisher": "Loris", + "version": "1.0.0", + "icon": "images/logo.png", + "galleryBanner.color": "#2F2833", + "publisher": "Pustur", + "author": { + "name": "Loris Bettazza", + "url": "https://github.com/Pustur", + "email": "loris.bettazza@gmail.com" + }, + "repository": { + "url": "https://github.com/Pustur/calamity-vscode" + }, "engines": { "vscode": "^1.14.0" }, @@ -19,4 +29,4 @@ } ] } -} \ No newline at end of file +} diff --git a/vsc-extension-quickstart.md b/vsc-extension-quickstart.md deleted file mode 100644 index 541db4b..0000000 --- a/vsc-extension-quickstart.md +++ /dev/null @@ -1,27 +0,0 @@ -# Welcome to your VS Code Extension - -## What's in the folder -* This folder contains all of the files necessary for your color theme extension -* `package.json` - this is the manifest file that defines the location of the theme file -and specifies the base theme of the theme -* `themes/Calamity-color-theme.json` - the color theme definition file - -## Get up and running straight away -* press `F5` to open a new window with your extension loaded -* open `File > Preferences > Color Themes` and pick your color theme -* Open a file that has a language associated. The languages' configured grammar will tokenize the text and assign 'scopes' to the tokens. To examine these scopes, invoke the `Inspect TM Scopes` command from the Commmand Palette (`Ctrl+Shift+P` or `Cmd+Shift+R` on Mac) . - -## Make changes -* you can relaunch the extension from the debug toolbar after making changes to the files listed above -* you can also reload (`Ctrl+R` or `Cmd+R` on Mac) the VS Code window with your extension to load your changes -* When editing workbench colors, it's easiest to test the colors in the settings under `workbench.colorCustomizations`. When done, run the `Generate Color Theme From Current Settings` command to generate an updated content for the color theme definition file. - -## Adopt your theme to Visual Studio Code -* The token colorization is done based on standard TextMate themes. Colors are matched against one or more scopes. -To learn about what scopes are used where, check out the [TextMate documentation](https://manual.macromates.com/en/themes) -and the [Scope Naming](https://www.sublimetext.com/docs/3/scope_naming.html) documentation from Sublime. -* A great place to examine themes is [here](https://tmtheme-editor.herokuapp.com/#!/editor/theme/Monokai). - -## Install your extension -* To start using your extension with Visual Studio Code copy it into the `/.vscode/extensions` folder and restart Code. -* To share your extension with the world, read on https://code.visualstudio.com/docs about publishing an extension.