language-servers/slint
1
0
Fork 0
mirror of https://github.com/slint-ui/slint.git synced 2025-10-01 06:11:16 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 5
slint/vscode_extension
History
Olivier Goffart d7e59e881f VSCode extension: add a way to restart the server
2021-04-07 18:17:03 +02:00
..
.vscode Generate the vscode extension with the wizard 2020-12-23 15:15:53 +01:00
src VSCode extension: add a way to restart the server 2021-04-07 18:17:03 +02:00
.eslintrc.json Generate the vscode extension with the wizard 2020-12-23 15:15:53 +01:00
build_lsp.sh Try to avoid doing cross builds on Linux 2021-04-01 12:57:01 +02:00
package.json VSCode extension: add a way to restart the server 2021-04-07 18:17:03 +02:00
README.md Add a features section in the README of the VSCode extension 2021-04-07 13:40:39 +02:00
sixtyfps.tmLanguage.json Rename "signal" to "callback" 2020-12-18 09:51:01 +01:00
tsconfig.json Generate the vscode extension with the wizard 2020-12-23 15:15:53 +01:00
vsc-extension-quickstart.md Generate the vscode extension with the wizard 2020-12-23 15:15:53 +01:00

README.md

sixtyfps-vscode README

Extension for VSCode which include syntax coloration and a way to start the LSP server

Features

  • Syntax highlighting
  • Diagnostics from .60 files
  • Live Preview of a .60 file
  • Jump to definition (currently, only definition of Component)

Setup

  1. Build the LSP
cargo build --bin sixtyfps-lsp
  1. run npm install in the vscode directory
cd vscode_extension
npm install

How to run the LSP

At the moment you need to load this directory in VS code and then start debugging (Run -> Start Debugging). That will "debug" the vs code extension and create a new VS code window. The LSP server binary will be started if previously built You can see the output in the output pane "SixtyFPS LSP" (that's the drop-down that usually shows "Tasks").

How to build the extension package

To create a .vsix package:

  1. Install vsce (via npm for example).
  2. Change to the vscode_extension sub-directory.
  3. Install the dependencies: npm install.
  4. Build the lsp binaries: npm compile-lsp.
  5. Run vsce package to create the extension package.