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: Re: [Edbrowse-dev] version
Date: Sun, 25 Mar 2018 01:11:04 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LRH.2.03.1803250101340.20184@carhart.net> (raw)
In-Reply-To: <20180224120744.eklhad@comcast.net>

Sounds good to me.  I noticed this in the roadmap message:

Another possibility is json support.
Nasa calls up 11 different json files via xhr, and does nothing with them 
as far as I can tell.
That seems unlikely.


Doesn't it place those?  I thought that the real space-related content, 
such as it is, was partially coming from JSON.  Is there more to JSON 
support besides JSON.parse and JSON.stringify?

Actually, if you have something else in mind besides these two 
functions, this could be good, because sometimes pages report "invalid 
JSON" errors.  I'm not sure if there is one overall cause for these. 
When I tried to research Chuck's request for dyndns, this was in part a 
JSON error.

  reply	other threads:[~2018-03-25  8:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-24 16:07 Karl Dahlke
2018-03-25  8:11 ` Kevin Carhart [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-06-11 15:45 [edbrowse-dev] version Karl Dahlke
2018-02-15 11:56 [Edbrowse-dev] version Karl Dahlke
2018-02-15 18:48 ` Adam Thompson
2018-02-15 21:04   ` Karl Dahlke
2018-02-16 19:11     ` Adam Thompson
2018-02-18  2:19   ` Karl Dahlke
2018-02-18  2:42     ` Kevin Carhart
2018-02-18  3:03       ` Karl Dahlke
2018-02-18  3:39         ` Kevin Carhart
2018-02-18  7:43           ` Karl Dahlke
2018-02-18  8:17             ` Dominique Martinet
2018-02-18  8:47               ` Dominique Martinet
2018-02-18  8:30             ` Kevin Carhart
2018-02-18  7:45         ` Kevin Carhart
2018-02-18  8:55           ` Karl Dahlke
2018-02-18 11:29           ` Karl Dahlke
2018-02-18 14:08           ` 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:

* 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.1803250101340.20184@carhart.net \
    --to=kevin@carhart.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \


* 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).