edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Kevin Carhart <kevin@carhart.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] startwindow / class NodeList
Date: Mon, 10 Aug 2015 01:56:27 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LRH.2.03.1508100049370.5894@carhart.net> (raw)



Hi guys

I was familiarizing myself with DOM discussions on the listserv over 
2014-15, so that I can hopefully contribute and be up to date on 
recent work when trying to figure out how.  I've installed from github, 
and have been taking a look at the startwindow.js.  Maybe I could help 
build out some pieces of DOM?

I noticed something in past DOM discussions on the list.  A while ago, 
Adam said, "Also, as per comments in startwindow.js, apparently we're 
supposed to return something called a node list object rather than an 
array from getElement* functions. No idea what one of these is yet, more 
future research I think."

You may know this already, but the env.js code has a specification for 
NodeList!  I put it up at:
http://carhart.net/~kevin/nodelist.js

Adam, you said you had taken a look at env.js, right?  I know it isn't 
suitable as an implementation out of the box, but do you think env is 
useable as a guide, for example if I was to try and adapt 
document.getElementsByTagName to return a NodeList?

I notice in the env code that they cite URLs from w3, which makes me 
hopeful that they have done good generic work that just happens to be in 
javascript.  Here's what they have to say about document and about the 
'Node' class,
http://carhart.net/~kevin/document.js
http://carhart.net/~kevin/node.js

thanks!
Kevin

--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists

             reply	other threads:[~2015-08-10  8:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10  8:56 Kevin Carhart [this message]
2015-08-11 21:38 ` Adam Thompson
2015-08-12  0:15   ` Karl Dahlke
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

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.1508100049370.5894@carhart.net \
    --to=kevin@carhart.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).