From: "Perry E. Metzger" <perry@piermont.com>
To: Richard Stallman <rms@gnu.org>
Cc: Ricardo Wurmus <rekado@elephly.net>, emacs-devel@gnu.org
Subject: Re: fine grained control of webkit browsing
Date: Tue, 19 Jun 2018 21:20:58 -0400 [thread overview]
Message-ID: <20180619212058.35d08bc4@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <E1fVPYi-0001sf-Ht@fencepost.gnu.org>
On Tue, 19 Jun 2018 18:57:08 -0400 Richard Stallman <rms@gnu.org>
wrote:
> > The widget is not fully integrated into Emacs. The extent to
> > which one can conveniently communicate with the widget is by
> > sending a string containing a JavaScript program to the widget
> > and have it return a value.
>
> In what computer does that JavaScript program get executed?
Inside the same Emacs process on the same machine. WebKit is linked
in to Emacs and controls a window. JavaScript is being injected by
elisp into the WebKit instance to control it.
> Why use JavaScript here?
In the absence of having the full WebKit API exposed to the rest of
Emacs, it's the only obvious way to tell WebKit to do things like
scrolling the window. Yes, it's not really what you want, which is
what we are discussing. Ideally, the entirety of the WebKit API would
be exposed to the elisp layer and one could much more tightly
integrate the browser into the rest of the editor.
Perry
--
Perry E. Metzger perry@piermont.com
next prev parent reply other threads:[~2018-06-20 1:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 15:49 fine grained control of webkit browsing Perry E. Metzger
2018-06-19 16:19 ` Ricardo Wurmus
2018-06-19 16:37 ` Perry E. Metzger
2018-06-19 18:58 ` joakim
2018-06-19 20:51 ` Perry E. Metzger
2018-06-19 21:31 ` joakim
2018-06-20 0:19 ` T.V Raman
2018-06-19 22:57 ` Richard Stallman
2018-06-20 1:20 ` Perry E. Metzger [this message]
2018-06-20 23:26 ` Richard Stallman
2018-06-21 0:00 ` Perry E. Metzger
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180619212058.35d08bc4@jabberwock.cb.piermont.com \
--to=perry@piermont.com \
--cc=emacs-devel@gnu.org \
--cc=rekado@elephly.net \
--cc=rms@gnu.org \
/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/emacs.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).