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]  compartments
Date: Tue, 04 Feb 2014 17:03:41 -0500	[thread overview]
Message-ID: <20140104170341.eklhad@comcast.net> (raw)

> When I say a page within a window I'm referring
> to the ability of edbrowse to go back pages.

cw = cw->prev

That's a little over simplified, but that's the idea,
go back to the previous edbrowse window, a completely separate window.
Really not different from switching buffers.
The previous window has its own context, its own global object,
its own html page, etc.

>In theory, but the compartment field is, by default, NULL.

Ok.

I'm not going to mess with it now, I'm working on the representation of lines,
but I may want to remove all those calls and just put one in jSyncup(),
and see if that works.
That is the function that is always called when you enter the world of javascript.
Click a button, submit a form, change a field with onchange code,
any of those things, calls jSyncup().
This takes any changes you made to the form in html
and updates the corresponding js variables,
so you see it would have to be called first before running any js.
If it also set the compartment we would be good, I think.
And we don't really have to be RAII to do this,
just set the comparment to what it should be at that point,
though RAII doesn't hurt.
There might be a simpler function call.
I'll experiment when I'm not in the middle of other changes.

Karl Dahlke

             reply	other threads:[~2014-02-04 22:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04 22:03 Karl Dahlke [this message]
2014-02-05 10:44 ` Adam Thompson
  -- strict thread matches above, loose matches on Subject: below --
2014-02-05 13:55 Karl Dahlke
2014-02-05 22:09 ` Adam Thompson
2014-02-04 19:17 Karl Dahlke
2014-02-04 21:00 ` 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=20140104170341.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).