Project supported by @nlnet keeps going!

@iced

I took #iced in crosshairs and want to make it the best #GUI for #Wayland input methods.
If there's interest, of course.

First results:

https://github.com/iced-rs/iced/pull/2918

I'm yet again defeated by iced-rs and threads management...

What I want to do is let the application run a js script (for reasons) that can send tcp request to a device (again, for reasons). And I have this working. It's a bit of a mess but it works.

Only now I want to be able to stop the script (without alt-F4 the whole application) because the script can take some time to execute and it's annoying when there is an error in the script.

Only rustyscript doesn't have a mechanism for that, so right now I'm resorting to make a subscriber for the js execution. Which is a pain, but I think I more or less got it...

Except...

Working on an Iced renderer for my Vulkan layer "MarpII".

So far, I got the quad renderer working (including rounded corners). Batches of quads are also cached, so re-rendering the same layout doesn't cost that much.

#rust #iced_rs

So I think my fondamental problem with my code is that iced isn't concurrent the way I though it would be. The interface isn't updated while a task is performed. Which sucks, because I wanted to be able to launch a thing and then stop it.