Hello,
Gavin Smith <gavinsmith0...@gmail.com> skribis:
> On Tue, Apr 02, 2019 at 09:46:05AM -0700, Per Bothner wrote:
>> Both Electron and QtWebEngine have mechanisms for communicating between
>> the "browser" window and the main application, which is not sandboxed.
>> (For QtWebEngine the main application is regular non-sandboxed C++ code.)
>> For a desktop browser like Firefox, one could pass important environment
>> variables in the URL. For bi-directional communication between a
>> sandboxed desktop browser and the C/C++ wrapper program one can always
>> use WebSockets or XmlHttpRequest ("AJAX").
>
> I've started work on a documentation browser using QtWebEngine. The
> work can be seen in the qt-info branch of the Texinfo Git repository:
>
> http://git.savannah.gnu.org/cgit/texinfo.git/tree/js/docbrowser?h=qt-info
Neat!
>From a “social” viewpoint, I think WebKitGTK would be more appropriate,
GTK+/GNOME being affiliated with GNU.
Also, QtWebEngine relies on bits of Chromium, which is a real challenge
from a software freedom viewpoint and from a security viewpoint, to the
point that we ended up removing it from our Qt builds in Guix:
https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/qt.scm#n143
https://lists.gnu.org/archive/html/guix-devel/2015-06/msg00302.html
Regardless, thanks for moving forward!
Ludo’.
