fltk-rs VS slint

I have added a tile example to the repo, it's based on the FLTK example.

fltk-accesskit is an accesskit integration crate for fltk-rs, the gui crate. It's implemented as an external crate to allow for more experimentation before stabilizing the api, especially since fltk is at version 1.4.

fltk-rs worked well for me, for a small app.

Gtk doesn’t require you to write xml, you can write your gui code in Rust. You also have https://github.com/fltk-rs/fltk-rs

Currently, I have narrowed potential libraries to: 1. Flutter 2. FLTK 3. Relm (GTK) 4. iced 5. Slint 6. Imgui, Imgui-rs 7. and gtk-rs

FLTK

The fltk-rs library provides Rust bindings for the FLTK toolkit. The fltk-rs crate supports old architecture with more than 80 customizable widgets and more than four supported theme schemes, including the GTK scheme. You can also use the fltk-theme crate for more customizations.

A friend of mine grew tired of plotting libraries that did not allow adding data points to his plot interactively like you can in Matlab, so he wrote one using FLTK using C++. I refactored his code a bit and then ported to Rust using the fltk-rs crate. Recently I needed this library for a project and I noticed I had not made it publicly available on Github. So I present to you the fltk-plot library!

fltk-rs is a Rust bindings crate for FLTK, the cross-platfrom & lightweight gui library.

Besides GTK I can recommend FLTK. It has been around for a long time and is very stable.

> I wonder if someone could make a decent cross-platform GUI toolkit to save us from the horribly slow Electron-hell we've carved out for ourselves.

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

There are a bunch of new native UI toolkit as well, such as Slint [https://slint.dev]

While I welcome new cross-platform GUI Frameworks, I wonder why not use a declarative UI similar to QML? Even Slint[1] (which is built in Rust) uses such syntax for its UI.

[1] https://slint.dev

If you want to use Rust, Slint[0] may be something to consider, seeing as the existing bindings for Qt and QML are not very pleasing to use (mostly talking about qmetaobject-rs and cxx-qt). If I'm not mistaken, Slint is developed by ex-QML people.

[0]: https://slint.dev

Yes, we'd like to improve on that: https://github.com/slint-ui/slint/issues/4128

I've implemented a LSP server (for Slint - https://slint.dev) and I agree with this article.

The paradox is that it was meant to avoid to write language support for each editor. Yet, if you want to support vscode you must create a specific extension for it and can't just have a language client.

The article mention the configuration problem, but I'd add the problem that Microsoft refuses to specify a way for the server to tell the client what are the config options so that the client can show some kind UI showing the possible configuration options with a description of what they do. https://github.com/microsoft/language-server-protocol/issues...

I've been enjoying Slint[0] lately. It is inspired by QML but is entirely implemented in Rust. From what I understand, it also transpiles the .slint files into Rust.

[0]: https://slint.dev

I'm working on a GUI toolkit that should match the requirements: Slint - https://slint.dev

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

Disclaimer: I work for Slint