forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Turner <>
Subject Re: Forrest: dynamic or static?
Date Mon, 22 Sep 2003 13:06:53 GMT
On Mon, Sep 22, 2003 at 06:21:12AM -0600, Antonio Gallardo wrote:
> >> > - Lucene integration.  As it exists in CVS, it screws up statically
> >> >   rendered sites, so is disabled.
> I think it would be disabled by default as the google feature currently
> is. Let the user decide to use one of them, or none. The idea of both
> sounds weird, Then we can join them in just one property. Is this correct?

That's how I saw it working.  Search on or off.  If on, google or lucene:


> I am in favor including Lucene. I think any documentation project must
> have a searching tool. For online sites we have "google search", for
> Intranets Lucene is a good candidate to do the job. Can someone point to
> another solution in this area? (Not ironic, is really a question). I saw
> the idea of htDig, but I dont see this a good idea at all.

Lucene search is great feature, and I'm keen to see it in Forrest once
the bug that causes it to break offline sites' builds is fixed.

> >> Being a Cocoon distribution, there is a huge amount of stuff that
> >> Forrest *could* include.  I think we need to draw a line, define what
> >> Forrest actually is, and stick to that.
> I dont see it totally black or white. We must concentrate in what is good
> for writing documentation. That is the goal of Forrest at all. Of course
> we can find a case for every cocoon stuff that can be related to writing
> docs (even remotely). But this is not the point.



> Best Regards,
> Antonio Gallardo

View raw message