You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
3. Ensure your machine has the ability to open html files in browser.
45
-
4. Right click on extension.js.html and select the option "Open In Default Browser".
46
-
or however you wish to open the html file.
13
+
## Using the Extension
14
+
1. Install the `.vsix` extension file into your instance of VSCode.
15
+
a. Navigate to the extensions tab on the left of the window.
16
+
b. Click the `...` in the upper right
17
+
c. Select "install from vsix"
18
+
d. Select the file
19
+
2. Make sure you have all the languages you will be using to solve problems installed on your local machine and referenced in your `$PATH`.
20
+
3. Start testing by pressing `f1` followed by `Start Testing`. You will be prompted to enter your email to procede. (This must be the email provided to your admin)
21
+
4. To move on to a following test press `f1` followed by `Next Test`.
22
+
5. When a problem is finished you can hit `f1 -> Stop Testing` to stop your session, or the session will automatically stop when you have passed all the tests.
23
+
6. You will be prompted with a survey upon the completion of a problem to leave your feedback.
47
24
25
+
## Developing and Altering the Extension
26
+
27
+
### Simple Config
28
+
29
+
1. To change the survey link, time limit, or any other configuration parameters make changes in `keylogger-mvp > pluginConfig.json`.
30
+
2. When changes have been made you simply repackage the plugin by running `vsce package` from the `keylogger-mvp/` directory.
31
+
32
+
### Debugging and Further Developement
33
+
34
+
1. To add additional features or fix any bugs you can make changes (likely to `extension.js`) from there you can debug the plugin.
35
+
36
+
1. If you have not already installed the packages cd into keylogger-mvp and run `npm i`
37
+
2. Open vscode and navigate your path to where extension.js is located
38
+
3. Once there run your `f5` command or manually run extension.js either with or without debugging
39
+
4. Once the new window opens, Open the command palette (ctrl + shift + p in windows)
40
+
5. Type in `Start Testing` and press `enter`
41
+
42
+
2. To add additional language support you must:
43
+
44
+
1. Add a new "runner file" in the `exec` directory. Follow the example of `compile.py`
45
+
2. Add a new case to the `replacer.py` file
46
+
3. Handle the new language in `runTest()` within `extension.js`
0 commit comments