From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] nasa / prepending "on" to events
Date: Fri, 26 Jan 2018 14:28:35 -0500 [thread overview]
Message-ID: <20180026142835.eklhad@comcast.net> (raw)
In-Reply-To: <CA+PgotKfzWgTF1eCPwgr8DS6UQTXbUOh9hDQazfmBs6so3M=sw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]
This is a good start and a good strategy.
I can capture all the generated html with db5, though I have to do some editing to pull that out and separate it from all the other debug messages.
But we must remember this is only part of the story.
You can build the page piece by piece, without generating any html at all.
Create each table, each cell, each paragraph, each anchor, literally build it from the ground up using the DOM primitives.
NASA might be doing that.
I mean there's obviously more text on the page than you see in html, even if it isn't complete and isn't linked properly.
This stuff is not easy.
Karl Dahlke
next prev parent reply other threads:[~2018-01-26 19:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 20:08 [Edbrowse-dev] Error Object Karl Dahlke
2018-01-19 20:51 ` Dominique Martinet
2018-01-25 10:48 ` [Edbrowse-dev] defaultView / cloning onevent$$array Kevin Carhart
2018-01-25 14:07 ` Karl Dahlke
2018-01-25 23:07 ` Kevin Carhart
2018-01-26 2:58 ` Karl Dahlke
2018-01-26 3:50 ` [Edbrowse-dev] nasa / prepending "on" to events Kevin Carhart
2018-01-26 4:59 ` Karl Dahlke
2018-01-26 5:51 ` Kevin Carhart
2018-01-26 6:43 ` Karl Dahlke
2018-01-26 8:10 ` Kevin Carhart
2018-01-26 8:21 ` Kevin Carhart
2018-01-26 9:08 ` Karl Dahlke
2018-01-26 10:38 ` Kevin Carhart
2018-01-26 14:32 ` Karl Dahlke
2018-01-26 19:13 ` Geoff McLane
2018-01-26 19:28 ` Karl Dahlke [this message]
2018-01-27 3:52 ` Kevin Carhart
2018-01-27 18:52 ` Geoff McLane
2018-01-27 21:10 ` Karl Dahlke
2018-01-28 3:12 ` Karl Dahlke
2018-01-28 19:19 ` Geoff McLane
2018-01-28 21:35 ` Karl Dahlke
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=20180026142835.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).