From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Alin Soare Newsgroups: gmane.emacs.devel Subject: Re: Tabs are ready? Date: Thu, 2 Feb 2012 13:54:13 +0200 Message-ID: References: <87hazaf2mf.fsf@mail.jurta.org> <4F2A6EBD.6050800@gmx.at> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=bcaec5299589e04b3004b7f9da51 X-Trace: dough.gmane.org 1328183668 15978 80.91.229.3 (2 Feb 2012 11:54:28 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 2 Feb 2012 11:54:28 +0000 (UTC) Cc: Juri Linkov , Emacs Dev To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 02 12:54:26 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RsvFB-0002Fb-9h for ged-emacs-devel@m.gmane.org; Thu, 02 Feb 2012 12:54:25 +0100 Original-Received: from localhost ([::1]:59097 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RsvFA-00081X-Jj for ged-emacs-devel@m.gmane.org; Thu, 02 Feb 2012 06:54:24 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:58003) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RsvF1-000816-VJ for emacs-devel@gnu.org; Thu, 02 Feb 2012 06:54:21 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RsvF0-0006nj-R8 for emacs-devel@gnu.org; Thu, 02 Feb 2012 06:54:15 -0500 Original-Received: from mail-iy0-f169.google.com ([209.85.210.169]:48581) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RsvF0-0006n4-Kt for emacs-devel@gnu.org; Thu, 02 Feb 2012 06:54:14 -0500 Original-Received: by iagz16 with SMTP id z16so3998566iag.0 for ; Thu, 02 Feb 2012 03:54:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VUb9tZ3dtkQwhswE9XAw30/TAcGXw1JGP2D2+XUyBI4=; b=B1hQygAx3G7XAdJfeNdp6ncElzuzynxHZDyr0ZDfEZ5+Bnkwc7ZWIbPBpHWQi6JT1m R0pLbz1IYk91lbaSkAoExgzeXGkCuFtjwH3/9rej2npXN9ZvI4Lhgh/3n98d72YgAo5U XDv3R7VNwZawMNWaZ3ZbFMtABIfrEyPvAKRFE= Original-Received: by 10.43.53.1 with SMTP id vo1mr2956066icb.2.1328183653714; Thu, 02 Feb 2012 03:54:13 -0800 (PST) Original-Received: by 10.231.42.209 with HTTP; Thu, 2 Feb 2012 03:54:13 -0800 (PST) In-Reply-To: <4F2A6EBD.6050800@gmx.at> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 209.85.210.169 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:148116 Archived-At: --bcaec5299589e04b3004b7f9da51 Content-Type: text/plain; charset=UTF-8 When I wrote them, I tried a few possibilities, but I remember I inserted them in the struct of a frame. In any case, a tab shoud be able to respond to events, and each event must be defined by a lisp function. This is the point where I stopped. I finished only the creation/deletion/ basic functions for tabs, and I inserted some simple events, like hide tab, or show tab, and did not continue any more. Whatever implementation will be , it must define the events as elisp functions ; even after the creation of a tab, there must be an event that calls a lisp function. In this manner, we will be able to have a lots of functionalities implemented as tabs. There can be defined lots of patterns for tabs. 2012/2/2 martin rudalics > > Wouldn't it be easier to implement tabs now with the help of Martin's > side windows? > > It depends on what "tabs" stands for and how many "tabs" we want to show > on any frame: If we want per-window tabs, atomic windows should be used. > If we want per-frame tabs, side windows could be used. > > martin > --bcaec5299589e04b3004b7f9da51 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

When I wrote them, I tried a few possibilities, but I r= emember I inserted them in the struct of a frame.

= In any case, a tab shoud be able to respond to events, and each event must = be defined by a lisp function.

This is the point where I stopped.

=
I finished only the creation/deletion/ basic functions for tabs, and I= inserted some simple events, like hide tab, or show tab, and did not conti= nue any more.

Whatever implementation will be , it must define the ev= ents as elisp functions ; even after the creation of a tab, there must be a= n event that calls a lisp function.

In this manner= , we will be able to have a lots of functionalities implemented as tabs. Th= ere can be defined lots of patterns for tabs.





2012/2/2 martin rudalics <rudalics@gmx.at>
> Wouldn't it be easier to implement tabs now with= the help of Martin's side windows?

It depends on what "tabs" stands for and how many "tabs"= ; we want to show
on any frame: If we want per-window tabs, atomic windows should be used. If we want per-frame tabs, side windows could be used.

martin

--bcaec5299589e04b3004b7f9da51--