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] css on demand
Date: Thu, 15 Feb 2018 03:17:30 -0500	[thread overview]
Message-ID: <20180115031730.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1802142222070.25035@carhart.net>

> I was just in startwindow - that's a ton of work!

Yeah, too bad some of it was wasted.   :)
You know the mantra, "A moment of thought is worth a megabyte of programming."
I slightly forgot that, just because I like to program.
I implemented hashing by nodes, hashing by class name, optimizations for certain chains, blah blah blah,
and then I realized I didn't need any of that if I was gathering css elements on demand,
and then I realized I couldn't support it anyways, if querySelectorAll is dynamic,
if it is suppose to query the document tree as it stands right now,
and nodes are always changing, with new nodes added,
so a snapshot cache we build at the start isn't really going to help,
and maintaining that cache as each new node is added etc is rather prohibitive,
so anyways that was 200 tricky lines of code that I wrote, then threw away within 24 hours,
but other than that, you know,
the other 750 lines are good, and represent real progress.
I'm about to delete the jotform stuff, cause I'm pretty sure we're not gonna use it,
and as others have pointed out in this list, if we change our mind it's all in git.

Karl Dahlke

  reply	other threads:[~2018-02-15  8:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 15:59 Karl Dahlke
2018-02-14 19:21 ` Adam Thompson
2018-02-14 19:50   ` Chuck Hallenbeck
2018-02-16 16:59     ` Karl Dahlke
2018-02-17 10:52       ` [Edbrowse-dev] URL.prototype.slice Kevin Carhart
2018-02-17 11:25         ` Karl Dahlke
2018-02-15  6:24 ` [Edbrowse-dev] css on demand Kevin Carhart
2018-02-15  8:17   ` Karl Dahlke [this message]
2018-02-15  8:34     ` Kevin Carhart

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=20180115031730.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).