From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Paul Michael Reilly Newsgroups: gmane.emacs.devel Subject: Re: Emacs in a Chrome Tab? (related to NaCl Support for Emacs discussion) Date: Tue, 10 Jan 2012 02:11:47 -0500 Message-ID: References: <87boqc1t51.fsf@gmail.com> <054F6D14-733F-4F22-A4F2-6AF1189D13A0@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=f46d04462f887b1eb704b6273a62 X-Trace: dough.gmane.org 1326179522 7467 80.91.229.12 (10 Jan 2012 07:12:02 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 10 Jan 2012 07:12:02 +0000 (UTC) Cc: emacs-devel@gnu.org To: chad Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 10 08:11:58 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RkVsA-0004Ab-DC for ged-emacs-devel@m.gmane.org; Tue, 10 Jan 2012 08:11:54 +0100 Original-Received: from localhost ([::1]:58828 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RkVs9-0002Y6-Ni for ged-emacs-devel@m.gmane.org; Tue, 10 Jan 2012 02:11:53 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:39817) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RkVs6-0002XD-61 for emacs-devel@gnu.org; Tue, 10 Jan 2012 02:11:51 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RkVs5-0008LH-3w for emacs-devel@gnu.org; Tue, 10 Jan 2012 02:11:50 -0500 Original-Received: from mail-tul01m020-f169.google.com ([209.85.214.169]:65100) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RkVs4-0008LD-Rh for emacs-devel@gnu.org; Tue, 10 Jan 2012 02:11:49 -0500 Original-Received: by obcwo8 with SMTP id wo8so6075432obc.0 for ; Mon, 09 Jan 2012 23:11:48 -0800 (PST) Original-Received: by 10.182.226.6 with SMTP id ro6mr17385016obc.3.1326179507969; Mon, 09 Jan 2012 23:11:47 -0800 (PST) Original-Received: by 10.182.147.37 with HTTP; Mon, 9 Jan 2012 23:11:47 -0800 (PST) In-Reply-To: <054F6D14-733F-4F22-A4F2-6AF1189D13A0@gmail.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 209.85.214.169 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:147549 Archived-At: --f46d04462f887b1eb704b6273a62 Content-Type: text/plain; charset=ISO-8859-1 Chad, this is an excellent reply. Thanks, -pmr On Mon, Jan 9, 2012 at 5:42 PM, chad wrote: > NativeClient is mostly about using the local processor to cut out server > round-trips for computations. Unfortunately for your idea, it doesn't > address the idea of the display engine; native client nexe's are expected > to use the browser's ui. There is some experimental 3D support for nexe's > via their alternative to NSAPI, but this is far enough away from Emacs that > a port would be complex. For your goals, I'd guess that xembed (ala the > xembed branch) is an easier practical path to a prototype. > > This idea, like Tom Tromey's `rebase emacs on Common Lisp', Steve's `Emacs > in JavaScript', and the various Guilemacs attempts point out (yet again) > something I would not have guessed when I started with emacs ~22 years ago: > while the most technically valuable piece of Emacs (aside from its freedom) > is the extensive libraries of elisp code, the most critical piece is > actually the display engine. It's very hard to move Emacs anywhere that > the display engine won't go, and it seems to be very hard to move the > display engine. > > *Chad > > P.S. This makes the herculean efforts of things like epoch, multi-tty, and > bidi all the more impressive. Thanks again to all the wonderful emacs > hackers out there. --f46d04462f887b1eb704b6273a62 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Chad, this is an excellent reply. =A0Thanks,

-pmr
On Mon, Jan 9, 2012 at 5:42 PM, chad <yandros@gmail.com>= wrote:
NativeClient is mostly about using the local= processor to cut out server round-trips for computations. =A0Unfortunately= for your idea, it doesn't address the idea of the display engine; nati= ve client nexe's are expected to use the browser's ui. =A0There is = some experimental 3D support for nexe's via their alternative to NSAPI,= but this is far enough away from Emacs that a port would be complex. =A0Fo= r your goals, I'd guess that xembed (ala the xembed branch) is an easie= r practical path to a prototype.

This idea, like Tom Tromey's `rebase emacs on Common Lisp', Steve&#= 39;s `Emacs in JavaScript', and the various Guilemacs attempts point ou= t (yet again) something I would not have guessed when I started with emacs = ~22 years ago: while the most technically valuable piece of Emacs (aside fr= om its freedom) is the extensive libraries of elisp code, the most critical= piece is actually the display engine. =A0It's very hard to move Emacs = anywhere that the display engine won't go, and it seems to be very hard= to move the display engine.

*Chad

P.S. This makes the herculean efforts of things like epoch, multi-tty, and = bidi all the more impressive. =A0Thanks again to all the wonderful emacs ha= ckers out there.

--f46d04462f887b1eb704b6273a62--