From: Adam Thompson <arthompson1990@gmail.com>
To: Chris Brannon <chris@the-brannons.com>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] $ object in javascript
Date: Tue, 27 Dec 2016 18:48:13 +0000 [thread overview]
Message-ID: <20161227184813.GC8364@odin> (raw)
In-Reply-To: <87mvfhxtkp.fsf@the-brannons.com>
[-- Attachment #1: Type: text/plain, Size: 1783 bytes --]
On Tue, Dec 27, 2016 at 07:47:18AM -0800, Chris Brannon wrote:
> Karl Dahlke <eklhad@comcast.net> writes:
>
> > Well we've all been corresponding long enough to know my answer to that one;
> > do as much as you can in start js:
>
> Right. It has so many benefits. I wonder if there's any way of making
> the code in startwindow tamper-proof, so that it cannot be replaced by
> the outside world. Also it would be nice if some methods and fields
> could be only visible to code in startwindow, while not being visible to
> the outside world. I don't think we can do that, but I'm going to
> research it.
As far as I know we can't with smjs, which scares me a little given all
the AJAX machinary we're looking at.
However, if we can make our native http fetching machinary work correctly we
*may* be ok. I think I'd rather the get and post bits were native so we can
make them read-only (I think) and make sure they can't be switched by outside
code.
> > Chris, would you rather I, or someone else, took over the official github hosting and edbrowse.org?
> > I primarily passed them to you because I'm older and will likely die
> > sooner,
>
> Well, I have no problem coordinating, hosting this list, etc etc.
> As it stands, our source downloads are now all hosted on Github. Github
> will automatically generate an archive for each tagged release, so
> there's no need to host them on edbrowse.org as well.
> I do still have to manage the static binaries myself. And the build
> process is quite finnicky. I'll keep doing that. Don't panic, I'm not
> going away.
I'm also able to help if any is required. Out of interest, and on a slightly
unrelated note, anyone know whos maintaining the netBSD package in pkgsrc?
Cheers,
Adam.
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-12-27 18:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 16:03 Karl Dahlke
2016-11-29 16:24 ` Chris Brannon
2016-11-30 0:47 ` Kevin Carhart
2016-11-30 7:30 ` Karl Dahlke
2016-11-30 7:43 ` Tyler Spivey
2016-11-30 7:54 ` Karl Dahlke
2016-12-01 0:04 ` Kevin Carhart
2016-12-01 1:17 ` Karl Dahlke
2016-12-25 13:06 ` Adam Thompson
2016-12-26 14:52 ` Karl Dahlke
2016-12-27 3:04 ` Kevin Carhart
2016-12-27 3:49 ` Karl Dahlke
2016-12-27 4:17 ` Kevin Carhart
2016-12-27 4:38 ` Karl Dahlke
2016-12-27 18:37 ` Adam Thompson
2016-12-27 4:59 ` Chris Brannon
2016-12-27 6:53 ` Kevin Carhart
2016-12-27 15:21 ` Chris Brannon
2016-12-27 20:13 ` Kevin Carhart
2016-12-27 13:26 ` Karl Dahlke
2016-12-27 15:47 ` Chris Brannon
2016-12-27 18:48 ` Adam Thompson [this message]
2016-12-27 20:23 ` Chris Brannon
2016-12-28 11:42 ` [Edbrowse-dev] Edbrowse in NetBSD Adam Thompson
2016-12-28 11:50 ` Chris Brannon
2016-12-28 12:15 ` Adam Thompson
2016-12-27 19:11 ` [Edbrowse-dev] $ object in javascript Adam Thompson
2016-12-27 19:47 ` Kevin Carhart
2016-12-27 20:11 ` Karl Dahlke
2016-12-27 20:45 ` [Edbrowse-dev] nextSibling and previousSibling Kevin Carhart
2016-12-27 21:14 ` Chris Brannon
2016-12-28 11:38 ` [Edbrowse-dev] $ object in javascript 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=20161227184813.GC8364@odin \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=chris@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).