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: Why Emacs should have a good web-browser Date: Thu, 09 Jul 2009 02:05:12 +0200 Message-ID: References: <87r5wqvqsn.fsf@stupidchicken.com> <87ocrueqdz.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1247097932 5067 80.91.229.12 (9 Jul 2009 00:05:32 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 9 Jul 2009 00:05:32 +0000 (UTC) To: Emacs Development Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 09 02:05:26 2009 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 1MOh8f-0004gb-64 for ged-emacs-devel@m.gmane.org; Thu, 09 Jul 2009 02:05:25 +0200 Original-Received: from localhost ([127.0.0.1]:57286 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MOh8e-0007RT-KA for ged-emacs-devel@m.gmane.org; Wed, 08 Jul 2009 20:05:24 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MOh8a-0007RC-OC for emacs-devel@gnu.org; Wed, 08 Jul 2009 20:05:20 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MOh8W-0007Qw-AG for emacs-devel@gnu.org; Wed, 08 Jul 2009 20:05:20 -0400 Original-Received: from [199.232.76.173] (port=38355 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MOh8W-0007Qt-3N for emacs-devel@gnu.org; Wed, 08 Jul 2009 20:05:16 -0400 Original-Received: from iwfs.imcode.com ([82.115.149.64]:47768 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 1MOh8V-0003dQ-Ep for emacs-devel@gnu.org; Wed, 08 Jul 2009 20:05:15 -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 n6905C4D017597 for ; Thu, 9 Jul 2009 02:05:12 +0200 In-Reply-To: <87ocrueqdz.fsf@stupidchicken.com> (Chong Yidong's message of "Wed, 08 Jul 2009 18:55:36 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.94 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: GNU/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:112212 Archived-At: Chong Yidong writes: > joakim@verona.se writes: > >> I would like to point to: >> http://www.emacswiki.org/emacs/EmacsXembed> >> I have some screenshots there of my xembed patch for emacs that allows >> xembedding for instance a video player(mplayer in the screenshot) in emacs. >> >> I am currently making a small xembeddable wrapper on webkit that I will >> make some screenshots with to show Emacs embedding a browser. > > That's excellent news. > > On a technical note, I think it makes more sense to associate embedded > applications with Emacs windows, rather than buffers as you're > apparently trying to do. Otherwise, we run into the problem of handling > the situation where the same buffer is displayed in more than one > window. Basically, we should have a way to say "the contents of this > window are handled by an embedded program, rather than by Emacs". WDYT? One aproach does not exclude the other. I modelled my xembed support on the way images are handled in Emacs. The use-case im really trying to achieve is having any sort of gtk controller embedded in a buffer. It kind of works already. Embedding an xembeddable browser, was just a special case of embedding the gtk socket component. I want this so I can make guis for controlling multimedia stuff in a hybrid emacs/traditional gui way. Personally I dont think embedding a browser in emacs is the way to go even though it makes for a fun demo. I think the emacs-w3m aproach is better. I'm also interested in making a similar aproach that would use mozilla-headless to render the web page in memory, and read the DOM through something MozRepl like into Emacs buffers. -- Joakim Verona