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]  tidy5
Date: Tue, 03 Feb 2015 17:15:17 -0500	[thread overview]
Message-ID: <20150103171517.eklhad@comcast.net> (raw)

> if tidy5 builds as a library (I hope it does)
> then we build and install their code same as any other library.

Sure, that makes sense.
So we'll see who has a chunk of time first to look into this.

If said library swallows html and gives us a tree of nodes, should we:

A) convert those nodes into the struct htmlTags we have today
and use most of our existing machinery, incremental, or

b) follow that tree directly, build js nodes off of it, use those nodes,
don't use our structures any more, this more of a rewrite.

I'm not expecting an answer, because we'd probably have to look
at the code, and library, and resulting tree to answer the question.
Just something to chew on.

Karl Dahlke

             reply	other threads:[~2015-02-03 22:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03 22:15 Karl Dahlke [this message]
2015-02-03 23:41 ` Adam Thompson
  -- strict thread matches above, loose matches on Subject: below --
2015-08-10  8:56 [Edbrowse-dev] startwindow / class NodeList Kevin Carhart
2015-08-12 19:55 ` Kevin Carhart
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
2015-02-02 19:58 Karl Dahlke
2015-02-03 21:18 ` 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=20150103171517.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).