Return-Path: 
 <forrest-dev-return-5792-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org
Received: (qmail 68717 invoked by uid 500); 26 May 2003 10:42:09 -0000
Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:forrest-dev-help@xml.apache.org>
list-unsubscribe: <mailto:forrest-dev-unsubscribe@xml.apache.org>
list-post: <mailto:forrest-dev@xml.apache.org>
Reply-To: forrest-dev@xml.apache.org
Delivered-To: mailing list forrest-dev@xml.apache.org
Received: (qmail 68708 invoked from network); 26 May 2003 10:42:08 -0000
Received: from grunt21.ihug.com.au (203.109.249.141)
  by daedalus.apache.org with SMTP; 26 May 2003 10:42:08 -0000
Received: from p639-apx1.syd.ihug.com.au (expresso.localdomain)
 [203.173.142.131]
	by grunt21.ihug.com.au with esmtp (Exim 3.35 #1 (Debian))
	id 19KFQb-00049K-00; Mon, 26 May 2003 20:42:06 +1000
Received: from jeff by expresso.localdomain with local (Exim 3.35 #1 (Debian))
	id 19KFSs-0001jG-00
	for <forrest-dev@xml.apache.org>; Mon, 26 May 2003 20:44:26 +1000
Date: Mon, 26 May 2003 20:44:26 +1000
From: Jeff Turner <jefft@apache.org>
To: forrest-dev@xml.apache.org
Subject: Re: [USER POLL/VOTE] Defining tabs?
Message-ID: <20030526104426.GA6029@expresso.localdomain>
Mail-Followup-To: forrest-dev@xml.apache.org
References: <3EC33423.10003@apache.org>
 <20030515121802.GC4404@expresso.localdomain> <3EC4E51C.4000206@che-che.com>
 <3EC4E784.2030004@apache.org> <3EC501B6.60308@che-che.com>
 <3EC51539.10108@apache.org> <3EC51A32.5060901@che-che.com>
 <3EC60229.90900@apache.org> <3EC98320.3030409@che-che.com>
 <3ED1BC65.2060607@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3ED1BC65.2060607@apache.org>
User-Agent: Mutt/1.5.3i
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On Mon, May 26, 2003 at 09:04:05AM +0200, Nicola Ken Barozzi wrote:
...
> What Jeff has proposed is the best IMHO. It can accomodate a skin that 
> allows tabs to show things at the skin's wish. We'll see if the impl 
> will be nice enough for users.

I have something implemented locally:

 - Any site.xml node can have a @tab attribute.
 - @tab attributes are like namespaces: they are inherited by child
   site.xml nodes unless overridden by a child's @tab.
 - tabs.xml <tab> elements can now have a @id identifier.
 - When rendering tabs, book2menu.xsl will render as "selected" the <tab>
   whose @id is equal to the site.xml @tab.

So, pretty simple and generic.  As for the
are-tabs-bookmarks-or-containers debate, it becomes a one-line change in
tabutils.xsl, which I'll parametrize and set to 'containers' by default.

Will commit tomorrow'ish..


--Jeff


> >PS. The fact that red and green does not mix together well does not mean 
> >that we should removed both colors. :-)
> 
> ;-)
> 
> -- 
> Nicola Ken Barozzi                   nicolaken@apache.org
>             - verba volant, scripta manent -
>    (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
>