Risultati di ricerca
Slint, the declarative GUI toolkit for Rust, C++, JavaScript, and Python. Build elegant, modern, stylish, native GUIs for Embedded, Desktop, and Web. Complete your UI design through quick iterations using Live Preview.
- Use Cases
Enjoy the freedom to configure your embedded device as per...
- Pricing
All individual users of Slint associated with the designing,...
- Community
We commit to upholding this foundation and pledge by...
- Blog
Slint 1.5: Embracing Android, Improving Live-Preview, and...
- Get Started
Start with SlintPad. SlintPad is our web based editor when...
- Supported Boards
Supported Boards. Filter content by. All Espressif Infineon...
- Chat
Non è possibile visualizzare una descrizione perché il sito...
- LVGL
Slint uses a declarative Domain Specific Language (DSL) to...
- Use Cases
- Overview
- Current Status
- Get Started
- Architecture
- License
- Contributions
- About us (SixtyFPS GmbH)
•Scalable: Slint should support responsive UI design, allow cross-platform usage across operating systems and processor architectures and support multiple programming languages.
•Lightweight: Slint should require minimal resources, in terms of memory and processing power, and yet deliver a smooth, smartphone-like user experience on any device.
•Intuitive: Designers and developers should feel productive while enjoying the GUI design and development process. The design creation tools should be intuitive to use for the designers. Similarly for the developers, the APIs should be consistent and easy to use, no matter which programming language they choose.
•Native: GUI built with Slint should match the end users' expectations of a native application irrespective of the platform - desktop, mobile, web or embedded system. The UI design should be compiled to machine code and provide flexibility that only a native application can offer: Access full operating system APIs, utilize all CPU and GPU cores, connect to any peripheral.
We invite you to use Slint and be part of its community.
Visit #MadeWithSlint to view some of the projects using Slint and join us in the Slint community.
Slint is in active development. The state of support for each platform is as follows:
•Embedded: Ready. Slint is being used by customers in production on embedded devices running embedded Linux and Windows. The Slint run-time requires less than 300KiB of RAM and can run on different processor architectures such as ARM Cortex M, ESP32, STM32 from the MCU category to ARM Cortex A, Intel x86 from the MPU category.
•Desktop: In Progress. While Slint is a good fit on Windows, Linux and Mac, we are working on improving the platform support in subsequent releases.
•Web: In Progress. Slint apps can be compiled to WebAssembly and can run in a web browser. As there are many other web frameworks, the web platform is not one of our primary target platforms. The web support is currently limited to demo purposes.
•Mobile
•Android: In Progress. Track the progress of work here #46.
Hello World
The UI is defined in a Domain Specific Language that is declarative, easy to use, intuitive, and provides a powerful way to describe graphical elements, their placement, their hierarchy, property bindings, and the flow of data through the different states. Here's the obligatory "Hello World":
Documentation
For more details, check out the Slint Language Documentation. The examples folder contains examples and demos, showing how to use the Slint markup language and how to interact with a Slint user interface from supported programming languages. The docs folder contains a lot more information, including build instructions, and internal developer docs. Refer to the README of each language directory in the api folder: •C++ (Documentation | Tutorial | Getting Started Template) •Rust (Documentation | Tutorial | Tutorial Video | Getting Started Template) •JavaScript/NodeJS (Beta) (Documentation | Tutorial | Getting Started Template)
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: •The femtovg renderer uses OpenGL ES 2.0 for rendering. •The skia renderer uses Skia for rendering. •The software renderer uses the CPU with no additional dependencies. NOTE: When Qt is installed on the system, the qt style becomes available, using Qt's QStyle to achieve native looking widgets.
Tooling
We have a few tools to help with the development of .slint files: •A LSP Server that adds features like auto-complete and live preview of the .slint files to many editors. •It is bundled in a Visual Studio Code Extension available from the market place. •A slint-viewer tool which displays the .slint files. The --auto-reload argument makes it easy to preview your UI while you are working on it (when using the LSP preview is not possible). •SlintPad, an online editor to try out .slint syntax without installing anything (sources). •An updater to convert the .slint files from previous versions to newer versions. •An experimental Figma importer. Please check our Editors README for tips on how to configure your favorite editor to work well with Slint.
You can use Slint under any of the following licenses, at your choice:
1.Royalty-free license,
2.GNU GPLv3,
3.Paid license.
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.
We are passionate about software - API design, cross-platform software development and user interface components. Our aim is to make developing user interfaces fun for everyone: from JavaScript, C++, or Rust developers all the way to UI/UX designers. We believe that software grows organically and keeping it open source is the best way to sustain th...
Start with SlintPad. SlintPad is our web based editor when you can try out Slint. It comes preloaded with some of our demos that should help you get started easily. Use it along with the Slint Documentation to design your first UI. Open SlintPad.
Gli Slint sono stati una rock band statunitense, in attività dal 1986 al 1992. Nonostante l'esigua discografia prodotta e lo scarso successo commerciale, sono considerati una delle band più influenti di fine anni ottanta ed inizio anni novanta oltre che tra le più grandi band nella storia del rock. Sono spesso categorizzati come ...
The Slint for Visual Studio Code Extension. As a Software Developer, integrating Slint into a new or existing code base, choose one of these languages to get started: C++. Rust. JavaScript. Next. Supported Platforms. Previous.
13 mag 2024 · Slint for Python Alpha Packages. Add Slint to your Python project without compilation, by installing our binary packages for Windows, macOS, and Linux: pip install slint. Thanks to feedback from the community, we've also improved our API to load .slint files.
Slint on Microcontrollers. How to use this crate: Designs of user interfaces are described in the .slint design markup language. There are three ways of including them in Rust: The .slint code is inline in a macro. The .slint code in external files compiled with build.rs.
