3 ms·
the core is https://github.com/webview/webview https://github.com/webview/webview with its rust binding, electron binds chromium and nodejs, I don't really know
by ausjke 6y ago
the core is https://github.com/webview/webview https://github.com/webview/webview with its rust binding, electron binds chromium and nodejs, I don't really know how webview works, a thin cross-platform API wrapper layer on top of native browser engine for each OS, so that you leverage the pre-installed browser in the OS and use it kind of like a shared library to minimize the app size?
electron always bundles the whole chromium into its binary, what is exactly "webview" comparing to chromium inside electron app?
- ausjke 6y agohttps://webkitgtk.org/ https://webkitgtk.org/ is what webview uses on Linux, this is gnome's own web engine and has nothing to do with chromium engine, so webview leverages similar web libraries to do the native GUI then.
- monocasa 6y agoI wouldn't say it had nothing to do with chromium; chromium's blink engineer is a fork of webkit.
- ComputerGuru 6y agoIt's not gnome's own engine at all, it's the forked-a-long-time-ago from KDE's KHTML, adopted by Apple and significantly improved internally under the WebCore project/framework with changes shared from time to time with KDE devs before it was hard-forked as webkit and developed more in the open, then adopted by Chrome/Chromium (before Google hard-forked and renamed it to blink), with gnomifications for integrations and wrappers for the GTK userland.
- baxrob 6y agoI think this is the clearest explanation of the current webview implementation: https://github.com/webview/webview/issues/305 https://github.com/webview/webview/issues/305
- abeltensor 6y agoYou are pretty much on the spot, its a library that directly interfaces with the existing browser engines on the user's computer.