On Wed, 2005-05-18 at 00:39 -0400, Gregor J. Rothfuss wrote:
> Thorsten Scherler wrote:
> 
> > The main question is how can I use the forrest resource without a simple
> > copy n' paste? e.g. 
> > <map:transform
> > src="{project:skins-dir}{forrest:skin}/xslt/fo/document2fo.xsl">
> >                   <map:parameter name="imagesdir"
> > value="{project:resources.images}/"/>
> >                   <map:parameter name="xmlbasedir"
> > value="{project:content.xdocs}{1}"/>
> >                 </map:transform>
> 
> these are instances of the forrest conf input module:
> 
>      <component-instance name="defaults" 
> class="org.apache.forrest.conf.ForrestConfModule">
>        <values>
>          <skin>@project.skin@</skin>
>          <menu-scheme>@project.menu-scheme@</menu-scheme>
>          <bugtracking-url>@project.bugtracking-url@</bugtracking-url>
>          <issues-rss-url>@project.issues-rss-url@</issues-rss-url>
>          <i18n>@project.i18n@</i18n>
>          <home>@forrest.home@/</home>
>          <context>@context.home@</context>
>          <skins-dir>@context.home@/skins/</skins-dir>
>          <stylesheets>@context.home@/resources/stylesheets</stylesheets>
>        </values>
>      </component-instance>
> 
>      <component-instance name="project" 
> class="org.apache.forrest.conf.ForrestConfModule">
>        <values>
>          <skin>@project.skin@</skin>
>          <sitemap>@project.home@/@project.sitemap@</sitemap>
>          <status>@project.home@/@project.status@</status>
>          <skinconf>@project.home@/@project.skinconf@</skinconf>
>          <doc>@project.home@/@project.content-dir@/</doc>
>          <content>@project.home@/@project.raw-content-dir@/</content>
>          <content.xdocs>@project.home@/@project.xdocs-dir@/</content.xdocs>
>  
> <translations>@project.home@/@project.translations-dir@</translations>
>  
> <resources.stylesheets>@project.home@/@project.stylesheets-dir@/</resources.stylesheets>
>  
> <resources.images>@project.home@/@project.images-dir@/</resources.images>
>          <skins-dir>@project.home@/@project.skins-dir@/</skins-dir>
>          <temp-dir>@project.temp-dir@</temp-dir>
>        </values>
>      </component-instance>
> 
> you would add that input module to lenya and change the build process to 
>   replace the values between @@ at build time. look at the 
> @lenya.version@ substitution for an example

Hmm, ok but still would you suggest to copy n'paste the original
stylesheets to lenya or would we state that for this feature (...and all
upcoming features based on forrest) we have a dependency on forrest? I
would vote for *not* c n'p but using the original ones. 

That mean the user have to have as well a forrest instance installed
besides cocoon and lenya.

This way I have the change to dig in a more general way of using forrest
ressources in lenya without modifying the original resources to much.

WDYT?
-- 
thorsten

"Together we stand, divided we fall!" 
Hey you (Pink Floyd)


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to