edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Kevin Carhart <kevin@carhart.net>
Cc: Karl Dahlke <eklhad@comcast.net>, Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] 3.6.0
Date: Tue, 27 Oct 2015 21:00:27 +0000	[thread overview]
Message-ID: <20151027210027.GF5233@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <alpine.LRH.2.03.1510262310140.30727@carhart.net>

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

On Mon, Oct 26, 2015 at 11:30:21PM -0700, Kevin Carhart wrote:
> 
> >Are there other bugs we need to fix, small enhancements we need to make?
> >In particular, (Kevin), are we miles away from jQuery,
> >wherein that should wait for 3.6.1, or would a few more small changes get us there?
> 
> The recent progress is significant, but I don't think it's going to be ready
> for 3.6.0.  Here's a crude gauge.  We're working through this javascript
> routine called jQuery.support, where they have bundled together a long
> series of tests of different mandatory behaviors.  And it tries them one
> after the next.  We've done several.  I'm currently working on a method
> called cloneNode, which roughly speaking is found at around line 75 of 232
> lines.  So I think our recent good work is about 33% of the way through the
> supports routine!  However, it could be even further than that, because when
> I scan lower, I notice a lot of use of the big node manipulations which are
> already done thanks to Karl. There's also empty space and comments, so it's
> not like the remaining 150 lines is dense with tricky DOM problems.
> 
> So it's coming, but it's a little more than a few small changes, I think.

Excellent, thanks for doing this work.

> By the way, recently I spent a few days learning the codebase better and
> tracing C calls from place to place.  I had hopped around in an episodic
> way, but hadn't gotten the big picture.  So now that I got to know the
> jseng-moz.cpp, readMessage, writeMessage, and the EJ_ commands, I like it!
> Thank you for writing this, Karl, Adam & Chris.

Karl and Chris have to take the credit for this setup.

Given that we can't release until a tidy5 package,
I say we continue fixing things and then do the bug fix phase at that point.
I guess I'm really hoping for some sort of jquery support by that stage.

Cheers,
Adam.

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

  reply	other threads:[~2015-10-27 21:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-26 16:42 Karl Dahlke
2015-10-27  6:30 ` Kevin Carhart
2015-10-27 21:00   ` Adam Thompson [this message]
2015-10-28  6:59     ` Kevin Carhart
2015-10-27  9:03 ` Chris Brannon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151027210027.GF5233@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    --cc=kevin@carhart.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).