Return-Path: 
 <user-return-1528-apmail-forrest-user-archive=forrest.apache.org@forrest.apache.org>
Delivered-To: apmail-forrest-user-archive@www.apache.org
Received: (qmail 89671 invoked from network); 4 Jan 2005 11:50:03 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 4 Jan 2005 11:50:03 -0000
Received: (qmail 7380 invoked by uid 500); 4 Jan 2005 11:48:41 -0000
Delivered-To: apmail-forrest-user-archive@forrest.apache.org
Received: (qmail 7256 invoked by uid 500); 4 Jan 2005 11:48:39 -0000
Mailing-List: contact user-help@forrest.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:user-help@forrest.apache.org>
list-unsubscribe: <mailto:user-unsubscribe@forrest.apache.org>
list-post: <mailto:user@forrest.apache.org>
Reply-To: user@forrest.apache.org
Delivered-To: mailing list user@forrest.apache.org
Received: (qmail 7230 invoked by uid 99); 4 Jan 2005 11:48:38 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: domain of sendtoandy@gmail.com
 designates 64.233.170.201 as permitted sender)
Received: from rproxy.gmail.com (HELO rproxy.gmail.com) (64.233.170.201)
  by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 04 Jan 2005 03:48:28 -0800
Received: by rproxy.gmail.com with SMTP id i8so26883rne
        for <user@forrest.apache.org>; Tue, 04 Jan 2005 03:48:24 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
        b=U+F+Sap8ayMjuHnborBHmBxUe1OF3co18CduvuXQi0SRj4P2PZwGEIsEhRQiyclfLJGzWTaIU7qzojVFtW5dcnvIqxyKxJWkDh9bp96wycz+Cetu3SOAHCOHZhrmE2sT7TdFsI6JXvVE/NYyux/gs7D/kwf7fj3T87Y9GcW92LI=
Received: by 10.39.2.49 with SMTP id e49mr46982rni;
        Tue, 04 Jan 2005 03:41:44 -0800 (PST)
Received: by 10.38.75.59 with HTTP; Tue, 4 Jan 2005 03:41:44 -0800 (PST)
Message-ID: <833b4fb605010403412295b978@mail.gmail.com>
Date: Tue, 4 Jan 2005 06:41:44 -0500
From: Andy J <sendtoandy@gmail.com>
Reply-To: Andy J <sendtoandy@gmail.com>
To: user@forrest.apache.org
Subject: Re: Aggregator Recipe Request
In-Reply-To: <41D9B75B.90604@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <833b4fb6050103034974b572ec@mail.gmail.com>
	 <41D9A867.9050606@apache.org> <41D9B75B.90604@apache.org>
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Thanks - I'll keep hacking it using your suggestion.  I had already
added the directory generator for the content but I can see your idea
wrt to getting this into the tabs.xml file.

On Mon, 03 Jan 2005 21:21:31 +0000, Ross Gardler <rgardler@apache.org> wrote:
> Ross Gardler wrote:
> > Andy J wrote:
> >
> >> Has anyone done something to populate a tab from an aggregation of
> >> files in a directory?  I read in the documentation
> >> (http://forrest.apache.org/docs/linking.html#menu_generation) about
> >> using an alternative tab generation method to select by directory -
> >> but I don't want that methodology for every tab, just one.  That is,
> >> what I'm trying to do is have one tab that gets its entries from all
> >> the files in a certain directory, e.g.:
> >>
> >> <foolist label="Foos" href="foos/" tab="foolist">
> >>     <!-- picks up all entries in foos/ and does their transformation
> >> as per the pipeline -->
> >>     <summary label="Summary" href="foos/"/>
> >> </foolist>
> >>
> >> If I understand the documentation, it's pretty clear on how to create
> >> a pipeline for processing the object files themselves into XML but I'm
> >> not sure how I'd go about getting the tab setup.
> >>
> >> Could anyone offer anything with the tabs and/or sitemap entry?
> >
> >
> > This is not currently possible, although it has been discussed before as
> > a possible enhancement. If you fancy having a go at creating this
> > functionality that would be cool. Here are a few pointers:
> >
> > - tab.xml is processed in tabs.xmap
> > - cocoon provides a directory generator
> > http://cocoon.apache.org/2.1/userdocs/generators/directory-generator.html
> >
> > Try something like:
> >
> >
> >         <map:select type="exists">
> >           <map:when test="{project:content.xdocs}tabs.xml">
> >             <!-- process as per current behaviour -->
> >           </map:when>
> >           <map:otherwise>
> >             <!-- use directory generator to read directory, transform
> > with XSL an serialise -->
> >           </map:otherwise>
> >         </map:select>
> 
> Just realised this is too simple, I'm rushing to get through mail
> backlogs and not thinking it through properly. The above will only
> create the <!-- picks up all entries in foos/ and does their
> transformation as per the pipeline --> part of your requirement. It will
> not allow you to include this in an existing tabs.xml file. In order to
> do this you need to have the tabs.xml file include the relevant entries.
> The best way to do this would be to use XInclude so you would have
> something like:
> 
> <xi:include href="do/generateDirTabs/ROOT_DIR"/>
> 
> Then use the cocoon directory generator linked to above to generate the
> XML file to be included at this point.
> 
> Note that this is well beyond the scope of the user mail list, this is
> now developer stuff. If you want to pursue this further please move the
> discussion to the dev list.
> 
> Ross
> 
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.300 / Virus Database: 265.6.8 - Release Date: 03/01/2005
> 
>