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 21:06:41 +0300 Message-ID: <83oce8fwlq.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> <83pqyofzdg.fsf@gnu.org> <8739vkbpq5.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 1279217330 16182 80.91.229.12 (15 Jul 2010 18:08:50 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 15 Jul 2010 18:08:50 +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 20:08:49 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 1OZSrY-0003Jk-1O for ged-emacs-devel@m.gmane.org; Thu, 15 Jul 2010 20:08:48 +0200 Original-Received: from localhost ([127.0.0.1]:36974 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OZSrX-0003VR-C8 for ged-emacs-devel@m.gmane.org; Thu, 15 Jul 2010 14:08:47 -0400 Original-Received: from [140.186.70.92] (port=46599 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OZSrR-0003Ux-E9 for emacs-devel@gnu.org; Thu, 15 Jul 2010 14:08:42 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OZSrQ-0004iW-8L for emacs-devel@gnu.org; Thu, 15 Jul 2010 14:08:41 -0400 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:50137) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OZSrQ-0004iL-0s for emacs-devel@gnu.org; Thu, 15 Jul 2010 14:08:40 -0400 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0L5M00I002CC5R00@a-mtaout22.012.net.il> for emacs-devel@gnu.org; Thu, 15 Jul 2010 21:08:38 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([77.127.120.144]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0L5M00EFH2EDFAD0@a-mtaout22.012.net.il>; Thu, 15 Jul 2010 21:08:38 +0300 (IDT) In-reply-to: <8739vkbpq5.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:127385 Archived-At: > From: =C3=93scar Fuentes > Date: Thu, 15 Jul 2010 19:48:50 +0200 >=20 > Eli Zaretskii writes: >=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? >=20 > I would use Qt, hence C++, not being shy about using advanced langu= age > features if necessary. That is for getting a working system as soon= as > possible. C++ is not the fastest language to get a job done. Plus, you'll have unrelated job on your hands of making Emacs C++-compliant, as discussed in another thread. Unless you are rewriting the whole Emacs, that is ;-) > > How you will be able to implement a new display engine without at > > least some familiarity with what the current one does? >=20 > I expect that if the internal layout of the data to be displayed is > clear enough, that is sufficient for the display engine writer. I m= ean, > knowing "this represents a text property" is what you need. Knowing= how > the current display engine deals with it shouldn't be necessary. I said "knowing WHAT the current does", not HOW it does that. The problem is, you cannot know WHAT it does without at least some study of the code, because there's no requirements document. Take the font-lock, for example -- it has special support in the display engine. Without implementing the APIs for this support, JIT Lock, which is standard since Emacs 21.1, will not work.