Return-Path: 
 <forrest-dev-return-6482-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org
Received: (qmail 28033 invoked by uid 500); 30 Jul 2003 12:03:58 -0000
Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:forrest-dev-help@xml.apache.org>
list-unsubscribe: <mailto:forrest-dev-unsubscribe@xml.apache.org>
list-post: <mailto:forrest-dev@xml.apache.org>
Reply-To: forrest-dev@xml.apache.org
Delivered-To: mailing list forrest-dev@xml.apache.org
Received: (qmail 28022 invoked from network); 30 Jul 2003 12:03:57 -0000
Received: from grunt21.ihug.com.au (203.109.249.141)
  by daedalus.apache.org with SMTP; 30 Jul 2003 12:03:57 -0000
Received: from p250-apx1.syd.ihug.com.au (expresso.localdomain)
 [203.173.140.250]
	by grunt21.ihug.com.au with esmtp (Exim 3.35 #1 (Debian))
	id 19hpgT-0004su-00; Wed, 30 Jul 2003 22:03:57 +1000
Received: from jeff by expresso.localdomain with local (Exim 3.35 #1 (Debian))
	id 19hpnG-0001i3-00
	for <forrest-dev@xml.apache.org>; Wed, 30 Jul 2003 22:10:58 +1000
Date: Wed, 30 Jul 2003 22:10:58 +1000
From: Jeff Turner <jefft@apache.org>
To: forrest-dev@xml.apache.org
Subject: Re: [patch] 'process' and 'raw' content directories
Message-ID: <20030730121058.GF4901@expresso.localdomain>
Mail-Followup-To: forrest-dev@xml.apache.org
References: <1059342813.3f2449ddc3f82@secure.solidusdesign.com>
 <1059511258.3f26dbdaa1ca2@secure.solidusdesign.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1059511258.3f26dbdaa1ca2@secure.solidusdesign.com>
User-Agent: Mutt/1.5.4i
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On Tue, Jul 29, 2003 at 04:40:58PM -0400, Dave Brondsema wrote:
> Quoting Dave Brondsema <dave@brondsema.net>:
> 
> > This patch is so that content/raw and content/process directories are
> > used rather than content/ and content/xdocs.  It uses <sync> where
> > possible (more
> > 
> > than before).  It does not break compatibility with existing
> > projects, unless
> > 
> > they override a xmap file.
> > 
> > I have tested it with static file generation and as a webapp.
> > 
> > Someone should verify that `forrest overrides` and `forrest backcopy`
> > work. 
> > 
> > I don't have a project here that overrides xmap files.  I think that
> > 'backcopy' did not and still does not handle 'status.xml' and
> > 'skinconf.xml' properly.
> > 
> 
> Doesn't anyone have any thoughts about this?  Isn't this the direction
> we want to go?

Hmm, don't know.  FWIW, I thought there was some general consensus to:

 - by default, give full control to the user.  Ie, make 'process' the
   default behaviour.

 - Make 'raw' content specifiable by some external marker, like a
   raw="true" attribute in the site.xml node.  This is a more general,
   fine-grained solution than having a special raw/ directory.

 - Defer the whole problem until 0.5 :)  It's been 5 months since we had
   a release, which is _way_ too long.

> I tested this patch with a project at work and 'forrest overrides'
> works properly.  I don't use backcopy at all so I didn't test that.

Well hang onto that patch, I'm sure we can make use of it eventually.

--Jeff

> -- 
> Dave Brondsema
> dave@brondsema.net
> http://www.brondsema.net - personal
> http://www.splike.com - programming