Return-Path: 
 <forrest-dev-return-5824-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org
Received: (qmail 32920 invoked by uid 500); 28 May 2003 09:18:22 -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 32907 invoked from network); 28 May 2003 09:18:21 -0000
Received: from grunt23.ihug.com.au (203.109.249.143)
  by daedalus.apache.org with SMTP; 28 May 2003 09:18:21 -0000
Received: from p705-apx1.syd.ihug.com.au (expresso.localdomain)
 [203.173.142.197]
	by grunt23.ihug.com.au with esmtp (Exim 3.35 #1 (Debian))
	id 19Kx4q-0004Ci-00; Wed, 28 May 2003 19:18:32 +1000
Received: from jeff by expresso.localdomain with local (Exim 3.35 #1 (Debian))
	id 19Kx7A-0000ZS-00; Wed, 28 May 2003 19:20:56 +1000
Date: Wed, 28 May 2003 19:20:56 +1000
From: Jeff Turner <jefft@apache.org>
To: forrest-dev@xml.apache.org, nicolaken@apache.org
Subject: Re: [USER POLL/VOTE] Defining tabs?
Message-ID: <20030528092056.GA1189@expresso.localdomain>
Mail-Followup-To: forrest-dev@xml.apache.org, nicolaken@apache.org
References: <3EC51A32.5060901@che-che.com> <3EC60229.90900@apache.org>
 <3EC98320.3030409@che-che.com> <3ED1BC65.2060607@apache.org>
 <20030526104426.GA6029@expresso.localdomain> <3ED20089.8050203@apache.org>
 <20030526123030.GB6029@expresso.localdomain> <3ED2297D.1070109@apache.org>
 <20030527102923.GB2520@expresso.localdomain> <3ED363D2.1060308@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3ED363D2.1060308@apache.org>
User-Agent: Mutt/1.5.3i
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On Tue, May 27, 2003 at 03:10:42PM +0200, Nicola Ken Barozzi wrote:
> 
> Jeff Turner wrote, On 27/05/2003 12.29:
> >On Mon, May 26, 2003 at 04:49:33PM +0200, Nicola Ken Barozzi wrote:
...
> >Now we've got this node.  We need to discover the associated tab.
> 
> Wait a sec... eh? I mean, that node *is* the associated tab, no?
> 
>   <tab sitepath="about/download"/>
> 
> means we find in site.xml the node
> 
>   //site/about/download
> 
> and render from there all the below elements.

Yes, but that's not the problem.  The problem is, how do we know we're in
the about/download tab?  We have to infer the current tab from the
current path.

Say our current path is "about/download/binaries/index.html".  This path
belongs to the "about/download" tab.  How can we know that?  What's the
algorithm in tab2menu.xsl?

Anyway, just to clarify: technical details aside, I agree with what
you're suggesting for tabs; it's just that the only implementation I can
see is an under-the-covers emulation of the @tab-in-site.xml solution.

--Jeff

> -- 
> Nicola Ken Barozzi                   nicolaken@apache.org
>             - verba volant, scripta manent -
>    (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
>