slint/tools/lsp
Tobias Hunger c25d15c3d2 live-preview: Remember recent colors
... for the duration of the session. How can we save those
colors?

Recent colors change a lot, we probably do not want that stored
inside the git repository hosting the slint files... and this is
probably "personal data" and nor "project data" in the first place.
2025-05-22 15:30:30 +02:00
..
common Fix assert in LSP (SubElement != Component) when renaming properties 2025-05-06 21:31:24 +02:00
fmt chore: A few clippy fixes 2025-05-09 13:25:38 +02:00
language chore: A few clippy fixes 2025-05-09 13:25:38 +02:00
LICENSES Simplify commercial license (#3063) 2024-05-31 14:06:17 +02:00
preview live-preview: Remember recent colors 2025-05-22 15:30:30 +02:00
ui live-preview: Remember recent colors 2025-05-22 15:30:30 +02:00
build.rs Simplify commercial license (#3063) 2024-05-31 14:06:17 +02:00
Cargo.toml live_preview: Fuzzy-match palette entries 2025-05-22 09:46:30 +02:00
common.rs lsp: Move poll_once into common 2025-05-22 14:03:52 +02:00
fmt.rs Simplify commercial license (#3063) 2024-05-31 14:06:17 +02:00
language.rs Auto-fixed clippy::unnecessary_map_or 2025-02-07 09:02:31 +01:00
main.rs live-preview: Send telemetry to VSCode 2025-05-09 19:18:27 +02:00
preview.rs lsp: Move poll_once into common 2025-05-22 14:03:52 +02:00
README.md lsp: Document debian dependencies 2025-01-30 15:22:38 +01:00
util.rs chore: A few clippy fixes 2025-05-09 13:25:38 +02:00
wasm_main.rs live-preview: Send telemetry to VSCode 2025-05-09 19:18:27 +02:00

LSP (Language Server Protocol) Server for Slint

This directory contains the implementation of the LSP server for Slint featuring diagnostics, code completion, goto definition, and more importantly, live-preview

Generic usage

The LSP server consists of a binary, slint-lsp (or slint-lsp.exe on Windows). It provides all the functionality and allows any programming editor that also implements the standardized LSP protocol to communicate with it.

If you have Rust installed, you can install the binary by running the following command:

cargo install slint-lsp

This makes the latest released version available in $HOME/.cargo/bin. If you would like to try a development version, you can also point cargo install to the git repository: for the released version. Or, to install the development version:

cargo install slint-lsp --git https://github.com/slint-ui/slint --force

Alternatively, you can download one of our pre-built binaries for Linux or Windows:

  1. Open https://github.com/slint-ui/slint/releases
  2. Click on the latest release
  3. From "Assets" download either slint-lsp-linux.tar.gz for a Linux x86-64 binary or slint-lsp-windows.zip for a Windows x86-64 binary.
  4. Uncompress the downloaded archive into a location of your choice.

As the next step, configure your editor to use the binary, no arguments are required

Make sure the required dependencies are found. On Debian-like systems install them with the following command:

sudo apt install -y build-essential libx11-xcb1 libx11-dev libxcb1-dev libxkbcommon0 libinput10 libinput-dev libgbm1 libgbm-dev

Code formatting

The slint code formatting tool is part of the lsp. To learn how to use it as a standalone tool, see fmt README

Editor configuration

Please check the editors folder in the Slint repository for instructions on how to set up different editors to work with Slint.