druid

One of the best cross-platform open source projects I've seen so far is https://makepad.nl. - wasm source takes around 2 MB - loads up quickly and it is fast even in mobile browsers - great codebase! - compiles in under a minute (41s on my laptop) inspite being written in Rust Still needs a lot of work to be usable: - missing UI features like proper layouting, configurability etc. - imo font rendering still needs a lot of work; but there are already project in rust which do font rendering right, for instance: (git clone github.com/linebender/druid && cd druid && cargo run --release --example=text) - no animated transitions of UI components Makepad doesn't strive to be UI toolkit, but judging by the way it works already and dedication of the founders it looks really promising.

Iced https://github.com/hecrj/iced and Druid https://github.com/linebender/druid Iced is taking the "get something working now" approach, whereas Druid is taking the longer term "build it right" approach. I wouldn't recommend either of them for serious projects yet though. I would also recommend Raph Levien's blog https://raphlinus.github.io/.

On keyboard handling, https://github.com/linebender/druid/issues/1040 is the main tracking issue. That references a number of PR's, of which 1049 is the core of the platform keyboard handling. I'd be very pleased for other people doing this (including winit) to use this as a model, as a fair amount of study went into getting it right, especially on Windows. Regarding IME, we haven't done it yet (we're trying to be fairly conservative in our roadmapping), but we plan to wire up actual composition regions and so on, and hope to plumb IME to it using a cross-platform abstraction. My understanding of the winit code is that it varies a lot from platform to platform, but seems to mostly be synthesizing keyboard events (ReceivedCharacter) when an IME request such as "insertText" happens.

This is a very complicated issue. You can read our reasoning at the time in https://github.com/linebender/druid/issues/16 Since then, I've both regretted the fact that we're duplicating work, and been happy that we've been able to move more nimbly than we would if we were dragging the rest of the winit userbase along. A recent example of that is keyboard handling, and I'm expecting a similar situation soon with IME, as we'll want to handle that very differently than winit's current implementation. Take a look at our CI for the testing story. We have some tests, but they're mostly for platform-independent logic; we don't run a lot of platform specific code in CI. That said, Rust's type system is strong enough to catch a lot of potential breakage at compile time. Other than that, people tend to notice broken things pretty quickly. So overal

Indeed, however I think we might replace Go with any programming language and your comment will still make sense. Currently, web-browsers are the best have-it-all platforms, and outside web-technologies there isn't many good alternatives. We landed in 2020 and we don't have any complete, native-like, cross-platform GUI toolkit (if we skip Qt and GTK). In last years a lot projects have appeared, which were trying to compete in GUI toolkit market share. All of them had its scope limited, however they brought quite fresh look on declarative programming interface [0][1], superb 2D rendering pipeline [2][3], ease of embedding [4] and adaption to low-power devices [5] but none of them is "complete". Personally, I am amazed of the implementation of rxi/lite [6], which is just an app (C with Lua) based on SDL2 library. It uses 2x less RAM than s

Neat! I was just about to need something like this, for building native app bundles for druid[1]. I'll open an issue, but do you have any interest in exposing this as a library? [1] https://github.com/xi-editor/druid

Hello, I'm Ankur! I've spent the last 8 years building frontend applications with a variety of tech, from modern-day React to jQuery and DOM soup in the Olden Days. While the bulk of my professional experience is with front-end development, I'm currently trying to transition into a role that involves primarily working with Rust. I've spent the last three months on a sabbatical where I've been experimenting with the language and contributing patches to an open-source GUI toolkit called Druid (https://github.com/xi-editor/druid), still in the early stages of development. I'm most interested in a role where I can build web APIs and network services with Rust, but I'm open to other roles as well. While my experience with Rust is limited, I'm a quick learner who can rapidly come up to speed with unfamiliar concepts and new codebases. I've spen