From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: "Perry E. Metzger" Newsgroups: gmane.emacs.devel Subject: Re: fine grained control of webkit browsing Date: Tue, 19 Jun 2018 21:20:58 -0400 Message-ID: <20180619212058.35d08bc4@jabberwock.cb.piermont.com> References: <20180619114906.4437a1f6@jabberwock.cb.piermont.com> <87po0mvjes.fsf@elephly.net> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1529457594 28973 195.159.176.226 (20 Jun 2018 01:19:54 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 20 Jun 2018 01:19:54 +0000 (UTC) Cc: Ricardo Wurmus , emacs-devel@gnu.org To: Richard Stallman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 20 03:19:50 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fVRmn-0007PN-Cz for ged-emacs-devel@m.gmane.org; Wed, 20 Jun 2018 03:19:49 +0200 Original-Received: from localhost ([::1]:45610 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fVRou-0002WE-Mg for ged-emacs-devel@m.gmane.org; Tue, 19 Jun 2018 21:22:00 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38974) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fVRoJ-0002W6-ON for emacs-devel@gnu.org; Tue, 19 Jun 2018 21:21:24 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fVRoI-0007ro-TO for emacs-devel@gnu.org; Tue, 19 Jun 2018 21:21:23 -0400 Original-Received: from hacklheber.piermont.com ([2001:470:30:84:e276:63ff:fe62:3400]:57078) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fVRoI-0007rQ-Ob; Tue, 19 Jun 2018 21:21:22 -0400 Original-Received: from snark.cb.piermont.com (localhost [127.0.0.1]) by hacklheber.piermont.com (Postfix) with ESMTP id 5605E1AE; Tue, 19 Jun 2018 21:21:22 -0400 (EDT) Original-Received: from jabberwock.cb.piermont.com (jabberwock.cb.piermont.com [10.160.2.107]) by snark.cb.piermont.com (Postfix) with ESMTP id 343C32DEC84; Tue, 19 Jun 2018 21:21:22 -0400 (EDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2001:470:30:84:e276:63ff:fe62:3400 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:226545 Archived-At: On Tue, 19 Jun 2018 18:57:08 -0400 Richard Stallman 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