unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: emacs-devel@gnu.org
Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>
Subject: DOM manipulation functions
Date: Sun, 23 Nov 2014 16:18:24 +0100	[thread overview]
Message-ID: <m3ppcedjy7.fsf@stories.gnus.org> (raw)

As part of the TLS management thing, it was suggested that Emacs display
visually certificate fingerprints:

http://sebsauvage.net/wiki/doku.php?id=php:vizhash_gd

I've started looking into this, and it seems like this would be really
easy to implement as SVG images -- SVG provides all the primitives
vizhash needs.

SVG is basically an XML DOM, and while constructing these it would be a
lot easier if Emacs had a DOM manipulation library.

So here's my two questions:

1) Would it be OK if I added a DOM manipulation/searching library to
Emacs?

2) Due to stupidity on my part I disregarded Chong's advice on how to do
the DOM manipulation things in shr.el, so we now basically have two DOMs
in Emacs -- the xml.el one and the one that shr uses.

I think it would be a good idea if I rewrote shr.el to just use the
xml.el DOM, like Chong said back then.  This will break any third-party
code that relies on shr internals, though.

So: New dom.el, and rewrite shr/eww to depend on dom.el.

Stefan, does this sound OK to you?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





             reply	other threads:[~2014-11-23 15:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-23 15:18 Lars Magne Ingebrigtsen [this message]
2014-11-23 15:58 ` DOM manipulation functions joakim
2014-11-23 15:59 ` Rüdiger Sonderfeld
2014-11-23 16:01   ` Lars Magne Ingebrigtsen
2014-11-23 16:52     ` Steinar Bang
2014-11-24  0:26   ` Leo Liu
2014-11-25  9:12     ` mapping data formats imported from C libraries (was: DOM manipulation functions) Ted Zlatanov
2014-11-25 15:54       ` mapping data formats imported from C libraries Lars Magne Ingebrigtsen
2014-11-25 16:27         ` Ted Zlatanov
2014-11-25 16:32           ` Lars Magne Ingebrigtsen
2014-11-25 16:40             ` Ted Zlatanov
2014-11-25 17:06               ` Lars Magne Ingebrigtsen
2014-11-26 10:41                 ` Steinar Bang
2014-11-26 15:51                   ` Lars Magne Ingebrigtsen
2014-11-26 19:57                     ` Steinar Bang
2014-11-26 20:00                       ` Lars Magne Ingebrigtsen
2014-11-26 12:59                 ` Ted Zlatanov
2014-11-26 15:56                   ` Lars Magne Ingebrigtsen
2014-11-26 16:48                     ` Ted Zlatanov
2014-11-23 18:45 ` DOM manipulation functions raman
2014-11-25 11:01 ` Nicolas Richard
2014-11-26 18:44 ` Lars Magne Ingebrigtsen
2014-11-26 19:42   ` Ted Zlatanov
2014-11-26 19:44     ` Lars Magne Ingebrigtsen

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=m3ppcedjy7.fsf@stories.gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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).