From: "ian.tegebo" <ian.tegebo@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Running WebKit browser in Emacs!
Date: Sat, 8 Mar 2014 11:31:23 -0800 (PST) [thread overview]
Message-ID: <77d0d759-0fd6-4b1a-8b4c-047e232f2398@googlegroups.com> (raw)
In-Reply-To: <mailman.16712.1394238253.10748.help-gnu-emacs@gnu.org>
On Friday, March 7, 2014 4:22:01 PM UTC-8, Daniel Hackney wrote:
> For another approach, see my old project Ezbl [1]. It used the XEmbed
And yet another,
http://www.emacswiki.org/emacs/eww
This approach is nice because it's pure elisp; the benefits could be manifold. On the one hand, it doesn't require a custom build.
On the other, I believe such an approach could be used to create graphical interfaces in Emacs for Emacs, e.g. Customize, but using the far more ubiquitous HTML/CSS languages as oppose to working directly with buffer/window/text-properties. Going further, js2-mode already has a fair bit of what's needed for an EMCAScript implementation. There's still a mountain of work to get through, but doing so would make Emacs even better for javascript development.
Currently, I suspect the difficulty of understanding the Emacs/Elisp interfaces and rendering model are why we don't see more ambitious graphical features from the community. To be clear, I'm not claiming that the Emacs/Elisp interfaces and rendering model *can* or *should* be simplified. That may or may not be so. My point is that many more people already understand the HTML/CSS interfaces and rendering model and that learning another is a significant barrier.
next parent reply other threads:[~2014-03-08 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.16712.1394238253.10748.help-gnu-emacs@gnu.org>
2014-03-08 19:31 ` ian.tegebo [this message]
2014-03-08 0:22 Running WebKit browser in Emacs! Daniel Hackney
-- strict thread matches above, loose matches on Subject: below --
2014-03-03 16:01 lazycat.manatee
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=77d0d759-0fd6-4b1a-8b4c-047e232f2398@googlegroups.com \
--to=ian.tegebo@gmail.com \
--cc=help-gnu-emacs@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 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.