edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] V 3.5.4
Date: Tue, 12 May 2015 08:32:15 +0100	[thread overview]
Message-ID: <20150512073215.GF2917@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20150411192321.eklhad@comcast.net>

[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]

On Mon, May 11, 2015 at 07:23:21PM -0400, Karl Dahlke wrote:
> > I guess with tidy5 we'll be wanting to go for 3.6 as the next release
> 
> I don't have strong feelings about this; whatever you and Chris think.

I'd go for 3.6 if given the choice, making 3.5.4 (the currently being worked on release) the last release in the 3.5 series.

> > I'm also thinking we should get a stabilised tidy5 based html parser before
> > we start playing with pulling the DOM into a separate process?
> 
> Yes, and definitely yes.
> Don't move all the chess pieces at once.
> And it really will bring benefit: more web pages parsed properly,
> all the nodes building js objects not just some of them,
> all the html attributes becoming members in the corresponding js nodes
> not just some of them, etc etc.

Yes definitely.

> > Next on my edbrowse todo list is to evaluate how ready the duktape js engine is
> 
> A good trial is to
> cp jseng-moz.cpp jseng-duk.c
> and then modify the latter to use the duktape engine calls
> and ideally we could just plug either one into edbrowse and they should
> both work the same.
> Good side by side comparisons.

Yeah that's the plan. It'll also be a good test of how adaptable the protocol
between edbrowse and edbrowse-js is in terms of passing around memory 
addresses etc.

> I wanted to do the same with v8 but never got round to it,
> and the v8 interface isn't as easy as I had hoped.
> I never even got hello world to run
> or even compile: js_hello_v8.cpp

Indeed, I'm thinking that v8 really isn't an option here.

Cheers,
Adam.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-05-12  7:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-10 23:37 Karl Dahlke
2015-05-11  0:37 ` chris
2015-05-11  0:54   ` Karl Dahlke
2015-05-11 22:41   ` Adam Thompson
2015-05-11 23:23     ` Karl Dahlke
2015-05-12  7:32       ` Adam Thompson [this message]
2015-05-12  9:15         ` Karl Dahlke
2015-05-13  7:17           ` Adam Thompson
2015-05-13  8:16             ` Karl Dahlke
2015-05-13 13:15             ` Karl Dahlke
2015-05-14  7:03               ` Adam Thompson
2015-05-12  8:07       ` chris

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=20150512073215.GF2917@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    /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).