On Tue, Feb 03, 2015 at 05:15:17PM -0500, Karl Dahlke wrote: > > if tidy5 builds as a library (I hope it does) > > then we build and install their code same as any other library. > > Sure, that makes sense. > So we'll see who has a chunk of time first to look into this.
I may have some time this weekend to have a look. > If said library swallows html and gives us a tree of nodes, should we: > > A) convert those nodes into the struct htmlTags we have today > and use most of our existing machinery, incremental, or > > b) follow that tree directly, build js nodes off of it, use those nodes, > don't use our structures any more, this more of a rewrite. > > I'm not expecting an answer, because we'd probably have to look > at the code, and library, and resulting tree to answer the question. > Just something to chew on. From what I've seen of tidy (based on the curl example code), I'd go for something between the two. Basically I'm thinking that our existing tag machinary needs work anyway, so we'd want to adapt it, but then we'd follow the tidy-generated tree, building our DOM based on that. We'd then have js hooks into our DOM which allow js to alter it since I suspect doing that with the tidy tree would be somewhat mor involved with the tidy code-base than we want to get. This also gives us greater flexibility in DOM implementation. Once js's finished with the DOM, we'd then render it. This logic would have to be repeated each time js alters things (with some optimisations) to ensure we get an accurate representation of what js's done to the page. On another DOM-related note, it seems that we probably need to move the contents of startwindow.js out of js and into our DOM implementation since DOM objects are supposed to be "host" objects rather than javascript objects as we're implementing them. This is another reason to get a fully functional c DOM implementation, since then we can plug in tidy5 to generate the initial structure and js to do its thing, whilst allowing the js stuff to be in c++ and the tidy5 stuff to be in whatever we need it to be. This isn't going to be incremental, but at some stage I think we need to just do it and stop making things "just work" for a few days until the next thing which "just doesn't work" pops up. Cheers, Adam.
signature.asc
Description: Digital signature
_______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
