edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Now on 24
Date: Wed, 29 Jan 2014 13:49:18 -0500	[thread overview]
Message-ID: <20140029134918.eklhad@comcast.net> (raw)

I downloaded moz 24, and am following the master branch for edbrowse.
I built everything, ran jsrt ok,
and am using edbrowse now to write and send this email.

I pushed a commit that changes several files, but all docs,
trying to bring that up to date with what we're doing.
Mostly README which was way out of date.
Also gave credit to Adam for his work in our usersguide.html,
but if you would rather have your privacy I will happily delete the reference.
My default is to give people the credit they are due.

With three of us accessing the main branch we need to coordinate.

One chunk of work is to clean up html.cpp,
use string objects where it makes sense,
like anywhere you see stringAndString or stringAndChar etc
all that mess is easier with strings,
and use the array class instead of my lists so all those warnings go away.
I could do this, unless someone else is in there anyways
and wants to take it on.

Tracking down more js bugs, probably best left to you.
Why for instance would a js object call ever return null?
Can't believe we're out of memory.

Then there is the question of substituting in longer lines,
or allowing for more lines.
This one probably best left to me, as I am more familiar with buffers.c.

Then there's lots of new features and enhancements to do, as we discussed,
but probably we should get this stuff stable first,
make a new version, then move on to other things.

What do you think?

Karl Dahlke

             reply	other threads:[~2014-01-29 18:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-29 18:49 Karl Dahlke [this message]
2014-01-29 22:31 ` Adam Thompson
2014-01-30  0:26 ` 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=20140029134918.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    /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).