forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Turner <>
Subject Re: publishing unlinked files
Date Mon, 04 Nov 2002 11:41:26 GMT
On Mon, Nov 04, 2002 at 12:00:19PM +0100, Nicola Ken Barozzi wrote:
> Jeff Turner wrote:
> >On Mon, Nov 04, 2002 at 11:21:37AM +0100, Nicola Ken Barozzi wrote:
> >
> >>Jeff Turner wrote:
> >>
> >>>On Mon, Nov 04, 2002 at 04:50:17AM -0500, Rodent of Unusual Size wrote:
> >>>
> >>>
> >>>>how do i cause forrest to include a file in the build output tree that
> >>>>isn't explicitly linked?  such as a .htaccess file?
> >>>
> >>>Don't know :/
> >>>
> >>>Perhaps we need Forrest pre- and post-targets:
> >>>
> >>>forrest.pre-script=build.xml
> >>>${forrest.pre-script}/prestuff
> >>>
> >>>${}/poststuff
> >>>
> >>>What do people think?
> >>
> >>Cocoon CLI can start crawling from a file containing a list of URLS, we 
> >>should get that working IMHO.
> >
> >
> >That wouldn't help much, as one would need to add a **/.htaccess rule to
> >the sitemap.
> Just add a ** rule at the end of the sitemap with a reader...

That works for .htaccess.  Wouldn't work for copying Javadocs, which is
much the same (unparsed files not linked directly).

> >I could use a pre-script in Anteater, to copy examples/*.xml into the
> >xdocs-dir before it's all rendered..
> Remember the discussion about not having to copy anything?
> How does it fit?

I was thinking.. IoC.. project in control of the overall doc build
process, not Forrest.  

Ideally, Forrest and the sitemap would be completely passive, imposing no
required structure on the project.  The project tells Forrest, "my xdocs
are _here_" and Forrest adjusts the sitemap accordingly, rather than
(current situation) Forrest rearranging the docs to fit with the sitemap.

> Doesn't a "mount" system for external resources work better conceptually?

Yes, probably would for my use-case..

<site dir="src/documentation">
  <examples dir="../../examples/"/>

Then in book.xml, have

<menu-item label="Examples" href="site:/site/examples"/>

But back to the original topic: would adding pre and post callbacks do
harm conceptually?  There's no reason why people can't today create a
build.xml which does preprocessing, invokes Forrest, then does
postprocessing.  That's what I'm doing in Anteater.  I think pre and post
targets would just make it simpler for people without a driving Ant


> Just 2c anyway...
> -- 
> Nicola Ken Barozzi         
>             - verba volant, scripta manent -
>    (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------

View raw message