From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] a JS centric design
Date: Sat, 07 Nov 2015 17:35:29 -0500 [thread overview]
Message-ID: <20151007173529.eklhad@comcast.net> (raw)
In-Reply-To: <87611d4fep.fsf@mushroom.localdomain>
> if we could come up with a native DOM that wasn't tied to an engine,
> it would be even better. So where do we start?
Actually we've made more strides in this direction than you might realize.
Fold all the js engine specific code into one file, currently jseng-moz.cpp.
Make an api that talks to that file, currently implemented in ebjs.[ch].
Keep a lot of the DOM functionality on this side of that API, decorate.c html.c.
All that was done in the past year.
Remember when js engine specific code was *everywhere*?
Sprinkled all over edbrowse?
That's one reason the moz upgrade was so horrible.
Remember how many JS AutoCompartment calls we use to have?
Now there are two.
And when we gathered that code together into one file it was at least
twice as big as it is now, having moved much of it to the other side.
So there is reason to believe we're gradually making sense of this.
Karl Dahlke
prev parent reply other threads:[~2015-11-07 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 19:51 Karl Dahlke
2015-11-07 16:13 ` Adam Thompson
2015-11-07 16:33 ` Karl Dahlke
2015-11-07 22:23 ` Chris Brannon
2015-11-07 22:35 ` 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=20151007173529.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).