From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Third
Date: Sun, 10 Sep 2017 08:27:38 -0700 [thread overview]
Message-ID: <87k216a80l.fsf@prgmr.com> (raw)
In-Reply-To: <20170808183915.eklhad@comcast.net> (Karl Dahlke's message of "Fri, 08 Sep 2017 18:39:15 -0400")
Karl Dahlke <eklhad@comcast.net> writes:
> As we accumulate ever more third party js code, should we keep stuffing it into startwindow.js,
> as we have done with the css parser and querySelectorAll,
> or should we put it all in third.js?
> The latter offers almost no advantage, except for its organization:
Splitting it out is probably a good idea, just for the organization.
-- Chris
prev parent reply other threads:[~2017-09-10 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 22:39 Karl Dahlke
2017-09-10 15:27 ` Chris Brannon [this message]
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=87k216a80l.fsf@prgmr.com \
--to=chris@the-brannons.com \
--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).