Return-Path: 
 <forrest-dev-return-6096-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org
Received: (qmail 28943 invoked by uid 500); 6 Jul 2003 02:34:12 -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 28932 invoked from network); 6 Jul 2003 02:34:12 -0000
Received: from grunt23.ihug.com.au (203.109.249.143)
  by daedalus.apache.org with SMTP; 6 Jul 2003 02:34:12 -0000
Received: from p39-apx1.syd.ihug.com.au (expresso.localdomain)
 [203.173.140.39]
	by grunt23.ihug.com.au with esmtp (Exim 3.35 #1 (Debian))
	id 19YzM2-0003hR-00; Sun, 06 Jul 2003 12:34:20 +1000
Received: from jeff by expresso.localdomain with local (Exim 3.35 #1 (Debian))
	id 19YzQz-0000Eg-00
	for <forrest-dev@xml.apache.org>; Sun, 06 Jul 2003 12:39:25 +1000
Date: Sun, 6 Jul 2003 12:39:25 +1000
From: Jeff Turner <jefft@apache.org>
To: forrest-dev@xml.apache.org
Subject: Re: resource directory clarification
Message-ID: <20030706023925.GE672@expresso.localdomain>
Mail-Followup-To: forrest-dev@xml.apache.org
References: 
 <03334AAF1DF8D2119B1000A0C9E32F5803EE2FFD@us-pb-xmsg-2.am.sony.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <03334AAF1DF8D2119B1000A0C9E32F5803EE2FFD@us-pb-xmsg-2.am.sony.com>
User-Agent: Mutt/1.5.4i
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On Wed, Jul 02, 2003 at 10:23:19AM -0700, Farr, Aaron wrote:
> Hello.
> 
> I've been using forrest for a while and we'll now be moving our department
> internal site to forrest, but after reading the documentation and the
> mailing list archives I'm still confused about the purpose of the
> src/documentation/resources directory.

Resources are things that are necessary for rendering the site, but not
directly displayed themselves (not content).

Examples of server-side resources are XSLT stylesheets and custom DTDs.
Examples of client-side resources are Javascript and CSS files.

I would say that images are content, not resources, and that they are
incorrectly classified currently.  There is a historical reason [1] for
this; we'll fix it in Forrest 0.6.

> General question is should these sort of directories:
>   /images
>   /scripts
>   /style

In Forrest 0.4 and 0.5, you would use:

src/documentation/resources/images
src/documentation/resources/scripts
src/documentation/resources/css

>   ...
> reside in /resources or in /content.
> 
> My first impression is that they belong in /resources, but if I understand
> correctly that requires a patch to work correctly.  Is there a consensus on
> this?  What will forrest 0.5 support?

AFAIK no patch should be necessary for images, *.js and *.css.

HTH,


--Jeff

> Thanks!
> 
> J. Aaron Farr
> � SONY ELECTRONICS
> � DDP-CIM
> � (724) 696-7653


[1] _Originally_, a resource was simply something that could be
referenced from anywhere in the site, with a well-known path.  That is
why images are in resources -- so that you can have <img
src="images/foo.gif"> anywhere in your site, and it will link to the
correct image.

The rationale for the original definition has proven faulty; it's all
very well being able to write <img src="images/foo.gif"> from index.xml
and subdir/index.xml, but then in the output, we'll have two copies of
the image:

foo.gif
subdir/foo.gif

Meaning that browsers can't just cache the image once for the whole site.