Skip to content

Commit a612872

Browse files
knightburtonyichoi
authored andcommitted
Update README.md (#42)
IoT.js-Debug-DCO-1.0-Signed-off-by: Imre Kiss [email protected]
1 parent ed1a3f1 commit a612872

File tree

1 file changed

+21
-70
lines changed

1 file changed

+21
-70
lines changed

README.md

Lines changed: 21 additions & 70 deletions
Original file line numberDiff line numberDiff line change
@@ -1,90 +1,41 @@
1-
# VSCode IoT.js Debug
2-
IoT.js and JerryScript debug adapter for Visual Studio Code.
1+
# IoT.js debug and language extension for VSCode.
2+
3+
[![License](https://img.shields.io/badge/licence-Apache%202.0-brightgreen.svg?style=flat)](LICENSE)
34

45
- [Introduction](#introduction)
56
- [Features](#features)
67
- [Requirements](#requirements)
7-
- [How to start](#how-to-start)
88
- [How to use](#how-to-use)
99
- [License](#license)
1010

1111
# Introduction
12-
`IoT.js Debug` is a debugger extension for [Visual Studio Code](https://code.visualstudio.com/) that lets you debug the code which is running on a device and lets you upload your code to the device, directly from the VSCode over websocket communication.
12+
`IoT.js VSCode Extension` is a debugger and language (like intelliSense, hover, ...) extension for [Visual Studio Code](https://code.visualstudio.com/) that lets you debug the code which is running on a device, lets you upload your code to the device, directly from the VSCode over websocket communication and helps you to write code with [IoT.js](https://github.com/Samsung/iotjs).
1313

1414
# Features
15-
Available Control commands:
16-
- Continue command
17-
- Pause command
18-
- Step-over command
19-
- Step-in command
20-
- Step-out command
21-
- Disconnect command
22-
23-
Available features:
24-
- Set/Remove breakpoint
25-
- Call stack display
26-
- Watch (evaluate expression)
27-
- Handle source receive from the engine
28-
- Sending source code from the vscode to the engine
29-
30-
Currently in Progress features or commands:
31-
- IoT.js module based completion
15+
- Debugger
16+
- Available Control commands:
17+
- Continue command
18+
- Pause command
19+
- Step-over command
20+
- Step-in command
21+
- Step-out command
22+
- Disconnect command
23+
24+
- Available features:
25+
- Set/Remove breakpoint
26+
- Call stack display
27+
- Watch (evaluate expression)
28+
- Handle source receive from the engine
29+
- Sending source code from the vscode to the engine
3230

3331
# Requirements
3432
- The latest Vscode which is available [here](https://code.visualstudio.com/Download).
3533
- An [IoT.js](https://github.com/Samsung/iotjs) or a [JerryScript](https://github.com/jerryscript-project/jerryscript) as an engine to run your code.
3634

3735
- (For development) Requires [node.js](https://nodejs.org/en/) v8.x.x or higher (latest one is recommended) and [npm](https://www.npmjs.com) 5.x.x or higher to be able to work properly.
3836

39-
# How to start
40-
Getting the sources:
41-
42-
```sh
43-
# Clone the repository to your local drive:
44-
$ git clone https://github.com/knightburton/vscode-iotjs-debug
45-
46-
# Move into the directory
47-
$ cd vscode-iotjs-debug
48-
```
49-
50-
The project requires node.js to build, the best way to install the node and the npm is the nvm (Node Version Manager):
51-
52-
```sh
53-
# Install the latest nvm with the following command
54-
$ curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.9/install.sh | bash
55-
56-
# Reload your .bashrc
57-
$ source ~/.bashrc
58-
```
59-
60-
Use the proper node.js and node package manager version:
61-
```sh
62-
# Install the latest node.js and npm with the nvm tool
63-
$ nvm install 9
64-
65-
# If you have already installed the node.js and npm then make sure you are using the right version in the project folder
66-
$ nvm use 9
67-
```
68-
69-
Install the project dependencies:
70-
```sh
71-
npm install
72-
```
73-
74-
For the first time you have to build the project to be able to start the extension host, this will build the project into the `out` folder:
75-
```sh
76-
npm run compile
77-
```
78-
79-
To start the extension you have to open the project in VSCode and you have to navigate to the Debug view (Ctrl+Shift+D).
80-
At the top of the debug panel you have to select the `Extension` option from the dropdown menu if you want to run the extension (or you have to select the `Extension Test` if you want to run the unit tests).
81-
After you selected the `Extension` option you can start the debug session by pressing the `F5` key or click on the green triangle shaped button next to the dropdown menu.
82-
This debug session will open up a new VSCode (Extension host) where our extension is installed and available.
83-
84-
**Note:** When the extension host window is opened you do not have to rebuild the project if you make any changes on the code because vscode will automatically do that, the only thing you have to do is restart the main debug session in the main vscode window by hit the restart button in the debug action bar or press the Ctrl+Shift+F5 key combination.
85-
8637
# How to use
87-
After the extension is running in the extension host window you have to open (or create a new) project folder where you have to define a `launch.json` configuration file inside the `.vscode` folder. In case of IoT.js Debug this configuration looks like this:
38+
You have to open (or create a new) project folder where you have to define a `launch.json` configuration file inside the `.vscode` folder. In case of IoT.js Debug this configuration looks like this:
8839

8940
```json
9041
{
@@ -98,7 +49,7 @@ After the extension is running in the extension host window you have to open (or
9849
"port": 5001,
9950
"localRoot": "${workspaceRoot}",
10051
"stopOnEntry": false,
101-
"debugLog": true
52+
"debugLog": 0
10253
},
10354
]
10455
}

0 commit comments

Comments
 (0)