[enhancement] consume upstream webview
See original GitHub issueI know that this has been discussed before, but I think it is time to revisit it for a couple reasons.
First of all, there is now activity again at: https://github.com/zserge/webview/tree/webview-x
I think that it would be beneficial for the entire community if the enhancements made here were pushed back upstream.
Second - at tauri we have the need to enable other languages (like python, nim, go and others) to consume the underlying webview codebase. The way that boscop/web-view
is structured at the moment makes that challenging, because of the way that the upstream source has been embedded. Basically non-rust consumers of tauri will need to pull in a rust crate / git repo to get the headers etc. in order to stay in lockstep with our api - which we for obvious reasons can’t allow to use two diverging sources.
One solution might be to use a flag in the consuming Cargo.toml that allows a user of boscop/web-view
to pull the source from some / any other place…
Thoughts?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:8 (4 by maintainers)
I was more keen to go in a more rusty direction, meaning I would like to slowly port the c/c++ code to Rust and maybe provide c bindings. I think the safety that Rust would provide in this case would be beneficial for bindings created for other languages, since anything can bind to c. What do you think?
There hasn’t been any more talk about an org, the only discussion about this can be read here: https://github.com/Boscop/web-view/issues/64