forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cyriaque Dupoirieux <>
Subject Re: svn commit: r366100 - in /forrest/trunk/main: fresh-site/ template-sites/basic/ template-sites/benchmark/ template-sites/business/ template-sites/v3/forrest.properti
Date Thu, 05 Jan 2006 15:14:10 GMT
Tim Williams a écrit :

>On 1/5/06, Ross Gardler <> wrote:
>> wrote:
>>>Author: crossley
>>>Date: Wed Jan  4 23:01:23 2006
>>>New Revision: 366100
>>>Use minimal files.
>>>    forrest/trunk/main/fresh-site/
>>>    forrest/trunk/main/template-sites/basic/
>>>    forrest/trunk/main/template-sites/benchmark/
>>>    forrest/trunk/main/template-sites/business/
>>>    forrest/trunk/main/template-sites/v3/
>>I'm not sure this is a good idea. Many users discover how to change
>>things in Forrest by reading this document from their seeded site.
>>If we are going to go for a minimal version like this (which certainly
>>looks less scary) we need a doc to detail the changes that are possible,
>>and we need the minimal file to point to that doc.
>I prefer having the beefier properties file vs minimal pointing to a
>detailed doc.  I liken our properties file to httpd.conf where I would
>be lost if they didn't have all of the directives in there commented
>out and well-described.  I also suspect this will lead new folks to
>making changes to webapp\ because that's
>where they happen to see the keys they want to change.  At least those
>of us who follow the LBPA (learn by poking around) method.
I also agree, It's a little bit like commented java or xsl sources is 
better than separated long design document...
(But separated doc is also needed ;-) )


View raw message