From: Gavin Smith <gavinsmith0123@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
"Ludovic Courtès" <ludo@gnu.org>, P <pronaip@protonmail.com>,
Texinfo <bug-texinfo@gnu.org>
Subject: Re: Any interest in using HTML for locally-installed Texinfo documentation?
Date: Tue, 15 Oct 2019 22:00:50 +0100 [thread overview]
Message-ID: <20191015210050.GB22658@mintstar> (raw)
In-Reply-To: <935f0a37-8c59-2877-989c-aa47e6478611@bothner.com>
On Tue, Oct 15, 2019 at 01:40:17PM -0700, Per Bothner wrote:
> On 10/15/19 1:20 PM, P wrote:
> > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > On Tuesday, October 15, 2019 7:27 PM, Gavin Smith <gavinsmith0123@gmail.com> wrote:
> > > WebKitGTK seemed to be the best option for a lightweight embedded
> > > web-browser. I looked into other options, such as the Gecko engine
> > > used inside Thunderbird, but apparently it is not supported any more
> > > to embed it in other programs. WebKitGTK allowed access to the DOM
> > > tree of the documents without the complication of communicating with
> > > embedded JavaScript, as was needed with QtWebEngine.
> > >
> >
> > Out of curiosity, have you looked at smaller browser engines, such as Dillo or Netsurf?
>
> Dillo does not support JavaScript or frames, which would seem to preclude
> (or at least complicate) the kind of functionality we are hoping for.
JavaScript should not be necessary if there is DOM access from the C/C++
side, as the case with WebKitGTK (although it is not as easy as it could
be). Frames should not be necessary either: for a table of contents
side bar, I imagine this would be done as a widget outside of the
embedded browser.
next prev parent reply other threads:[~2019-10-15 21:00 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 12:55 Any interest in using HTML for locally-installed Texinfo documentation? Gavin Smith
2019-04-01 14:01 ` sirgazil
2019-04-02 9:37 ` Ludovic Courtès
2019-04-02 15:02 ` Gavin Smith
2019-04-02 16:46 ` Per Bothner
2019-04-07 16:28 ` Gavin Smith
2019-04-08 15:12 ` Ludovic Courtès
2019-04-08 15:39 ` Pierre Neidhardt
2019-04-08 23:46 ` Gavin Smith
2019-04-09 6:25 ` Eli Zaretskii
2019-04-13 16:21 ` Gavin Smith
2019-04-14 19:25 ` Pronaip
2019-10-15 19:27 ` Gavin Smith
2019-10-15 20:20 ` P
2019-10-15 20:35 ` Gavin Smith
2019-10-15 20:40 ` Per Bothner
2019-10-15 21:00 ` Gavin Smith [this message]
2019-10-15 21:09 ` Per Bothner
2019-10-15 21:30 ` Gavin Smith
2019-10-16 1:39 ` Ricardo Wurmus
2019-10-19 20:31 ` Ludovic Courtès
2019-10-22 19:00 ` Gavin Smith
2019-10-22 20:18 ` Gavin Smith
2019-11-03 14:04 ` Ludovic Courtès
2019-11-03 15:37 ` Gavin Smith
2019-11-06 21:49 ` Ludovic Courtès
2019-04-03 21:21 ` Ludovic Courtès
2019-04-04 10:33 ` Gavin Smith
2019-04-02 15:31 ` Per Bothner
2019-04-03 21:11 ` Ludovic Courtès
2019-04-03 22:44 ` Per Bothner
2019-04-04 10:23 ` Gavin Smith
2019-04-04 16:02 ` Ludovic Courtès
2019-04-02 20:12 ` Ricardo Wurmus
2019-04-02 20:27 ` Ricardo Wurmus
2019-04-02 22:58 ` sirgazil
2019-04-02 22:10 ` Per Bothner
2019-04-02 23:09 ` sirgazil
2019-04-03 8:43 ` Gavin Smith
2019-04-03 14:23 ` sirgazil
2019-04-03 14:40 ` Per Bothner
2019-04-03 14:49 ` Ricardo Wurmus
2019-04-02 21:02 ` George Clemmer
2019-04-07 11:08 ` Gavin Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191015210050.GB22658@mintstar \
--to=gavinsmith0123@gmail.com \
--cc=bug-texinfo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=per@bothner.com \
--cc=pronaip@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).