forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [issues] New comment: (FOR-187) Redefine project documentation dirs
Date Thu, 01 Jan 1970 00:00:00 GMT
The following comment has been added to this issue:

     Author: Nicola Ken Barozzi
    Created: Thu, 10 Jun 2004 4:55 PM
This is a summary and final decision-vote about the new dir structure 
that Forrest will have in version 0.7 .

"Cleaning Forrest source directory madness"

Below is a summary of the results that have come from this thread:


    content -> model
      - files to process (1)
      - files not to process (2)
    resources -> controller
    skins -> view

We would have use definable (KISS)

files to process-dir (1)
files not to process-dir (2)

What can [files to process (1)] contain?

- *.xml   (documentdtd, faq, changes, todo, status, etc)
- *.html  (html4, to be tidied)
- *.xhtml (xhtml1, xhtml2-dev)
- *.wiki
- *.png,gif,etc

The default content dirs 1,2 would be:

    content/*.xml (1)
    content/images/*.png (1)
    content/raw/foo.html (2)

The only special dir that will remain is "raw", and it seems that there 
is a real-life use case for it.

Mind me, we still add a **.* matcher at the end of the
content-handling pipeline, so that content/** can still contain anything 
(ie cocoon can proces it but in this case can also decide to just pass 

But as you know in this way I cannot easily cater for the special case
in which I want to explicitly have something as-is, like for example a
raw document-dtd xml file.

So the content dir is about all content, that Forrest *may* alter.
The raw dir is about content that Forrest may *not* alter in any way.
View the issue:

Here is an overview of the issue:
        Key: FOR-187
    Summary: Redefine project documentation dirs
       Type: Improvement

     Status: Assigned
   Priority: Major

    Project: Forrest
  Component: Core operations
    Fix For: 0.7

   Assignee: Steven Noels
   Reporter: Nicola Ken Barozzi

    Created: Thu, 10 Jun 2004 4:53 PM
    Updated: Thu, 10 Jun 2004 4:53 PM

We should finalize all discussions about where to put sources and extensions in the projects.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message