From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: joakim@verona.se Newsgroups: gmane.emacs.devel Subject: Re: An Emacs plug-in for a browser (Firefox?) Date: Sat, 06 Sep 2008 18:58:48 +0200 Message-ID: References: <18624.40059.414121.633475@gargle.gargle.HOWL> <48C0BB3A.4080201@pajato.com> <87zlmnezy9.fsf@shellarchive.co.uk> <48C0FC53.4020806@gmail.com> <6fa54e4e0809050420i5132ace5red5a011b69ecd1ed@mail.gmail.com> <87myilkyyf.fsf@cyd.mit.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1220720479 19119 80.91.229.12 (6 Sep 2008 17:01:19 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 6 Sep 2008 17:01:19 +0000 (UTC) Cc: rms@gnu.org, pmr@pajato.com, lennart.borgman@gmail.com, Antoine Levitt , raman@users.sourceforge.net, emacs-devel@gnu.org, phil@shellarchive.co.uk To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Sep 06 19:02:12 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Kc1Ap-0003kv-8b for ged-emacs-devel@m.gmane.org; Sat, 06 Sep 2008 19:02:11 +0200 Original-Received: from localhost ([127.0.0.1]:38458 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kc19p-0006ak-NN for ged-emacs-devel@m.gmane.org; Sat, 06 Sep 2008 13:01:09 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Kc19k-0006Xi-H8 for emacs-devel@gnu.org; Sat, 06 Sep 2008 13:01:04 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Kc19g-0006Rr-Kk for emacs-devel@gnu.org; Sat, 06 Sep 2008 13:01:03 -0400 Original-Received: from [199.232.76.173] (port=48063 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kc19g-0006Rm-Df for emacs-devel@gnu.org; Sat, 06 Sep 2008 13:01:00 -0400 Original-Received: from iwfs.imcode.com ([82.115.149.64]:34930 helo=gate.verona.se) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Kc19d-0005Ez-9h; Sat, 06 Sep 2008 13:00:57 -0400 Original-Received: from localhost.localdomain (IDENT:1005@localhost [127.0.0.1]) by gate.verona.se (8.13.4/8.11.4) with ESMTP id m86GwtNi008650; Sat, 6 Sep 2008 19:00:11 +0200 In-Reply-To: <87myilkyyf.fsf@cyd.mit.edu> (Chong Yidong's message of "Sat, 06 Sep 2008 12:42:48 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Linux 2.4-2.6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:103591 Archived-At: Chong Yidong writes: > "Richard M. Stallman" writes: > >> I proposed years ago that we extend Emacs to the point where it can >> function as a word processor. This is mainly a matter of adding >> features that let you put things in a buffer (and save them in files) >> to get various kinds of formatting effects. To display web pages is >> an even more distant goal; it requires MORE new buffer and display >> features. > > That's assuming we rely on the Emacs redisplay engine. The approach > being discussed in this thread is to embedding the output generated by > an external browser library in an Emacs window. > > Basically, this involves being able to tell an Emacs window not to draw > the usual Emacs display, but to display the output from an external > process (an embedded browser process) instead. I think it's very > feasible, assuming someone has the time to do it. The bottleneck here > is manpower. Again I want to shamelessly promote my project: http://www.emacswiki.org/cgi-bin/wiki/EmacsXembed I havent worked on it lately, but this thread is starting to make me want to prove that its possible to embed a browser. The thing that actually stopped me from demoing browser embedding, rather that video etc, is that I didnt find a browser which supported being embedded with xembed. It shouldnt be a big problem, though, to modify a gnome based browser to use a xembeddable widget as main window. My primary aim for embedding isnt actually browsers: its for embedding stuff like Inkscape, multimedia apps, and make music guis for csound and supercollider etc, so thats why I havent done anything more for browser support. > (Maybe this would be a good Google Summer of Code project). -- Joakim Verona