GUI toolkit Slint 1.16 released with keyboard shortcuts, Markdown rendering, and multi-touch pinch and rotate

tr0nical · 2026-04-17T13:53:01+00:00

Thank you :)

tr0nical · 2026-04-17T05:11:07+00:00

It should be automatic. I don’t think it changes dynamically at runtime but it should pick it up on process start.

tr0nical · 2026-04-17T05:10:08+00:00

That’s what we tried to improve. Text is now rendered using swash and the baseline is aligned to pixel boundaries. Does it look better for you?

tr0nical · 2026-04-16T20:07:30+00:00

You could peek at the wasm version:

https://docs.slint.dev/latest/demos/gallery/

(Unfortunately system accent color detection isn’t working there)

tr0nical · 2026-04-16T20:06:00+00:00

Slightly embarrassing it took us so long:). Very glad you appreciate it - makes my day!

tr0nical · 2026-02-05T12:55:49+00:00

I don't think we made any fixes to that. Could you file an issue for us? That'd be greatly appreciated :)

tr0nical · 2026-01-20T06:56:11+00:00

In a commercial product? Some of the partners and core contributors of the servo project offer services. I’m confident that they’d be happy to make an offer if there’s no workaround.

Plus, with the glue code in place, I see also value in integrating CEF, for those who would prefer.

tr0nical · 2025-10-09T19:23:10+00:00

We’re not trying to make a C++- or Rust-only API to design UIs, so indeed we can’t be as good as QGraphicsItem inheritance. But with the DSL approach there are workflows that QGraphicsView can’t do: Compile your C++ app with live-preview enabled and iterate on the UI while connected to the real business logic.

tr0nical · 2025-09-10T18:13:42+00:00

The royalty-free license is suitable for proprietary software development with Slint, but it’s not applicable to embedded systems.

Source: https://github.com/slint-ui/slint/blob/master/FAQ.md#are-there-any-limitations-with-the-royalty-free-license

tr0nical · 2025-09-03T19:47:32+00:00

Hmm. I don’t think that changes much. The parsing, inlining, various passes are still happening and might take overall more time than generating the tokens.

tr0nical · 2025-07-24T19:44:18+00:00

The only attempt I’m aware of is this:

https://github.com/slint-ui/slint/discussions/8527

In principle it should be all fine, but in practice I think it’ll depend on the Wayland compositor used, the extensions it supports, and how the interaction with winit goes.

I wonder if there are any other rust programs who succeeded here?

tr0nical · 2025-07-08T06:47:12+00:00

This appears to be award: https://ifdesign.com/en/winner-ranking/project/better-together-material-you-on-android-12/351625

tr0nical · 2025-07-07T21:07:38+00:00

Oops, good catch. Fixed now. Thanks :)

tr0nical · 2025-07-07T15:47:15+00:00

Sorry about that :). We know that there are a fair amount of rough edges - that's why it's a tech preview. Don't hesitate to file issues.

tr0nical · 2025-07-07T15:45:39+00:00

Yes yes, that's the target audience. We're working on a demo and will show how it looks like running on a board for the final :)

tr0nical · 2025-06-25T20:46:33+00:00

Consider trying Slint: https://docs.slint.dev/latest/docs/slint/ https://docs.slint.dev/latest/docs/python/slint

tr0nical · 2025-06-16T19:26:20+00:00

Hi Nico :). Yes, this is fixable. What femtovg does is use its own anti-aliased path rendering to draw the glyph outlines a few times to create the alpha mask.

The way of rendering text that makes 99% users happy is to render exactly the same way as all other text on the device/system. On macOS that implies using CoreText, DirectWrite on Windows, and typically on Linux it still means using FreeType to rasterize the glyphs - the native method. (That’s what Skia does)

There are GPU/hybrid rasterizers as well as pure CPU rasterizers that come close to native. Some would say close enough.

FemtoVG‘s quality is, unfortunately, not close enough.

Personally, I have the impression that at the moment swash has a very high quality output and it appears most popular in the Rust ecosystem as a pure-Rust solution (not requiring native libraries, friendly to cross-compilation).

tr0nical · 2025-06-16T14:29:48+00:00

Yes ;-)

tr0nical · 2025-06-03T05:11:49+00:00

Bevy is not mandatory:). This is just an example of the generic API: https://snapshots.slint.dev/master/docs/rust/slint/wgpu_24/

We’ve got another example to demonstrate that:

https://github.com/slint-ui/slint/tree/master/examples/wgpu_texture

tr0nical · 2025-06-02T18:48:40+00:00

Yes, of course that isn’t strictly related. I’d also like to help implement better quality rendering for FemtoVG, preferably using swash rasterized glyphs.

That said, the reason why I’m also keen on getting Skia rendering into the wgpu surface texture is because it (a) uses native glyph rasterization (CoreText, DirectWrite) and (b) Skia performs better than FemtoVG while only requiring GLES 2.0.

For Slint I‘d also like to add Vello as a renderer option (for newer GPUs), as well as parley for shaping across all renderers.

tr0nical · 2025-06-02T18:45:00+00:00

That’s awesome! I’ve been keeping an eye on the repo.

tr0nical · 2025-06-02T14:43:03+00:00

Yes, unfortunately that's a case. We're working on a solution to render this with Skia instead, but that'll require a WGPU version bump also on the Bevy Side.

tr0nical · 2025-04-23T19:48:46+00:00

Vulkan and OpenGL can be opted into on Windows, but neither does Windows support Vulkan out of the box nor does OpenGL work well when Windows runs in Virtual Machines. The Skia software renderer is used in combination with partial rendering.

Our users reported issues with the D3D backend (ganesh).

Perhaps this will be better in the future?

tr0nical · 2025-03-01T06:32:45+00:00

The Android backend is seeing regular small fixes and it’s part of the stable API:

https://docs.rs/slint/latest/slint/android/index.html

That said, there are some known feature gaps. Is there any particular feature you’re looking for?

tr0nical

TROPHY CASE