Return-Path: 
 <forrest-dev-return-5922-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org
Received: (qmail 73450 invoked by uid 500); 12 Jun 2003 12:37:35 -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 73361 invoked from network); 12 Jun 2003 12:37:34 -0000
Received: from pegase1.c-s.fr (HELO pegase1.cie-signaux.fr) (194.2.40.7)
  by daedalus.apache.org with SMTP; 12 Jun 2003 12:37:34 -0000
Received: from pegase0.si.c-s.fr
        by pegase1.cie-signaux.fr  with ESMTP id OAA22245
        for <forrest-dev@xml.apache.org>;
 Thu, 12 Jun 2003 14:37:33 +0200 (MET DST)
Received: from pegase0.si.c-s.fr
  by pegase0.si.c-s.fr  with ESMTP id OAA05931
  for <forrest-dev@xml.apache.org>; Thu, 12 Jun 2003 14:35:51 -0100 (GMT)
Received: from hermes19.si.c-s.fr
  by pegase0.si.c-s.fr  with ESMTP id OAA05912
  for <forrest-dev@xml.apache.org>; Thu, 12 Jun 2003 14:35:48 -0100 (GMT)
Received: from c-s.fr ([172.17.52.218]) by hermes19.si.c-s.fr
          (Netscape Messaging Server 4.15) with ESMTP id HGDCEE00.IYH for
          <forrest-dev@xml.apache.org>; Thu, 12 Jun 2003 14:37:26 +0200
Message-ID: <3EE87320.1030909@c-s.fr>
Date: Thu, 12 Jun 2003 14:33:36 +0200
From: "MAISONOBE Luc" <luc.maisonobe@c-s.fr>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.3) Gecko/20030507
X-Accept-Language: fr, en
MIME-Version: 1.0
To: forrest-dev@xml.apache.org
Subject: Re: Cleaning Forrest source directory madness
References: <3EE862C4.6060207@apache.org>
In-Reply-To: <3EE862C4.6060207@apache.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Nicola Ken Barozzi wrote :

> Scenario A (multiple dirs)
> 
>   content        all stuff to be "digested" by Forrest
>     xdocs        xml document-dtd files
>     html         html files
>     wiki
>     ...
>   resources      all stuff to be referenced as-is
>     images
>     scripts
>     styles
>     files
>     ...
>   global         all stuff to be referenced as-is and is always relative
>     images
>     scripts
>     styles
>     files
>     ...
> 
> Scenario B (single dirs)
>   content        all stuff to be "digested" by Forrest
>    <here goes mixed content>
>   resources      all stuff to be referenced as-is
>    <here goes mixed resources>
>   global         all stuff to be referenced as-is and is always relative
>    <here goes mixed global>

The more I think about it, the more I prefer scenario B.

Scenario A means directories have three different roles depending on 
their level. The first level (content vs. resources vs. global) 
specifies forrest-related features, mainly what the tool should do with 
the files. The second level (images vs. scripts vs. styles vs. files vs. 
anything else) specifies file types which is probably more a 
site-maintainer oriented feature to help him keep things clean, which is 
often a matter of taste and different for everyone. The third and deeper 
levels specify target site file structure, which is often a mapping of 
the navigation logic on the target site and hence oriented toward site 
users. These roles seem too interlaced (is it english ?, should I say 
interwoven or intertwin ?) and they assign different meanings to one 
mechanism: file hierarchy.

The upper level (content vs. resources vs.global), which is the same in 
both proposals seems fine to drive forrest behaviour.

File type organisation, IMHO, should be let to the user and be at the 
lowest level.

Target site structure, should probably not be specified here. Isn't the 
site.xml file specifically designed for that ? Couldn't this file take 
care of all this structuring (including resources and global) and be 
moved up in the hierarchy (at the same level as content, resources and 
global, or above, next to status.xml ? By the why is this status.xml 
file this high in the directory tree ?

                                                             Luc