From bert@vankets.com Wed Jun 5 11:43:00 2002 Return-Path: Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list forrest-dev@xml.apache.org Received: (qmail 85925 invoked from network); 5 Jun 2002 11:43:00 -0000 Received: from mail.hospitable.be (HELO relay.hospitable.be) (212.35.122.81) by daedalus.apache.org with SMTP; 5 Jun 2002 11:43:00 -0000 Received: from beke2000.vankets.com (adsl-60028.turboline.skynet.be [217.136.106.124]) by relay.hospitable.be (Postfix) with ESMTP id AFEE3A1746 for ; Wed, 5 Jun 2002 13:40:46 +0200 (CEST) Message-Id: <5.1.0.14.0.20020605134258.039e31b8@mail.visitronics.be> X-Sender: postmaster.vankets@mail.visitronics.be X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 05 Jun 2002 13:45:01 +0200 To: forrest-dev@xml.apache.org From: Bert Van Kets Subject: RE: Tabs In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > > > As Steven proposed I'm using the same technology as the menu > > system. I > > added a **top-**.xml pipeline to teh sitemap, a top.xml file > > in the xdocs > > directory and a top2xhtml.xsl to the skin stylesheet/html directoy. > > The top.xml file contains entries much like the menu system. > > I'm using a > > label and a dir attribute do link a sub-directory to a tab. Every > > directory in the tab sub-directory will activate the tab too. > > Very simple, > > easily maintainable and proven system. > >This is exactly what I've proposed a while ago - to use a special markup for >the 'global-path' and 'tabs' (I think that you'll see it if you take a look >at the sample that I've sent to you, except for the syntax - I prefer >'*/top/*'-like notation in sitemap). indeed, the way these things are linked is the same to me I'll change it. >And I'd call it 'tabs.xml' instead - it'd be more obsious for a reader. Good point. Will do. > > > > > > >A while ago were proposed a site.xml (or it was index.xml?) > > that would carry > > >all the needed things for either the 'global-path' (apache > > > xml.apache > > > >project) or the tabs, menus, etc - something like a topic > > map, but nothing > > >yet done in that direction. > > > > hmm, that would need to span the WHOLE site. The menu system > > of every > > project would need to be in there. Unless there's a site.xml > > per project I > > don't see how this could be maintained. > > I think a site.xml file should only contain the top path > > entries, like the > > top.xml file contains the tab entries. > > This way the structure is split up in three levels: > > site.xml : site path at the top of the page > > top.xml (1 per project) : tabs content > > book.xml (1 per directory) : menu content. > >Not bad idea. Thanks > > > > > > >Regarding the path: you can use a sitemap parameter and pass > > it to your > > >stylesheet. But I think that we must find a better solution > > without a need > > >to specify the context directory. > > > > The data is already in Ant. I just need a way to access it. > >If you use Ant for it then you'll have to rebuild the site for every >possible deployment locations. Yes, but I don't see another solution. Do you? > > AFAIK I can't > > use the sitemap since it resides in the forrest directory. Any other > > suggestions? > >Don't see how this can be a problem? I have to look at it closer. Thanks. Bert >Konstantin > > > > > Bert > > > > > > >Konstantin > > > > > > > > > > > Bert > > > > > > > > This mail is written in 100% recycled electrons. > > > > > >