forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicola Ken Barozzi <>
Subject Re: Where to put additional stuff in the Forrest CVS?
Date Sat, 09 Nov 2002 12:18:29 GMT

David Crossley wrote:
> Jeff Turner wrote:
>>Steven Noels wrote:
>>>Nicola Ken Barozzi wrote:
>>>>I have xsl files to transform Maven-like DTDs to Forrest DTD, with their 
>>>>own ant buildfile, and I happened to be puzzeled over where to commit them.
>>>Those would be used by CAP pipelines which we will implement for a 
>>>customer after the GetTogether.
>>>>Under src/resources we have resources like /library, charts, etc/, but 
>>>>basically "modules" like /editor, forrestbar, and now conversion/.
>>>How about src/resources/library/xslt ?
>>>Or maybe have a semantical grouping underneath, like:
>>>                           maven
>>>                           docbook
>>>                           wiki
>>>                           util
>>>                           forrest
>>There is typically only one *2document.xsl stylesheet per format..
> I would rather the grouping idea. Sometimes there will be
> a multi-stage conversion. Cocoon (a.k.a document-v10) has
> a few already in /xslt/ i.e. changesv10tochangesv11.xsl,
> docv10todocv11.xsl, faqv10tofaqv11.xsl
> Such stylesheets are specifically for a certain purpose,
> so it seems better to me to have src/resources/convert
> with type-specific sub-dirs to hold all of their resources,
> e.g. /maven/*.xsl, /maven/build.xml, etc.). Otherwise
> we will need strange filenames to distinguish each.

I think I'll go with



and add the convert dir to the ones copied in the webapp.

So it's easy to understand how to convert stuff statically with the 
buildfile in the convert dir, while keeping the possibility of using the 
files dynamically in Forrest.

Nicola Ken Barozzi         
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)

View raw message