Im trying to use iced for the gui in an audio plug in I’m building, but I keep seeing discrepancies in how to accomplish this.
On the iced github page, it says that to implement the Sandbox trait, you use this signature: fn view(&self), yet in the documentation it says to use view(&mut self). When I try to use the non-mut version, I get an error saying that it expects self to be mutable.
I also stumbled across iced-pure, which seems like a better idea. But I need to use a NumberInput widget from the iced-aw crate. Unfortunately, these widgets are not pure.
So how do I go about creating a gui using NumberInput? Do I need to create the widgets myself to make them pure? I’d like to use other widgets from the iced-aw crate too, so that wouldn’t be ideal
Or do i have to use the mutable version of view? If so, why does github say to use non mutable? Is this specific to certain versions of iced? If the newer version of iced uses a non mutable view function, does that mean it’s pure? Have the iced-pure changes been merged into iced?
I decided to give up. Iced just isn’t a mature enough gui framework and the alternatives don’t look great either.
I restarted my plug in project using JUCE tonight and I already have the gui started. It’s c++, so that sucks, but oh well
@Barbacamanitu @Solemarc
I’d like to hear your thoughts about Tauri and Dioxus.
I know react so Dioxus was easy for me to pick up. I haven’t tried tauri but I know React, Vue and Svelte pretty well so I assume I’d be golden with it as well
What GUI framework did you end up using in C++? Qt?
I started trying out JUCE. It’s a framework for making audio plugins (VSTs). Though I think I’m going to give the rust solution another shot with Vizia.
Vizia looks really nice, but the book only covers a counter example… Sadly, this is the state of most Rust GUI libraries at the moment…
Right? What’s with that? It’s like everyone gets their crate to the minimal working state and stops workings on it.