From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-po-03v.sys.comcast.net (resqmta-po-03v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:162]) by hurricane.the-brannons.com (Postfix) with ESMTPS id C7375786FA for ; Fri, 26 Dec 2014 19:19:52 -0800 (PST) Received: from resomta-po-11v.sys.comcast.net ([96.114.154.235]) by resqmta-po-03v.sys.comcast.net with comcast id YTHT1p00254zqzk01THg3E; Sat, 27 Dec 2014 03:17:40 +0000 Received: from eklhad ([68.84.191.77]) by resomta-po-11v.sys.comcast.net with comcast id YTHg1p0011gep3001THgjM; Sat, 27 Dec 2014 03:17:40 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke User-Agent: edbrowse/3.5.2 Date: Fri, 26 Dec 2014 22:17:39 -0500 Message-ID: <20141126221739.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=1419650260; bh=9KR5q8AD0gH4CjLYyOEqgSit6u7Fn2whuScHCEVj+Kg=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=a2MnQLpvRFGyxE+jLQJlfrCPad0VzWCwp+0qku+ZqA/ULXkOqCIDo8bXps7FJWE+J vFQy0sDnpf+UpUt35ZzW+0vQ7LpqPtGHV9ZtoiZvClXkyY7ZpVW3Ngi5zEi5xacFuY 4DngFnXpIegx2Ot5ZvZiasvWNzc7NjH9fd389L3EPdRX2BqhlOxXXHwvqHWz6pxOBu 6wCB404W5Rchas9s30Zi09+ikLPW1CPb20DKtmzcFRrxsDWlKZBEAbuiICrN5lJzId Vs6rR0fXADuw2Mwy+tcP9RzUlM3N/NcarGeJQ1z1D0dPa9ZxeLgPgwLWc3oI8t7flG 8rlQq3hSLhwxA== Subject: [Edbrowse-dev] Tasks 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: Sat, 27 Dec 2014 03:19:53 -0000 It's kinda funny - we get busy with our lives and don't do substantial work on edbrowse for several months, then we dive in on things, sometimes the same things, which isn't very efficient. I'd like to propose a few tasks, using that term loosely, and ask who might want to claim which ones. These are in no order, and there may be others; I may even be missing the most important ones. 1. Research into v8 or perhaps other js engines. Just play with it, hello world, what can it do, is it better or worse than moz, perhaps rewrite jseng.cpp in it if you really want to dive in. 2. Is there any open source that would help us with DOM? I thought we might steal from Chrome, which would play better with v8, but I don't know if any dom software can reasonably be extracted from the whole. 3. How does dom really work anyways? Is there a book or tutorial that actually tells us what we have to implement? 4. Fork off a copy of edbrowse and download files in the background, as described in my earlier email. 5. Implement imap. A lot of people want this. Many more would use it for mail if it had imap, and curl supports imap, so I don't think this would be as hard as it first appears. 6. How are we going to approach frames and iframes. Today I turn them into hyperlinks to the web pages, but *every* other browser puts all the pages together into oneseamless whole. We should probably do that too. Then buffers and web pages don't corresponds 1 for 1 any more. Lines 237 through 451 might be this page, and 452 to 989 that page, and so on. 7. What happens when javascript accesses variables in other documents. This can be done through frames. In the mozilla world, those variables are in another compartments. Doesn't that cause js to blow up? Or at least not to see those variables? Or is everything in firefox in one compartment, but that can't be right either because each compartment has one global window object. Maybe interwindow communication doesn't happen enough for us to worry about, and is usually done for visual effects anyways. 8. What is ajax and jquery and all those, and how much of that do we have to implement? 9. Find the most common websites, and trace through the js, slowly and painfully, to see what we really need to do. This is market driven, the 100 most used websites, and make edbrowse work for those. Given our limited resources, we might have to proceed this way, rather then doing it all. I've tried to track through js to see where edbrowse fails and why, and it's a terribly slow and frustrating process, especially if the js has been deliberately crapized. I think we really need to do some of this, but I rarely have the patience to actually do it. Karl Dahlke