From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs and Gnome Canvas Date: Thu, 15 Jul 2010 20:06:51 +0300 Message-ID: <83pqyofzdg.fsf@gnu.org> References: <4C3CD120.4040905@swipnet.se> <5A91499A-0470-43FD-9F48-560CEAD3424C@mit.edu> <83wrsyr068.fsf@gnu.org> <83iq4hhjww.fsf@gnu.org> <87sk3lbvv0.fsf@telefonica.net> <83hbk1grnq.fsf@gnu.org> <4C3EBCDC.8050709@swipnet.se> <83d3upgmwj.fsf@gnu.org> <4C3ECB4C.6050208@swipnet.se> <83aaptgly1.fsf@gnu.org> <4C3ED4F9.4080603@swipnet.se> <83630hgi0r.fsf@gnu.org> <4C3EE8D6.3020607@swipnet.se> <8339vlgcax.fsf@gnu.org> <87fwzkbzg8.fsf@telefonica.net> <877hkwag6y.fsf@stupidchicken.com> <877hkwbth6.fsf@telefonica.net> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Trace: dough.gmane.org 1279213809 3180 80.91.229.12 (15 Jul 2010 17:10:09 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 15 Jul 2010 17:10:09 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?utf-8?Q?=C3=93scar_Fuentes?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 15 19:10:06 2010 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.69) (envelope-from ) id 1OZRwk-0006Bq-6P for ged-emacs-devel@m.gmane.org; Thu, 15 Jul 2010 19:10:06 +0200 Original-Received: from localhost ([127.0.0.1]:39292 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OZRwi-00045A-Vf for ged-emacs-devel@m.gmane.org; Thu, 15 Jul 2010 13:10:05 -0400 Original-Received: from [140.186.70.92] (port=54726 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OZRwP-0003xq-P7 for emacs-devel@gnu.org; Thu, 15 Jul 2010 13:09:47 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OZRwN-0004VM-3F for emacs-devel@gnu.org; Thu, 15 Jul 2010 13:09:43 -0400 Original-Received: from mtaout23.012.net.il ([80.179.55.175]:44767) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OZRwM-0004V4-Sx for emacs-devel@gnu.org; Thu, 15 Jul 2010 13:09:43 -0400 Original-Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0L5L00I00ZMG6F00@a-mtaout23.012.net.il> for emacs-devel@gnu.org; Thu, 15 Jul 2010 20:08:48 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([77.127.120.144]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0L5L00FIHZMNK4A0@a-mtaout23.012.net.il>; Thu, 15 Jul 2010 20:08:48 +0300 (IDT) In-reply-to: <877hkwbth6.fsf@telefonica.net> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 (beta) 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:127379 Archived-At: > From: =C3=93scar Fuentes > Date: Thu, 15 Jul 2010 18:27:49 +0200 >=20 > I know from the start that the stuff I'll use *if* the plan goes > ahead is not acceptable for key Emacs developers Why the defeatism? Yidong expressed an understandable skepticism, bu= t if you present a persuasive case for the Canvas, I don't think it wil= l be rejected without consideration. > Anyways, I'm not interested on learning about the current display > engine. How you will be able to implement a new display engine without at least some familiarity with what the current one does? > I'm more interested on a simpler approach: here is the data, displa= y > it. This isn't Emacs. You are describing Gnuplot. The most important problem a display engine needs to solve is: here's the new data and the old display, now update the display. And the data is not all given in one place. > The only thing I really fear is finding that other parts of Emacs > (high-level event handling or content change management, for > instance) are tightly coupled with the current display engine. What do you mean by ``tightly coupled''? The current display stops i= f input becomes available -- is that tight enough? In general, if you make all kinds of assumptions that would break you= r approach, I'd suggest to publish those assumptions -- that's the fastest way to validating them, short of studying the code yourself.