From: Adam Thompson <arthompson1990@gmail.com>
To: Chris Brannon <chris@the-brannons.com>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] debian1
Date: Sat, 4 Jan 2014 23:14:19 +0000 [thread overview]
Message-ID: <20140104231419.GC11201@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <877gaf2vl4.fsf@mushroom.PK5001Z>
On Sat, Jan 04, 2014 at 03:09:11PM -0800, Chris Brannon wrote:
> Adam Thompson <arthompson1990@gmail.com> writes:
>
> > I've looked for one and I think someone did something based around a gtk-less
> > webkit, but I'm not sure how maintained (or maintainable) it is.
>
> Yeah, I heard something about a headless webkit a while back, but I
> never tracked it down.
> Also, a friend of mine is working on a console browser that uses firefox
> as its backend. It hooks into firefox via mozrepl. Here's the brief
> description of mozrepl:
>
> <quote>
> MozRepl lets you program Firefox and other Mozilla-based applications from the
> inside using a telnet client.
> </quote>
>
> You still have to run firefox itself, but for those of us who don't care
> to spin up a GUI, you can run it under xvfb, which is a virtual X
> server.
I've played with xvfb in the past, never really got it to work particularly well though.
At any rate, it seems an aweful lot to get javascript and dom working,
and would make edbrowse basicly just a firefox client.
I've got no problem with using something like your friend's work,
but I'd rather not take edbrowse in this direction if at all avoidable.
Also do you know if iceweasel has this feature?
Cheers,
Adam.
next prev parent reply other threads:[~2014-01-04 23:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-04 20:03 [Edbrowse-dev] debian Karl Dahlke
2014-01-04 21:40 ` [Edbrowse-dev] debian1 Adam Thompson
2014-01-04 23:09 ` Chris Brannon
2014-01-04 23:14 ` Adam Thompson [this message]
2014-01-05 15:47 ` Chris Brannon
2014-01-05 1:09 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:
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=20140104231419.GC11201@toaster.adamthompson.me.uk \
--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).