Let's see if a vim browser is possible with #servo and #iced_rs 👀

I think I've been sleeping on #iced_rs -- It's nice to see a lot of good work has been done on developing a rust native GUI toolkit.

Now there just needs to be more GUI apps made with libcosmic/icedrs.

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

#nlnet #iced_rs #rust #rustlang #cjk #inputmethod

Report cursor size to input method by dcz-self · Pull Request #2918 · iced-rs/iced

This is a follow-up to https://discourse.iced.rs/t/better-input-method-suport-on-wayland/973 . The input method may place a popup with suggestions on the screen. For this, it needs to know the area...

GitHub

#rustyscript #iced_rs #tokio #rustlang #rust

(I don't thing switching to future or another lib would change much, but if you think I'm wrong please explain)

So...

You might have read me tell you about how I was... not having a great time trying to make #rustyscript and #iced_rs work well together and failing....

Specifically I couldn't find a way to stop the execution of a script. (I have script with long pauses waiting for stuff to happen IRL, and when the script is wrong, having to either close the application or wait until the end of the script is not great).

Turns out... I can't do that. Either because rustyscript's "load_modules" or "eval" can't be cancelled... Or maybe because a function I declare for the runtime use a blocking operation.

I still have some tests to do, but more to the point I need to really up my #tokio game.

#rustlang #rust

I mean there are probably difficult threading stuff happening in both iced-rs and rustyscript...

And I'm trying to tie them up with tokio, maybe adding a level of complexity...

Still, I don't think this needs be such a headhache.
I'm not even sure who to ask for help at this point.

#rust #iced_rs #rustyscript

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...

#rust #iced_rs #rustyscript #rustlang

Text seems to work, and the analytical AA was trivial to implement (just smooth-step the opacity value based on your distance at the edges).

I'm currently playing around with the borders by exaggerating them. Those big borders look kinda cute 🥺 .

#iced #rustlang #rust #iced_rs #vulkan #marpii

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 #rustlang #iced #iced_rs #vulkan #vulkanapi #marpii

#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.