From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:41]) by hurricane.the-brannons.com (Postfix) with ESMTPS id F0C8078953 for ; Sat, 7 Nov 2015 14:34:59 -0800 (PST) Received: from resomta-ch2-20v.sys.comcast.net ([69.252.207.116]) by resqmta-ch2-09v.sys.comcast.net with comcast id embC1r0032XD5SV01mbWE1; Sat, 07 Nov 2015 22:35:30 +0000 Received: from eklhad ([IPv6:2601:405:4080:53:21e:4fff:fec2:a0f1]) by resomta-ch2-20v.sys.comcast.net with comcast id embV1r00P1DsNmD01mbV8e; Sat, 07 Nov 2015 22:35:30 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: <20151006145114.eklhad@comcast.net> <87611d4fep.fsf@mushroom.localdomain> User-Agent: edbrowse/3.5.4.2+ Date: Sat, 07 Nov 2015 17:35:29 -0500 Message-ID: <20151007173529.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=1446935730; bh=IqpVYpK4759RluXakvXhoY75wkcn7+qPvmUnPPIbP6E=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=IdFOuRKVo0zaVQH9n25XpdPa8POvv94NZOduc3UpT7Q5luPJ1Gneg9AKQq06oA/v9 oRWnOGBMW20LQnq2wepW1uP5lz8nQJ+EGehw8PO0vJZcdKJs7mWrRjue90QIPeYAEd iQrZBRbURsWk8tgopqgonxnK4vOmQHgSE/xu9TxKeLLKCBOes6cXEdWDsijXAWgfrw lZ9kDBkPvi4kjZMkLmGd79bxmjwEuCY+7EzpLDrXsdPOckeCDBjIauIBBiG6Q2eYyt 0Q5tCteZBFxBnIaOqOGsNgnlFnZmr5MUF48+p1+vPU3a7vCI7QcLm+VaVoIuO1Gbzb bZ0+guWGSW7ow== Subject: [Edbrowse-dev] a JS centric design X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.20 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2015 22:35:00 -0000 > 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