From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] edbrowse-js back in the fold??
Date: Tue, 29 Sep 2015 04:16:18 -0400 [thread overview]
Message-ID: <20150829041618.eklhad@comcast.net> (raw)
In-Reply-To: <20150929072512.GU2254@toaster.adamthompson.me.uk>
> Any progress with looking into duktape?
As per duktape, you may want to simply "look around" / research,
rather than diving in with both feet and translating jseng-moz.cpp.
I say this because that process is changing a lot, more than I thought.
I've already discussed the reformulation of innerHTML and document.write,
with new hooks to tidy parsing and tree formulation and tree decoration,
but beyond this there are more native functions that I first thought.
This is what Adam predicted quite some time ago.
I mean there aren't tons of them, but more than I thought.
So it is in a bit of flux at the moment; it should settle down
to stability again in a month or so.
Karl Dahlke
prev parent reply other threads:[~2015-09-29 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-26 14:05 Karl Dahlke
2015-09-28 4:42 ` Adam Thompson
2015-09-28 15:20 ` Chris Brannon
2015-09-28 17:28 ` Karl Dahlke
2015-09-29 7:25 ` Adam Thompson
2015-09-29 8:16 ` Karl Dahlke [this message]
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=20150829041618.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.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.
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 NNTP newsgroup(s).