slint/tools/lsp
Ashley 5c6f07da64
Move named color & color literal parsing to slint common (#9981)
* Move color_parsing to common

* [autofix.ci] apply automated fixes

* Fixes

* Change how feature flags work

* Use std feature for common in compiler

* Add color-parsing feature instead

---------

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2025-11-10 08:39:28 +00:00
..
common live-preview: add a callback to rename an element 2025-09-03 22:16:34 +02:00
fmt lsp: add format imports (#9707) 2025-10-13 10:44:28 +02:00
language lsp: add format imports (#9707) 2025-10-13 10:44:28 +02:00
LICENSES
preview Move named color & color literal parsing to slint common (#9981) 2025-11-10 08:39:28 +00:00
ui live-preview: Don't show reload icon on MacOS (#9807) 2025-10-21 13:03:52 +02:00
build.rs
Cargo.toml Move named color & color literal parsing to slint common (#9981) 2025-11-10 08:39:28 +00:00
common.rs lsp: No error when sending messages to the Preview fails 2025-09-10 19:35:47 +02:00
fmt.rs
language.rs Move named color & color literal parsing to slint common (#9981) 2025-11-10 08:39:28 +00:00
main.rs lsp: No error when sending messages to the Preview fails 2025-09-10 19:35:47 +02:00
preview.rs live-preview: account for transformation when highlighting items 2025-10-18 11:59:09 +02:00
README.md Zed extension: fix windows package name 2025-08-19 10:14:18 +02:00
util.rs Parse: accept changed callback without brace 2025-08-29 14:49:47 +02:00
wasm_main.rs lsp: No error when sending messages to the Preview fails 2025-09-10 19:35:47 +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-x86_64.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.