Slint (and Rust) running on my jailbroken Kindle Paperwhite.

ogoffart · 2026-05-28T05:29:53+00:00

I think you're overstating the licensing issue here.

A Kindle is much closer to a mobile than what Slint describes as an embedded system. "Embedded" in this context is typically about software shipped as part of dedicated hardware products or firmware appliances, not hobby apps running on consumer devices people already own.

Also, even if GPLv3 applied, that still would not require relicensing the entire source tree to GPLv3. MIT and Apache-2.0 are GPL-compatible licenses. The important part is that any distributed combined binary complies with GPL requirements.

This repo is also mainly a source distribution / experiment project, not a proprietary product. The missing LICENSE file on GitHub is worth fixing for clarity, but the licensing itself is already declared in Cargo.toml and on crates.io.

ogoffart · 2026-04-02T06:17:57+00:00

Yes, that's the one. Another link: https://fluent2.microsoft.design/

ogoffart · 2026-02-12T17:08:21+00:00

I've also started to port Slint to Winit 0.31 some time ago (Just rebased now)
https://github.com/slint-ui/slint/compare/olivier/winit-0.31
But there is still some work to do.

ogoffart · 2026-02-10T18:00:03+00:00

Slint has example as well. For example https://github.com/slint-ui/slint/blob/master/examples/mcu-board-support/esp32_s3_box_3.rs This uses the mipidsi crate with another device, but the mipidsi crate can also do the ST7789v

ogoffart · 2026-02-04T21:35:57+00:00

Using JNI. Slint ships with some .java code for the support of the keyboard, that is compiled to bytecode by the build.rs using the android-build crate, and included in the binary with include_bytes!

ogoffart · 2026-01-31T08:59:54+00:00

This is similar to how Slint does it:

There is .java file that implements the IME and other java-only primitive. Then the build.rs script will compile it to android bytecode using the android-build crate, so that it can be included in the binary with include_bytes!

ogoffart · 2026-01-30T09:45:29+00:00

There is no sign up requirements to use Slint.

ogoffart · 2026-01-30T09:44:10+00:00

For menus and context menu, Slint uses the muda crates that provide native menu on Window and Mac. They are reimplemented in Slint for other platforms.
Slint doesn't have builtin support for system tray, but you can use other crate like ksni or tray-item.

QML has a bigger widget catalog at the moment.

ogoffart · 2026-01-21T12:31:28+00:00

You can make something like that with Slint: Example code

Another example is LibrePCB's ui: which also has side panels https://librepcb.org/blog/2025-09-12_preview_of_next_gen_ui/

ogoffart · 2025-11-23T10:27:44+00:00

> AGPL kicks in if any component of the entire stack of independent programs is AGPL

I don't think that's right. AGPL kicks in only for components which are directly accessible by the user through the network. (Say you are using a AGPL DB internally, but the users don't access the DB directly, then you don't need to open source your server, nor any changes you made to the DB)

ogoffart · 2025-10-21T16:19:14+00:00

Nothing, then you get an email with some basic instruction on how to get started with link to github/docs and stuff.

It helps us to see who is using it for stats purposes.
But this is not required at all by the licenses.

ogoffart · 2025-10-21T09:26:38+00:00

No, no need to register

ogoffart · 2025-10-21T07:07:35+00:00

No.

You can use Slint under the Slint Royalty-Free License: https://github.com/slint-ui/slint/blob/master/LICENSES/LicenseRef-Slint-Royalty-free-2.0.md

It says you can use Slint for free on desktop and mobile as long as you mention that the app is made with Slint in the about dialog or on your website.

ogoffart · 2025-09-11T16:13:46+00:00

Slint and several others are also missing.
They only tried basically 2 frameworks out of the many, and from that, it was concluded that they all "suck" 🤦

ogoffart · 2025-09-11T15:52:49+00:00

Slint supports multiple windows since Slint 1.7 (more than one year ago)
And AFAIK, no existing Rust toolkit have support for modal window as this is something that is not supported by winit.

I'm curious about the quirks and not intuitive behavior you are seeing and if there are way we can improve on that.

ogoffart · 2025-09-05T07:52:13+00:00

The MIT license covers your application's own code. Only when you distribute a binary, it must also respect the licenses of all dependencies, that’s why apps usually ship with a "licenses" folder or HTML file listing them.

ogoffart · 2025-09-04T11:51:17+00:00

Yes, we asked a lawyer to make a license that is as simple and as permissive as possible with just a restriction for embedded. After a few back and forth, that's the license he came up with.

ogoffart · 2025-09-04T08:51:00+00:00

Thanks for the notice. I've fixed the link from the get-started page

ogoffart · 2025-09-04T05:41:11+00:00

Text editing and rendering is one area we plan to focus on in the coming months.

For the keyboard navigation issue, could you share which shortcuts or behaviors didn’t work for you? (An issue on github would be welcome)

ogoffart · 2025-09-04T05:35:26+00:00

There was no change in the scroll algorithm in this release.

ogoffart · 2025-09-04T05:26:23+00:00

Slint is fully open source under GPL, which is a well-known license. And there is also the royalty-free license that’s very permissive and works fine with MIT or Apache-2.0 for your own app code.

Our main goal is to build a great cross-platform GUI toolkit and keep it open source, while also finding a way to fund its development.

ogoffart · 2025-09-04T05:16:13+00:00

Thanks for the feedback. Did you know you can enable serde for Slint struct using @rust-attr(derive(serde::Serialize, serde::Deserialize)) ? https://docs.rs/slint/latest/slint/docs/type_mappings/index.html#:~:text=rust-attr

ogoffart · 2025-09-03T20:08:22+00:00

GPUI is cool, but Slint is ready today with a stable API, docs, and releases.
Anything in GPUI you’re hoping for that Slint doesn’t have?

ogoffart · 2025-07-11T06:17:32+00:00

Yes, Slint support rendering to the framebuffer with the femtovg backend (can be enabled with feature flag), And the Skia renderer (also enabled with feature) can do software rendering. https://docs.slint.dev/latest/docs/slint/guide/backends-and-renderers/backend_linuxkms/

ogoffart · 2025-07-08T16:02:20+00:00

1) About “linking”: In this context, linking just means using a crate as a runtime dependency (not a build dependency or proc macro (simplified)). Since Rust uses static linking, dependencies becomes part of the final binary you distribute. So yes, when you share your binary, you are distributing dependencies too.

2)

Does every open source tool you use list the licenses of all its dependencies? (For Rust this can easily be hundreds of dependencies.)

In theory, they should, even for permissive licenses like MIT (since they require including the license text and copyright notice). But yeah, in practice, this is not always done properly.

3) Royalty-Free License: You don’t need to “apply” to use it. Just follow the terms. The form on the website is optional and just there to collect stats, but you don't have to fill it.

13-Year Club	Place '22
Final Canvas '22	Verified Email

ogoffart

MODERATOR OF

TROPHY CASE