From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Reitter Newsgroups: gmane.emacs.devel Subject: Re: Aquamacs distro for OS X like behavior Date: Fri, 8 Apr 2005 10:50:52 +0100 Message-ID: References: <7ca1709813602da58a139cee58fb4c63@gmail.com> <3b9c4e2f33d37fed55f640dcafbc8d65@gmail.com> <002d01c53a15$4a871c60$0200a8c0@sedrcw11488> <004e01c53bc0$adedf560$0200a8c0@sedrcw11488> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1112953946 32084 80.91.229.2 (8 Apr 2005 09:52:26 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 8 Apr 2005 09:52:26 +0000 (UTC) Cc: rms@gnu.org, Lennart Borgman , Robert Roebling , emacs-devel@gnu.org, monnier@iro.umontreal.ca Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Apr 08 11:52:23 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DJq9r-0001lo-0h for ged-emacs-devel@m.gmane.org; Fri, 08 Apr 2005 11:52:11 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DJpjK-0000dq-L6 for ged-emacs-devel@m.gmane.org; Fri, 08 Apr 2005 05:24:46 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DJpig-0000UN-2u for emacs-devel@gnu.org; Fri, 08 Apr 2005 05:24:06 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DJpiU-0000Pm-E0 for emacs-devel@gnu.org; Fri, 08 Apr 2005 05:23:58 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DJpiU-0000OJ-0U for emacs-devel@gnu.org; Fri, 08 Apr 2005 05:23:54 -0400 Original-Received: from [64.233.184.204] (helo=wproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DJq9S-00081A-LA for emacs-devel@gnu.org; Fri, 08 Apr 2005 05:51:46 -0400 Original-Received: by wproxy.gmail.com with SMTP id 50so953756wri for ; Fri, 08 Apr 2005 02:50:55 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:in-reply-to:references:mime-version:content-type:message-id:content-transfer-encoding:cc:from:subject:date:to:x-mailer; b=tEccthXZmLxtwTUPOIHM1LSxQd1fKlBeCLd1JB9NGfMQUwqpFCX1ot7Qv+HREQ/I9Jev1X+k0WJIBnZgQNFACkiOigHsM66KfzBFefcKdrdqra0b09Z4JaqtGUlEmANuwoGRx8ZIZqJFlrE/1Bu4vFl0VdrmO5q5XtBDmtgytdg= Original-Received: by 10.54.79.17 with SMTP id c17mr781145wrb; Fri, 08 Apr 2005 02:50:55 -0700 (PDT) Original-Received: from ?129.215.110.120? ([129.215.110.120]) by mx.gmail.com with ESMTP id d74sm1458009wra.2005.04.08.02.50.54; Fri, 08 Apr 2005 02:50:55 -0700 (PDT) In-Reply-To: Original-To: Johan Vromans X-Mailer: Apple Mail (2.619.2) 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:35750 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:35750 On 8 Apr 2005, at 10:17, Johan Vromans wrote: > Also, I think the number of widgets that emacs will use is rather > limited. Using a UI toolkit represents a long-term commitment. Given that UI toolkits seem to live in a fashion-driven biosphere, it might be interesting to consider alternatives. How about documenting interfaces for the most commonly used functions, starting with tasks where a good GUI would be helpful? For example, one could define a structured language to serialize customization settings, which could then be parsed by little external modules - written by the community or the port people in order to implement system-native behavior. This would not preclude the use of the default behavior, i.e. customization buffers. I understand (and I know very little about the technical side of emacs!) that custom options have such an API anyways - it would come down to defining a serialization (to write stuff into a file and read it out again) and an update protocol.