madmaxio

Thank you, that's very interesting.

Seems true, if someone is also interested in wider writing support, please share ideas or examples for implementation.

I'm also interested in reader, any plans for it in the future or it will stay in current state?

Soory for such a late reply, check please this code for the idea of what I'm trying to do (it won't compile, it's the ideal scenario for web application workflow):...

For client handler overwrite build_request: fn build_request(&mut self, url: &url::Url) -> ws::Result { let mut req = Request::from_url(url)?; req.headers_mut().push(("TheHeader".into(), "That's it".into())); Ok(req) } For server I think you can do...

After implemeting this, I'm also very interested in implementing optimized DOM updates similar style to Yew framework (update DOM partially instead of full page). If someone is also interested in...

let uv_color: Vec4 = texture.sample(*sampler, in_uv); | ---- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `glam::Vec4`, found `spirv_std::glam::Vec4` And so on. Just noticed glam default features message at the start.

I'm on windows 11 with stable rust.

PS C:\src\.external\renderling\crates\example> cargo run warning: C:\src\.external\renderling\crates\renderling-gpui\Cargo.toml: `default-features` is ignored for glam, since `default-features` was not specified for `workspace.dependencies.glam`, this could become a hard error in the future warning: C:\src\.external\renderling\crates\renderling\Cargo.toml: `default-features`...

Are you on the same branch? I just do simple steps: 1. clone repository 2. go to crates/example 3. cargo run Does this build for you?