Re: [Edbrowse-dev] parser separation

[Adam Thompson <arthompson1990@gmail.com>]

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

On Sun, Aug 30, 2015 at 08:21:07AM -0400, Karl Dahlke wrote:
> > Still not sold on hubbub.
> 
> Oh I'm not either, not at all,
> just like I'm not sold on v8 -
> but encapsulating things in separate sourcefiles gives us options,
> and flexibility, and sometimes leads to a better design.
> I'll get started on this today.

Agreed, one of the things I'd like to do is decouple the parsing logic from js
value creation and property setting.
The two are semantically different operations,
and the js stuff shouldn't be done if js is disabled anyway.
The DOM, when created, needs to know about js stuff,
though Ideally I'm aiming for an api which exposes our DOM to js without creating js
objects for everything and then syncing things around.
I'm not sure exactly how this would work,
but I don't want to have to reparse everything multiple times for the sake of
js object creation, or have the parser creating js objects in its node tree.

> And I agree we don't have to build a fully functional node right now,
> but there are I suspect a few things we'll need to add to take advantage of tidy.
> More on this later.

Indeed, that makes sense.

Cheers,
Adam.

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