From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] startwindow / class NodeList
Date: Wed, 12 Aug 2015 12:55:25 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1508121148020.32056@carhart.net> (raw)
In-Reply-To: <20150711201545.eklhad@comcast.net>
Hi Adam and Karl,
Thanks for writing, I take your points about where to do what.
I see the points about the back and forth, can we, can't we. I'm not
married to writing javascript so maybe I could help build out some
pieces of DOM in C when the time comes. I remember the tidy5 thread and I
agree that this will be huge, because doesn't this mean you will have an
easier time from now on, doing the types of translations that jSyncup
does? So tidy5 is a big deal! Maybe I should wait a while and see how
the landscape for how to work changes with the parser?
> Even if startwindow.js is temporary, it sure has brought us a lot of
> functionality for not a lot of code,
> to help us see the path ahead, maybe like a prototype.
I know what you mean. In order to get over the chicken and egg problem of
not knowing anything and not knowing how to find out, I did something like
this and compiled a very marked-up edbrowse as a dynamic harness for
loading a web page over and over and playing along with what
happens. What I've observed is that then it raises a question around
generality and specificity: so I'm knee-deep in the real world, weird code
of a live website (like amazon, or yellowpages or yelp), how do I know if
the situations I'm seeing will come up enough generally for the effort to
have been worth it? Or does this uncertainty mean that the
reverse-engineering technique is extraneous? Anyway, I did some of this..
it's like Karl has written from time to time - you also reverse particular
pages because you are trying to get that page working for yourself in the
short term.
> I think we all have a lot of other stuff going on in life,
> which has slowed us down a bit of late.
I understand.. I have set it down for long periods. I picked edbrowse
back up about a month ago and have been a bit addicted since then.
thanks
Kevin
PS As a short aside, Karl, you have periodically said, I don't foresee
anyone writing journal articles about us. I wonder if someone like Norton
or McAfee would show some interest. Have you considered trying to
interest the anti-malware world in edbrowse as a safe quarantine or
forensic environment for a page containing bad javascript?
--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists
next prev parent reply other threads:[~2015-08-12 19:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 8:56 Kevin Carhart
2015-08-11 21:38 ` Adam Thompson
2015-08-12 0:15 ` Karl Dahlke
2015-08-12 19:55 ` Kevin Carhart [this message]
2015-08-12 20:56 ` Karl Dahlke
2015-08-13 1:08 ` Chris Brannon
2015-08-13 4:36 ` [Edbrowse-dev] tidy5 Kevin Carhart
2015-08-13 20:07 ` Adam Thompson
2015-08-14 0:54 ` Kevin Carhart
2015-08-14 3:45 ` Karl Dahlke
2015-08-14 20:17 ` Chris Brannon
2015-08-16 5:54 ` Kevin Carhart
2015-08-16 10:38 ` Karl Dahlke
2015-08-14 3:37 ` Karl Dahlke
2015-08-16 18:10 ` Adam Thompson
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=alpine.LRH.2.03.1508121148020.32056@carhart.net \
--to=kevin@carhart.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.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).