Browse Source

more release features

Karathan 6 years ago
parent
commit
7a3ab06ae6
7 changed files with 20 additions and 88 deletions
  1. 4
    1
      README.md
  2. BIN
      images/icon.png
  3. BIN
      images/screen.png
  4. 16
    14
      package.json
  5. 0
    29
      src/extension.ts
  6. 0
    22
      src/test/extension.test.ts
  7. 0
    22
      src/test/index.ts

+ 4
- 1
README.md View File

@@ -1,4 +1,7 @@
1 1
 # Pokéscript Language Support for Visual Studio Code
2 2
 
3
-Adds syntax highlighting for the Pokéscript language to Visual Studio Code. It is based on https://github.com/dan-c-underwood/vscode-arm - An ARM support Extension.
3
+Adds syntax highlighting for the Pokéscript language to Visual Studio Code. For an example macro definition for the pokéscript language you can use https://gist.github.com/SBird1337/0238742cdf606ae6fdec7587b063b30f, which this is currently compliant with. Currently only Syntax Highlighting is supported, but IntelliSense of some sort is planned.
4 4
 
5
+Here is an example of how the Syntax Highlighting looks:
6
+
7
+![PokéScript](images/screen.png "Screenshot")

BIN
images/icon.png View File


BIN
images/screen.png View File


+ 16
- 14
package.json View File

@@ -2,21 +2,29 @@
2 2
     "name": "pokescript",
3 3
     "displayName": "PokéScript",
4 4
     "description": "PokéScript Language Support",
5
-    "version": "0.0.1",
5
+    "version": "1.0.1",
6
+    "homepage": "https://gitlab.karathan.at/Karathan/vs-pokescript",
7
+    "repository": {
8
+        "type": "git",
9
+        "url": "https://gitlab.karathan.at/Karathan/vs-pokescript"
10
+    },
11
+    "license": "MIT",
12
+	"galleryBanner": {
13
+		"color": "#0084A9",
14
+		"theme": "dark"
15
+    },
16
+    "icon": "images/icon.png",
6 17
     "publisher": "karathan",
7 18
     "engines": {
8 19
         "vscode": "^1.25.0"
9 20
     },
10
-    "categories": [
11
-        "Other"
12
-    ],
21
+    "categories": ["Programming Languages"],
22
+    "keywords": ["romhacking", "assembly", "pokescript"],
23
+    "preview": true,
24
+
13 25
     "extensionDependencies": [
14 26
         "dan-c-underwood.arm"
15 27
     ],
16
-    "activationEvents": [
17
-        "onCommand:extension.sayHello"
18
-    ],
19
-    "main": "./out/extension",
20 28
     "contributes": {
21 29
         "grammars":[
22 30
             {
@@ -24,12 +32,6 @@
24 32
                 "path": "./syntaxes/pokescript.json",
25 33
                 "injectTo": [ "source.arm" ]
26 34
             }
27
-        ],
28
-        "commands": [
29
-            {
30
-                "command": "extension.sayHello",
31
-                "title": "Hello World"
32
-            }
33 35
         ]
34 36
     },
35 37
     "scripts": {

+ 0
- 29
src/extension.ts View File

@@ -1,29 +0,0 @@
1
-'use strict';
2
-// The module 'vscode' contains the VS Code extensibility API
3
-// Import the module and reference it with the alias vscode in your code below
4
-import * as vscode from 'vscode';
5
-
6
-// this method is called when your extension is activated
7
-// your extension is activated the very first time the command is executed
8
-export function activate(context: vscode.ExtensionContext) {
9
-
10
-    // Use the console to output diagnostic information (console.log) and errors (console.error)
11
-    // This line of code will only be executed once when your extension is activated
12
-    console.log('Congratulations, your extension "pokescript" is now active!');
13
-
14
-    // The command has been defined in the package.json file
15
-    // Now provide the implementation of the command with  registerCommand
16
-    // The commandId parameter must match the command field in package.json
17
-    let disposable = vscode.commands.registerCommand('extension.sayHello', () => {
18
-        // The code you place here will be executed every time your command is executed
19
-
20
-        // Display a message box to the user
21
-        vscode.window.showInformationMessage('Hello World!');
22
-    });
23
-
24
-    context.subscriptions.push(disposable);
25
-}
26
-
27
-// this method is called when your extension is deactivated
28
-export function deactivate() {
29
-}

+ 0
- 22
src/test/extension.test.ts View File

@@ -1,22 +0,0 @@
1
-//
2
-// Note: This example test is leveraging the Mocha test framework.
3
-// Please refer to their documentation on https://mochajs.org/ for help.
4
-//
5
-
6
-// The module 'assert' provides assertion methods from node
7
-import * as assert from 'assert';
8
-
9
-// You can import and use all API from the 'vscode' module
10
-// as well as import your extension to test it
11
-// import * as vscode from 'vscode';
12
-// import * as myExtension from '../extension';
13
-
14
-// Defines a Mocha test suite to group tests of similar kind together
15
-suite("Extension Tests", function () {
16
-
17
-    // Defines a Mocha unit test
18
-    test("Something 1", function() {
19
-        assert.equal(-1, [1, 2, 3].indexOf(5));
20
-        assert.equal(-1, [1, 2, 3].indexOf(0));
21
-    });
22
-});

+ 0
- 22
src/test/index.ts View File

@@ -1,22 +0,0 @@
1
-//
2
-// PLEASE DO NOT MODIFY / DELETE UNLESS YOU KNOW WHAT YOU ARE DOING
3
-//
4
-// This file is providing the test runner to use when running extension tests.
5
-// By default the test runner in use is Mocha based.
6
-//
7
-// You can provide your own test runner if you want to override it by exporting
8
-// a function run(testRoot: string, clb: (error:Error) => void) that the extension
9
-// host can call to run the tests. The test runner is expected to use console.log
10
-// to report the results back to the caller. When the tests are finished, return
11
-// a possible error to the callback or null if none.
12
-
13
-import * as testRunner from 'vscode/lib/testrunner';
14
-
15
-// You can directly control Mocha options by uncommenting the following lines
16
-// See https://github.com/mochajs/mocha/wiki/Using-mocha-programmatically#set-options for more info
17
-testRunner.configure({
18
-    ui: 'tdd', 		// the TDD UI is being used in extension.test.ts (suite, test, etc.)
19
-    useColors: true // colored output from test results
20
-});
21
-
22
-module.exports = testRunner;