madnirua

LibrePCB is revamping their UI with Slint to deliver a sleek, modern experience for their open-source EDA tool. In their latest blog post, they share a preview of LibrePCB 2.0’s new UI and the story behind migrating their 10+ year old Qt C++ codebase to Rust + Slint.

We’re proud to announce Slint 1.13. Now with Live-Preview for Rust & C++, an outline panel, menu improvements, better gradients, and more.

Read the full release blog: https://slint.dev/blog/slint-1.13-released

tl;dr

- Add 3D graphics with new WGPU support (works with Bevy). - Build Rust UIs for iPhone & iPad. - Import Figma design tokens into your app. - Smarter live preview & debug console

Did you get a chance to check https://slint.dev?

Disclaimer: I work for Slint

Based on the discussion with our community, we added a clause in our CLA - https://cla-assistant.io/slint-ui/slint - to ensure that Slint will always be made available under an open source license as well as a royalty-free license.

"We believe that open-source software development and communities are the foundation for a healthy ecosystem of high-quality software, where everyone can learn, improve and give back. We commit to upholding this foundation and pledge by promising to continue to develop Slint in the open under an open-source license compliant with the Open Source Definition.

Further, we commit to provide a royalty-free license for those who develop desktop or web applications and do not want to use open-source components under copyleft licenses."

For non-commercial and personal projects, the runtime licenses are free.

For commercial projects, the online form https://slint.dev/get-price (from https://slint.dev/pricing page) automatically sends an email with pricing info (no marketing person is involved :) ). Note: you need to enter your business email in the form.

You are right. The Qt backend is optional.

Slint (https://slint.dev) is an open source declarative GUI toolkit to create elegant, modern, and native GUI for embedded, desktop, and web applications. One of the USPs of Slint is that it supports multiple programming languages such as C++, Rust, and JavaScript. Recently, one of the Slint community members added support for C#. Check out Matheus' YouTube video where he walks through the demo applications -- https://www.youtube.com/watch?v=EwLFhk5RUwE

Link to blog: https://microhobby.com.br/blog/2023/09/27/creating-user-inte... GitHub repo: https://github.com/microhobby/slint-dotnet

Star Slint on GitHub: https://github.com/slint-ui/slint/

Let us know what you think. Thanks.

We changed the term from "User" to "Seat" and added an entry in the FAQ section to avoid confusion.

We plan to add a pricing calculator later, replacing “Call us for pricing “

Thanks :)

For the short term, we have an example that some of our community users and commercial customers a using to build their custom virtual keyboard

https://github.com/slint-ui/slint/blob/master/examples/virtu...

Qt is only needed if you want native looking widgets. Otherwise, another style will be used for widget, which does not look native. In the future, we plan to have native backend using the native API, which will allow native widgets without using Qt.

Reference: https://github.com/slint-ui/slint/blob/master/docs/install_q...

Thanks for the feedback. We will try to get some designers to improve the widget gallery examples.

Here is the correct link

https://slint.dev/releases/1.0.2/docs/node/

Thanks for reporting. Will fix that.

We investigated integration VxWorks as part of a customer request and we concluded that all the required hooks exist to support Slint.

Not sure why or who downvoted.

We will add more detailed comparison in our documentation. Thanks.

A user is a person (eg. a developer or a designer etc.) using Slint to build the GUI.

Thanks.. This is a nice reference for an onboarding guide.. We could add a similar section to our documentation page https://slint.dev/docs

Thanks :)

Since Qt is a much broader toolkit, we are considering of writing dedicated blogs to do an objective comparison between the two toolkits on the GUI part only.

Probably because we are using HTML and CSS instead of Slint :)

Jokes aside .. which browser and device combo are you using.. We can adjust the css accordingly. Thanks.

Just a nice co-incidence :)

The toolkit was initially named SixtyFPS and was renamed to Slint last year --https://slint.dev/blog/sixtyfps-becomes-slint

The name comes from our design goals - Straightforward, Lightweight, Intuitive, Native Toolkit.

Thanks.. Probably we should name our major releases after some of the band's titles :)

Disclaimer: I work for Slint

I suppose you are referring to the "Embedded Add-on per application" pricing? At least the non-commercial use is hopefully clear :)

Yes, we need find a better way to show the pricing there since it's dependent on 2 variables - volume and type of embedded system. Maybe some sort of a online calculator?

Disclaimer: I work for Slint

Indeed we are actively working on all of those topics:

Accessibility support in Slint is improving. We just merged the initial AccessKit integration into our winit backend -- https://github.com/slint-ui/slint/pull/2865

IDE integration - our VSCode extension is pretty stable these days (https://slint.dev/get-started#vscode) and we also support integrating into other IDEs via LSP (https://slint.dev/get-started#other-ide)

Graphical tooling for UI/UX designers - our current prototype https://slintpad.com needs more work to become an easy Drag n'Drop editor for UI/UX designers -- but we are on the right path to achieve that :)

Disclaimer: I work for Slint

Thanks. We have a lot of users who are migrating from Qt/QML to Slint.

The smooth scrolling part -- is that for the wasm binary or for a native application?

Slint is a declarative GUI toolkit to build native user interfaces (native as opposed to web-based). Spurred by the positive response we received after the 1.0 release, we'd like to open up the licensing options and we'd love to get your feedback.