From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.devel Subject: Re: Infrastructural complexity. Date: Sun, 26 Jul 2009 19:45:02 +0200 Message-ID: <4A6C961E.3030805@gmx.at> References: <20090712180623.GA1009@muc.de> <4A643993.5080302@gmx.at> <87ljmjl9ow.fsf@catnip.gol.com> <4A648E1D.1000007@gmx.at> <877hy3l3kj.fsf@catnip.gol.com> <4A64BF58.4030001@gmx.at> <871vobkny7.fsf@catnip.gol.com> <4A658CD2.8020504@gmx.at> <1248195599.7551.26.camel@dell-desktop.example.com> <4A65FA0E.6020800@gmx.at> <1248200131.7551.75.camel@dell-desktop.example.com> <4A66E607.9030505@gmx.at> <1248280114.7109.33.camel@dell-desktop.example.com> <4A67593D.6020908@gmx.at> <1248289454.7109.47.camel@dell-desktop.example.com> <4A682C53.2080307@gmx.at> <1248375083.15583.9.camel@dell-desktop.example.com> <4A6970B8.7000006@gmx.at> <4A6AC7EA.2010007@gmx.at> <4A6B3CE2.8070404@gmx.at> <4A6C72BE.5080207@gmx.at> <1248628716.5952.11.camel@dell-desktop.example.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1248630336 10662 80.91.229.12 (26 Jul 2009 17:45:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 26 Jul 2009 17:45:36 +0000 (UTC) Cc: rms@gnu.org, cyd@stupidchicken.com, lennart.borgman@gmail.com, joakim@verona.se, emacs-devel@gnu.org, juri@jurta.org, Stefan Monnier , acm@muc.de, drew.adams@oracle.com, Miles Bader To: Thomas Lord Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jul 26 19:45:27 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 1MV7mj-0007hE-Om for ged-emacs-devel@m.gmane.org; Sun, 26 Jul 2009 19:45:22 +0200 Original-Received: from localhost ([127.0.0.1]:60096 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MV7mj-0006yQ-A4 for ged-emacs-devel@m.gmane.org; Sun, 26 Jul 2009 13:45:21 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MV7md-0006vi-Sy for emacs-devel@gnu.org; Sun, 26 Jul 2009 13:45:15 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MV7mY-0006um-DR for emacs-devel@gnu.org; Sun, 26 Jul 2009 13:45:14 -0400 Original-Received: from [199.232.76.173] (port=34190 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MV7mY-0006uj-7K for emacs-devel@gnu.org; Sun, 26 Jul 2009 13:45:10 -0400 Original-Received: from mail.gmx.net ([213.165.64.20]:36037) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1MV7mX-0001tM-HK for emacs-devel@gnu.org; Sun, 26 Jul 2009 13:45:09 -0400 Original-Received: (qmail invoked by alias); 26 Jul 2009 17:45:07 -0000 Original-Received: from 62-47-57-16.adsl.highway.telekom.at (EHLO [62.47.57.16]) [62.47.57.16] by mail.gmx.net (mp071) with SMTP; 26 Jul 2009 19:45:07 +0200 X-Authenticated: #14592706 X-Provags-ID: V01U2FsdGVkX18jc8MAngIj00c43bCGToL/cA4aa6Ed8USeZNeP3t PBSy965RKspa9A User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) In-Reply-To: <1248628716.5952.11.camel@dell-desktop.example.com> X-Y-GMX-Trusted: 0 X-FuHaFi: 0.71 X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. 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:113175 Archived-At: > They are frames. Frames are modified to have a > `parent' slot which may be nil or may be a > frame that itself has a nil `parent'. Then you have to rewrite the frame management code in addition to the window management code. For example, the semantics of both `next-frame' and `next-window' would change. >> decide how they are allowed to >> tile a frame > > Yes. I have one possibility that seems to cover > all of the use cases people commonly want, but > there are other ways to do it, certainly. > >> (which would be mostly a copy of the window making, >> splitting, and deleting code) > > Maybe. There are other possibilities. > It could also be done with something like > the layout engines found in some GUI > toolkits. These would have to be rewritten and adapted accordingly. > It's not clear that much or any changes to > window code would be needed. Perhaps > some changes to `display-buffer'; perhaps > some changes to `buffer-list' that kind > of thing. These would be ways for an elisp > program to limit which buffers are likely to > be displayed in framelets that are used as control > panels. `buffer-list' is not part of the window management code. But what would `window-frame' return? What would the `frame-root-window' of the `window-frame' of a window be? Or `selected-frame'? martin