On Fri, Dec 27, 2002 at 07:54:53AM -0500, Berin Loritsch wrote: > > From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]] > > > > Paul Hammant wrote: > > > Folks, > > > > > > Have we chosen a xdocs->html technology for the avalon-site depot? > > > > > > Forrest, Anakia, Cocoon? > > > > Given that Forrest is to prefer to plain Cocoon since it's > > Cocoon based > > but tailored for our use, and that the only one holding back IIRC on > > Anakia has since then decided to use Forrest (see Phoenix docs), I'd > > choose Forrest. > > As long as it works, I am +1. > > Does Forrest have good documentation on getting it to work and installed? > > That is my concern. If we offload the tools to a third party, I don't > want to have to wrestle with the tool we choose. Maven is a *build* tool, > and from what I understand, can delegate to Forrest for doc generation. > So as long as it is made **really*easy** for the user to get up and running, > I am behind it.
Forrest is pretty easy to install and get running. Just add bin/ to your path, and type 'forrest' in the project directory. Only problem is, Forrest is quite a large download (13mb), more than I'd expect casual users to get to make a small doc patch. One compromise is to add the DTDs in CVS, and enough Ant machinery to validate the xdocs. Then if './build.sh validate' succeeds, the docs can be safely checked in. After all, XML's main advantage is content/style independence, so there should be no need to view the HTML (requiring Forrest) to edit the content. For people requiring more visual feedback than an XML editor gives, we have a bunch of Forrest projects being updated every hour at http://forrestbot.cocoondev.org/ The DTDs and Ant 1.6 validation stuff adds about 1.5mb to CVS. --Jeff -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
