From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) by hurricane.the-brannons.com (Postfix) with ESMTPS id A35C621DE02 for ; Mon, 11 May 2015 16:23:14 -0700 (PDT) Received: from resomta-ch2-05v.sys.comcast.net ([69.252.207.101]) by resqmta-ch2-07v.sys.comcast.net with comcast id SnPB1q0022Bo0NV01nPM8E; Mon, 11 May 2015 23:23:21 +0000 Received: from eklhad ([IPv6:2601:4:5380:4ee:21e:4fff:fec2:a0f1]) by resomta-ch2-05v.sys.comcast.net with comcast id SnPM1q0055LMg2101nPMRJ; Mon, 11 May 2015 23:23:21 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: <20150410193753.eklhad@comcast.net> <20150511224106.GE2917@toaster.adamthompson.me.uk> User-Agent: edbrowse/3.5.3+ Date: Mon, 11 May 2015 19:23:21 -0400 Message-ID: <20150411192321.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1431386601; bh=BA5mFIp952j7t8odENtdU2NnMjPL0gu4wqiPf+uKM0I=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=dUsiZKQRFihfPLm69eehUjO1Nh62G7sfnue9kewA2UIs+/VM4kr8/w9WzSQy0PKKQ H1JjmzJCiQLiXZ5WTfnZki2IWaIVaSuDjK2hnzuZW1ZUD8dvvjygaIUjouW/Zo2b71 SxW+Ex18hiL2VcuncZMuub643eNyfgIeKR6yW8m0sBjIwjRV3WGkMlaIDYkAOO+kPO Jvjbt7xTnwafaWIYIT3yVOA1ohenjETcY8rLiUHyt7Gd0IzifldGT3TAx+J7C0l0Xu UV+ThpAcQU1Ki4IyG8/ykx541FToFJl2EEv5o0qHf/p8lG2HP37LdmTYbupWV3bU2R XimGqBHKcY6/A== Subject: [Edbrowse-dev] V 3.5.4 X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 May 2015 23:23:14 -0000 > 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'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. > 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. 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 Karl Dahlke