Iced is the clear number one for me, too. The only thing I'd love to see officially supported in iced in the future is mobile apps. But it looks like that ain't gonna happen anytime soon (with the most recent PRs getting rejected once again).

Have a question, what is the best way to detect if a `text_input` is focused?

Not exactly what you asked, but I recently answered a very similar question on StackOverflow: https://stackoverflow.com/questions/79345013/how-to-focus-te...

Yes, not what I want :-).

I can focus just fine. I want to detect if a text_input is focused, when I am checking key-presses.

But going through every discussion and all, there was a PR that might have allowed to do this, and it's been merged, but it's not working the way I want.

My use case is, If the text_input is not focused, I can press characters to perform some operations. If text_input is selected, it should be ignored.

For now I am back using modifiers, will get back to this later.

The only things I don't like about this is a) your binaries will become huge and very slow to compile with optimizations enabled and b) it's dependence on GPUI and its unsure future direction (I'd like to see GPUI thrive outside of Zed but the maintainers have clarified that that's not the goal for now).

Isn't pure CPU rendering possible in iced with the tiny-skia backend?

Maybe... Is this framebuffer? My platform is pretty unusual (riscv64-musl), so I was pretty happy when something was working.

If your interested, it is a portable audio player with the size of the iPod Nano 7g:

https://github.com/nanowave-player/nanowave-ui

You might need to modify it slightly to get it to render to the right location, but it's a pure software renderer. You could ask in the Iced zulip https://iced.zulipchat.com/

Cool stuff. Have you tried https://github.com/embedded-graphics/embedded-graphics ?

The Rust Community is working on gcc-rs for this very reason.

gcc-rs is far from being usable. If you want to use Rust with gcc-only targets you're probably better off with rustc_codegen_gcc instead.

One could also compile to wasm, and then convert that wasm to C.

It sounds convenient %)

There are some new interesting developments though: https://github.com/gfx-rs/wgpu/pull/8217 Just sadly not in the spec as mentioned.

The text in the last survey question (target platform) seems wrong (or the graphic is wrong).

Yes, I agree it’s mostly tools...