Slint is an open-source declarative GUI toolkit to build native user interfaces for Rust, C++, JavaScript, or Python apps.
Find a file
2022-02-18 12:24:35 +01:00
.cargo Update copyright information to reflect name change 2022-02-09 10:27:47 +01:00
.github/workflows CI: Prospective fix for the cpp test building with the native style 2022-02-15 11:43:30 +01:00
.reuse janitor: Prospective fix for reuse CI check 2022-02-17 14:59:51 +01:00
.vscode Move resources to the website repo 2020-11-25 11:56:10 +01:00
api Begin rasterizing glyphs for glyph embedding 2022-02-15 15:52:24 +01:00
cmake Update copyright information to reflect name change 2022-02-09 10:27:47 +01:00
docker Update copyright information to reflect name change 2022-02-09 10:27:47 +01:00
docs Simplify a bit the test dependencies 2022-02-15 10:47:58 +01:00
examples Update cargo-ui URL 2022-02-10 20:37:18 +01:00
helper_crates Fix LICENSES symlinks 2022-02-09 17:05:47 +01:00
internal fix slint_debug_property cfg build 2022-02-18 12:24:35 +01:00
LICENSES Fix linking to the FAQ in the commercial LicenseRef 2022-02-10 21:00:31 +01:00
logo Add missing icon update 2022-02-08 11:14:37 +01:00
scripts Fix the feature name in the build script 2022-02-10 09:13:17 +01:00
tests Fix the inliner thinking property are not modified when they are 2022-02-17 16:25:48 +01:00
tools LSP docs: explain how to show the preview from kate 2022-02-17 08:37:06 +01:00
vscode_extension Bump version number to 0.2.1 2022-02-10 16:25:28 +01:00
xtask janitor: Fix ci 2022-02-17 14:20:46 +01:00
.clang-format Reformat public header with Qt's clang-format 2020-05-11 15:20:17 +02:00
.gitattributes Add a .gitattributes to rust diff looks better 2020-12-08 16:40:55 +01:00
.gitignore Clean up generated C++ include directory handling 2021-09-18 07:32:53 +02:00
.mailmap Add a .mailmap to unify our email addresses 2022-02-17 08:54:46 +01:00
.pre-commit-config.yaml Add .pre-commit-config.yaml 2021-08-17 22:38:16 +02:00
Cargo.toml Update copyright information to reflect name change 2022-02-09 10:27:47 +01:00
CHANGELOG.md ChangeLog: Fix typo in links 2022-02-09 14:02:11 +01:00
CMakeLists.txt Update copyright information to reflect name change 2022-02-09 10:27:47 +01:00
CONTRIBUTING.md A few occurence of sixtyfps less 2022-02-09 13:32:17 +01:00
Cross.toml Update copyright information to reflect name change 2022-02-09 10:27:47 +01:00
cspell.json Add slint to cspell 2022-02-02 16:26:18 +01:00
FAQ.md Remove broken link from FAQ.md 2022-02-11 07:14:17 +01:00
LICENSE.md Update copyright information to reflect name change 2022-02-09 10:27:47 +01:00
README.md Upate the links to the templates repository 2022-02-09 15:49:18 +01:00
rustfmt.toml Initial commit laying out the structure 2020-05-04 10:49:58 +02:00

Slint

Formerly known as

Build Status Discussions

Slint is a toolkit to efficiently develop fluid graphical user interfaces for any display: embedded devices and desktop applications. We support multiple programming languages, such as Rust, C++, and JavaScript.

Our design goals are:

  • Lightweight: Fit into a few hundred kilobytes of RAM and require little processing power.
  • Straightforward: Programmers and designers should feel productive and be able to enjoy the design and development process. The APIs should be consistent, easy to use, and intuitive, no matter the target language. High-quality documentation should describe the APIs, teach concepts and how to use them.
  • Native: We support many different target platforms, from embedded devices to desktops including mobile and web. Both the user and the developer should feel at home on each platform. The look and feel and experience should match the users' expectations of a native application.

Current Status

Slint is in active development. Its state of development depends on the kind of application.

  • Embedded: Ready! Slint is already happily used by customers on embedded devices (running on an Arm processor with Linux). We are also looking into supporting microcontrollers.
  • Desktop: In Progress. Slint is usable on Windows, Linux and Mac. We plan on building up the desktop support in subsequent releases to reach the level of integration we're aiming for.
  • Mobile (Android/iOS): Todo. We haven't started supporting mobile platforms yet, but it is our intention to do so in the future.
  • Web: Our focus is on Embedded and Desktop applications. We do not intend to compete in the web space as a primary platform. That said, Slint can compile to WebAssembly and the demos are running in a web browser. But the web support is currently limited to demo purposes.

Documentation

Refer to the README of each language directory in the api sub-folder:

The examples folder contains examples and demos. The docs folder contains build instructions and internal developer docs.

Demos running in WebAssembly Simulation

Click on the screenshots to run the WebAssembly simulation

Printer Demo Slide Puzzle Todo Widget Gallery
Screenshot of the Printer Demo Screenshot of the Slide Puzzle Screenshot of the Todo Demo Screenshot of the Gallery Demo

Desktop Native Widgets

Windows macOS Linux
Screenshot of the Gallery on Windows Screenshot of the Gallery on macOS Screenshot of the Gallery on Linux

The .slint Markup Language

Slint comes with a markup language that is specifically designed for user interfaces. This language provides a powerful way to describe graphical elements, their placement, and the flow of data through the different states. It is a familiar syntax to describe the hierarchy of elements and property bindings. Here's the obligatory "Hello World":

HelloWorld := Window {
    width: 400px;
    height: 400px;

    Text {
       y: parent.width / 2;
       x: parent.x + 200px;
       text: "Hello, world";
       color: blue;
    }
}

Check out the language reference for more details.

Architecture

An application is composed of the business logic written in Rust, C++, or JavaScript and the .slint user interface design markup, which is compiled to native code.

Architecture Overview

Compiler

The .slint files are compiled ahead of time. The expressions in the .slint are pure functions that the compiler can optimize. For example, the compiler could choose to "inline" properties and remove those that are constant or unchanged. In the future we hope to improve rendering time on low end devices by pre-processing images and text. The compiler could determine that a Text or an Image element is always on top of another Image in the same location. Consequently both elements could be rendered ahead of time into a single element, thus cutting down on rendering time.

The compiler uses the typical compiler phases of lexing, parsing, optimization, and finally code generation. It provides different back-ends for code generation in the target language. The C++ code generator produces a C++ header file, the Rust generator produces Rust code, and so on. An interpreter for dynamic languages is also included.

Runtime

The runtime library consists of an engine that supports properties declared in the .slint language. Components with their elements, items, and properties are laid out in a single memory region, to reduce memory allocations.

Rendering backends and styles are configurable at compile time. Current there are two back-ends:

  • The gl backend uses OpenGL ES 2.0 for rendering.
  • The qt backend uses Qt's QStyle to achieve native looking widgets. In the future it could also use QPainter.

Tooling

We have a few tools to help with the development of .slint files:

  • A LSP Server that adds things like auto-complete and live preview of the .slint files to many editors
  • It is bundled in a Visual Studio Code Extension accessible from the market place
  • A slint-viewer tool which display the .slint files. With the --auto-reload argument, makes it easy to preview your UI as you are working it (when using the LSP preview is not possible)
  • An online editor to try out .slint syntax without installing anything (sources)
  • An updater to convert the .slint files from previous version to the newer version
  • An experimental Figma importer

Contributions

We welcome your contributions: in the form of code, bug reports or feedback.

  • If you see an RFC tag on an issue, feel free to chime in.
  • For contribution guidelines see CONTRIBUTING.md. The dual-licensing requires the contributor to accept a CLA.

License

This software is provided under a dual licensing scheme:

See also the Licensing FAQ

Frequently Asked Questions

Please see our separate FAQ.

About us

Olivier and Simon started their open source journey in the KDE project, the popular Open Source Desktop Environment for Linux. Later they met while working together in a small company in Norway called Trolltech, on the Qt C++ toolkit. Here, they gained valuable experience in API design, cross-platform software development and user interface components. Simon continued in the Qt Company as one lead developer and maintainer of the QtQml engine, while Olivier co-founded Woboq, a software consulting company. Years later, and now based in Berlin, they are starting a new project. With Slint they aim to make developing user interfaces fun for everyone: from JavaScript, C++, or Rust developers all the way to UI/UX designers.

Contact us

Feel free to join Github discussions for general chat or questions. Use Github issues to report public suggestions or bugs.

To contact us privately send an email to info@slint-ui.com

For chat, we also have our Mattermost instance