Return-Path: 
 <forrest-dev-return-8417-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-forrest-dev-archive@www.apache.org
Received: (qmail 40331 invoked from network); 22 Dec 2003 14:50:26 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 22 Dec 2003 14:50:26 -0000
Received: (qmail 43476 invoked by uid 500); 22 Dec 2003 14:50:21 -0000
Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org
Received: (qmail 43292 invoked by uid 500); 22 Dec 2003 14:50:20 -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 43267 invoked from network); 22 Dec 2003 14:50:20 -0000
Received: from unknown (HELO wkwyw.ensim.dedicated-servers.co.uk)
 (217.199.181.91)
  by daedalus.apache.org with SMTP; 22 Dec 2003 14:50:20 -0000
Received: from wkwyw.net (host-64-110-159-97.interpacket.net [64.110.159.97])
	(authenticated (0 bits))
	by wkwyw.ensim.dedicated-servers.co.uk (8.11.6/8.11.6) with ESMTP id
 hBMEuNr14774
	for <forrest-dev@xml.apache.org>; Mon, 22 Dec 2003 14:56:24 GMT
Message-ID: <3FE70494.8000306@wkwyw.net>
Date: Mon, 22 Dec 2003 10:49:56 -0400
From: Ross Gardler <rgardler@wkwyw.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: forrest-dev@xml.apache.org
Subject: Re: Multiple tab.xml files
References: <3FE51343.5010202@wkwyw.net> <3FE5BC93.8040608@wkwyw.net>
 <bs51lm$h8r$1@sea.gmane.org>
In-Reply-To: <bs51lm$h8r$1@sea.gmane.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Nicola Ken Barozzi wrote:

> It has been intentional [only one set of tabs per site]. Tabs should never change during navigation, 
> it's confusing.
> 
> What you may want instead are hierarchical tabs, as seen here:
> http://www.oreillynet.com/

OK I see the value in this.

> Instead of recreating a new file we can easily extend the current 
> tabs.xml, and this *should* make it backward compatible:
> 
> <tabs software="Forrest"
>     title="Apache Forrest"
>     copyright="2002-2003 The Apache Foundation"
>     xmlns:xlink="http://www.w3.org/1999/xlink">
> 
>     <tab id="home" label="Home" dir="">
>       <tab id="a" label="A" dir="a"/>
>     </tab>
>     <tab id="community" label="Community" dir="community"/>
>     <tab id="howto" label="How-to" dir="community/howto">
>       <tab id="b" label="B" dir="b"/>
>     </tab>
> 
>  </tabs>
> 
> As long as we are able to filter //tab/tab elements, also old skins 
> should work, and the new ones can use subtabs.

+1

> But let me add another question: are not tabs part of the site? Then why 
> are they in a separate file?
> 
> My idea was to have top-level nodes of site.xml be the tabs, and a skin 
> could decide at which level switch from tabs to navigation. As some 
> pointed out, tabs are not necessarily containers of pages, but links to 
> pages. Hence they have to remain in a separate hierarchy. This does not 
> mean though that they have to be in a separate file.
> 
> The problem is that we already have a site.xml that needs tabs to be 
> defined outside of the main element, so it would have to change. I would 
> like to get this going later, as it's a big thing to do.

I see a couple of problems with this, but as you say it's a big thing 
overall, so I'll keep them to myself for now.

> So for now making hierarchical tabs possible similarly to what we have 
> now is a very good next step. (we'll have to add the functionality to 
> our skins BTW)

I'll have a go at it ove rthe holidays when I'm board of writing 
(happens alot :-)

I've also tidied up my code to make dynamic webapps work again, I'll 
post a patch as soon as I get some decent bandwidth later today.

Ross