Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 82087 invoked by uid 500); 26 May 2003 12:28:09 -0000 Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: forrest-dev@xml.apache.org Delivered-To: mailing list forrest-dev@xml.apache.org Received: (qmail 82078 invoked from network); 26 May 2003 12:28:09 -0000 Received: from grunt23.ihug.com.au (203.109.249.143) by daedalus.apache.org with SMTP; 26 May 2003 12:28:09 -0000 Received: from p639-apx1.syd.ihug.com.au (expresso.localdomain) [203.173.142.131] by grunt23.ihug.com.au with esmtp (Exim 3.35 #1 (Debian)) id 19KH5D-0007mc-00; Mon, 26 May 2003 22:28:07 +1000 Received: from jeff by expresso.localdomain with local (Exim 3.35 #1 (Debian)) id 19KH7W-0002TC-00 for ; Mon, 26 May 2003 22:30:30 +1000 Date: Mon, 26 May 2003 22:30:30 +1000 From: Jeff Turner To: forrest-dev@xml.apache.org Subject: Re: [USER POLL/VOTE] Defining tabs? Message-ID: <20030526123030.GB6029@expresso.localdomain> Mail-Followup-To: forrest-dev@xml.apache.org References: <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> <20030526104426.GA6029@expresso.localdomain> <3ED20089.8050203@apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3ED20089.8050203@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 01:54:49PM +0200, Nicola Ken Barozzi wrote: > > Jeff Turner wrote, On 26/05/2003 12.44: > > >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 elements can now have a @id identifier. > > - When rendering tabs, book2menu.xsl will render as "selected" the > > whose @id is equal to the site.xml @tab. > > It basically makes tabs work as now, but using the site.xml structure > instead of the directory structure. Yes, it's just a different tab selection mechanism. > Wouldn't it work equally well if we simply show the children of a > site:xxx link in tabs.xml instead of the dir ones? It would even be less > changes for the users, but maybe I'm missing something. Sorry I'm not following. "children of a site:xxx link in tabs.xml"? > >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. > > Excellent. > > >Will commit tomorrow'ish.. > > TIA > > What about the tabs.xml-site.xml dichotomy? Could we just make it so > that if tabs.xml is not defined, we can instead use a section in > site.xml? Sounds good. It follows the general pattern established by site.xml overriding book.xml. --Jeff