From: chad <yandros@gmail.com>
To: Paul Michael Reilly <pmr@pajato.com>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs in a Chrome Tab? (related to NaCl Support for Emacs discussion)
Date: Mon, 9 Jan 2012 14:42:07 -0800 [thread overview]
Message-ID: <054F6D14-733F-4F22-A4F2-6AF1189D13A0@gmail.com> (raw)
In-Reply-To: <CAGwjgEhn53rauR4A80zAXBMDcgH42n+_bUomLKDS9N1z6cVpkQ@mail.gmail.com>
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.
next prev parent reply other threads:[~2012-01-09 22:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 20:41 Emacs in a Chrome Tab? (related to NaCl Support for Emacs discussion) Paul Michael Reilly
2012-01-09 21:08 ` Antoine Levitt
2012-01-09 21:56 ` Paul Michael Reilly
2012-01-09 22:42 ` chad [this message]
2012-01-10 7:11 ` Paul Michael Reilly
2012-01-09 23:26 ` Antoine Levitt
2012-01-10 7:19 ` Paul Michael Reilly
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=054F6D14-733F-4F22-A4F2-6AF1189D13A0@gmail.com \
--to=yandros@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=pmr@pajato.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.