forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject AW: Cocoon & Skins
Date Thu, 27 Mar 2003 09:35:10 GMT
Cocoon is a framework for XML publishing. It can be used as standalone 
or as webapplication.

Forrest uses Cocoon as library. Forrest can also be used as standalone
or as webapplication.

So if you work with Forrest, you have nothing to do with Cocoon - besides
a few things (sitemap, ...).

For used as webapplication a WebContainer (Servlet/JSP) is needed: for 
example Tomcat.


Default skins are located in <forresthome>/context/skins.
Besides the common-directory, which contains share sources, each directory
contains a skin. You can create your own by copying the template directory
and modifying the sources in there.

Thats default - you can place your skin into another location. But then you
have to set the property project.skins-dir in the (and
all other properties it depends on: project.content-dir.

Which skin should be used is stored in the property

Jan Matèrne

> -----Ursprüngliche Nachricht-----
> Von: Ines Robbers []
> Gesendet am: Donnerstag, 27. März 2003 10:13
> An:
> Betreff: Cocoon & Skins
> Hello!
> I've downloaded Forrest and read the documentation but some things are
> still not clear to me:
> Cocoon and Tomcat are already installed on my computer and I 
> want to use
> Forrest with it.
> I "seeded" a new website which worked fine but how exactly 
> does Forrest
> work "in" or "with" Cocoon?
> I didn't start Tomcat/Cocoon and Forrest works anyway. There doesn't
> seem to be any connection between them.
> Do I have to copy Forrest-files into Cocoon maybe or do I have to seed
> my new project into the Cocoon folder?
> Another thing I don't understand is how to apply one's own skin. Where
> do I place a modified copy of the forrest-site skin?
> Somewhere in my xml-forrest folder or somewhere in the new project's
> folder - and there, do I put it into the build folder or in src?
> I'd appreciate your help very much!!
> Thanks!
> Ines 

View raw message