forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Turner <je...@apache.org>
Subject Re: Short-term plans (Re: Xindice going to forrest)
Date Wed, 09 Oct 2002 13:49:56 GMT
On Wed, Oct 09, 2002 at 05:10:12PM +0400, Piroumian Konstantin wrote:
> > From: Jeff Turner [mailto:jefft@apache.org] 
> > On Wed, Oct 09, 2002 at 02:18:59PM +0200, Steven Noels wrote:
> > > Jeff Turner wrote:
> > > 
> > > >If you need any help or advice, there's a list of people 
> > very willing 
> > > >to help.
> > > 
> > > doesn't everybody hears Jeff volunteering to document shbat 
> > & seeding? 
> > > ;-)
> > 
> > He certainly will, soon as build.build.xml becomes build.xml. 
> > If there's no objections (there were two +1's) I'll do it all 
> > tomorrow.
> > 
> > Then.. what needs to happen before a 0.2 release?
> > 
> > Would it be a good idea to roll back the input modules patch 
> > for 0.2? Some reasons:
> >  - It's not yet configurable from the forrestbot, which I gather is
> >    breaking the outerthought sites?
> 
> What's the problem here? Won't your XMLModule solve this problem?

Yes, but first we'd have to implement the agreed-upon 'chaining' system
in Cocoon. Also, people are right now busy fiddling with the input module
API. If we release Forrest 0.2 relying on input modules, it is unlikely
to work with Cocoon a month from now. Also, it requires pulling apart the
forrestbot to use the new config mechanism.

> >  - There's an annoying Cocoon bug[1] that virtually prevents use of a
> >    'live' Forrest webapp. Any edit to the sitemap kills Cocoon.
> 
> I'll try to find time today evening to investigate the cause.

There's a patch in the bug report that seems to work, but it needs
reviewing.

> > Input modules are undoubtedly the way to go in the future though. I
> > especially like them because they're vital to 'in-place' Forrest
> > operation (where you don't copy docs into build/*).
> 
> Ok, no serios objections here, except that I don't like seeing Ant tokens in
> the sitemap.

Absolutely. But we know there's a better solution coming, so they're not
too hard to ignore :)

> And it's only the 0.2 version of Forrest, so I hope until the Forrest 1.0 is
> released Cocoon will stabilize a little and we'll be able to cleanup again
> the sitemap (and the next thing to do is to split it into subsitemaps).

Yes, it would be great if we could hide all the component configurations
in a parent sitemap.

> > Konstantin?
> 
> Yes, I am.

Good for you ;)

--Jeff

> Konstantin ;)
> 
> > [1] http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11518

Mime
View raw message