Evan Almloff

> @ealmloff Are you interested in contributing a new implementation? I would be happy to, but before I implement anything sledgehammer-bindgen is a bit different from the original sledgehammer library....

We were just discussing embedding Blitz (Dioxus' WGPU renderer) into other windows and game engines (specifically bevy) on discord ([here](https://discord.com/channels/899851952891002890/954257659597553664/1084891398358175865)). Currently this is not possible, but it would definitely be...

Wry recently added support for embedding a webview into a raw window including a wgpu window: https://github.com/tauri-apps/wry/blob/dev/examples/wgpu.rs. Using that example to build support into dioxus would be much easier than...

It would be great to get an example showing how to export your Dioxus component as a web component. You could use existing libraries like [webcomponent](https://lib.rs/crates/webcomponent), or [custom-elements](https://github.com/gbj/custom-elements) to register...

[dioxus-web-component](https://github.com/ilaborie/dioxus-web-component) seems like a really good community solution to exporting web components from dioxus

An automated tool for tracking breaking changes would be great! > Another thing that could be useful, though is more of a procedural improvement, is to establish milestone integration branches....

> > Who handles fixing conflicts in bug PRs: the person who filed the PR or the maintainers? > > Do you mean conflicts that bug PRs introduce into new...

Overall I think if the automation is good enough, the release branch approach is worth trying. @jkelleyrtp I know you have looked into automatically tracking breaking changes before a release....

We can try this on the main repo. A major flaw with not merging everything until before a release is there are a lot less people testing the new features....

That could be part of the solution. The other half of the solution would be automatically detecting PRs that will require a major version bump. We also release a lot...