From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: Emacs and Gnome Canvas Date: Thu, 15 Jul 2010 23:27:14 +0200 Message-ID: <87tyo0a11p.fsf@telefonica.net> References: <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> <83oce8fwlq.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1279229264 27473 80.91.229.12 (15 Jul 2010 21:27:44 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 15 Jul 2010 21:27:44 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 15 23:27:41 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 1OZVy0-0002Fo-1Q for ged-emacs-devel@m.gmane.org; Thu, 15 Jul 2010 23:27:40 +0200 Original-Received: from localhost ([127.0.0.1]:52602 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OZVxz-0000Mp-DN for ged-emacs-devel@m.gmane.org; Thu, 15 Jul 2010 17:27:39 -0400 Original-Received: from [140.186.70.92] (port=59656 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OZVxt-0000MO-5w for emacs-devel@gnu.org; Thu, 15 Jul 2010 17:27:34 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OZVxs-0008EQ-7N for emacs-devel@gnu.org; Thu, 15 Jul 2010 17:27:33 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:41516) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OZVxr-0008E7-Su for emacs-devel@gnu.org; Thu, 15 Jul 2010 17:27:32 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1OZVxp-0002Co-71 for emacs-devel@gnu.org; Thu, 15 Jul 2010 23:27:29 +0200 Original-Received: from 83.42.13.171 ([83.42.13.171]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 15 Jul 2010 23:27:29 +0200 Original-Received: from ofv by 83.42.13.171 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 15 Jul 2010 23:27:29 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 43 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 83.42.13.171 User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) Cancel-Lock: sha1:KVhxRutAkg/ZZpWz5T2YEOLfTFE= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) 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:127393 Archived-At: Eli Zaretskii writes: >> I would use Qt, hence C++, not being shy about using advanced language >> 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. That's very true. Unfortunately, AFAIK there is no Free high quality cross platform GUI for Lisp :-) > Plus, you'll have unrelated job on your hands of making Emacs > C++-compliant, as discussed in another thread. Only the Emacs header files that the display engine needs must be acceptable by g++. The .c files would be compiled by gcc as usual. > Unless you are rewriting the whole Emacs, that is ;-) Others are already doing that :-) >> > How you will be able to implement a new display engine without at >> > least some familiarity with what the current one does? >> >> 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 mean, >> 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. I see. That's probably one instance of the "tight coupling" I was talking about before. Apart from reading all the source code, I hope that it is possible to look into just a few header files for learning the interface of the display engine.