Skip to content

Commit d3671fb

Browse files
author
Stefan Heller
authored
Merge pull request #10 from code-keylogger/new-doc
Fixing frontend documentation as per Katz
2 parents bd46151 + c01ed0b commit d3671fb

File tree

11 files changed

+95
-149
lines changed

11 files changed

+95
-149
lines changed

.gitignore

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,9 @@
11
node_modules
22
.DS_Store
3-
out
3+
out
4+
keylogger-mvp/exec/run.glob
5+
keylogger-mvp/exec/run.vo
6+
keylogger-mvp/exec/run.vos
7+
keylogger-mvp/exec/run.vok
8+
keylogger-mvp/exec/exec.py
9+
keylogger-mvp/exec/prob.json

README.md

Lines changed: 33 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -10,38 +10,37 @@ be able to see their problem question and how many tests they are passing. Once
1010
finish they will open the Command Palette and type in 'Stop Testing'. Once this is complete
1111
the user will be prompted to copy the link to a survey and fill out it out in browser.
1212

13-
## Using the extension
14-
1. Install the .vsix extension into your instance of VSCode
15-
2. Make sure you have all the language's you will be using to solve problems installed on your local machine
16-
as that will be required to run the tests
17-
3. Start testing by pressing `f1` followed by `Start Testing`
18-
4. To finish testing press `f1` followed by `Stop Testing`
19-
20-
## Quick Start
21-
1. If you have not already installed the packages cd into keylogger-mvp and run 'npm i'
22-
2. Open vscode and navigate your path to where extension.js is located
23-
3. Once there run your f5 command or manually run extension.js either with or without debugging
24-
4. Once the new window opens, Open the command palette (ctrl + shift + p in windows)
25-
5. Type in Start Testing and press enter
26-
6. Enter your email address in the window prompt, once typed press enter
27-
7. Choose the language you are using by either selecting or typing one of the dropdown languages
28-
8. Choose the problem set you are using by either selecting or typing one of the dropdown problem sets
29-
9. Write your code once the problem appears
30-
10. When finished open the command palette and type Stop Testing and press enter
31-
11. A survey will prompt please copy the link into your browser and fill out the survey
32-
12. If you wish to use the extension again please exit out and begin from step 2 (Assuming you still have the packages installed)
33-
34-
35-
36-
## Running extension.js Documentation Locally
37-
38-
If you wish to view the documentation for this program in webpage format please follow the steps bellow:
39-
40-
1. Where extension.js is located along your path run './node_modules/.bin/jsdoc .\extension.js'
41-
or include 'Path To README.md \README.md' after '.\extension.js' in order to view this README.md on the Home page. (Recommended)
42-
ie: './node_modules/.bin/jsdoc .\extension.js path\to\readme\README.md\README.md'
43-
2. This will create a folder called out.
44-
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.
4724

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`

keylogger-mvp/exec/exec.py

Lines changed: 0 additions & 41 deletions
This file was deleted.

0 commit comments

Comments
 (0)