forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r887433 - in /forrest/trunk/site-author: content/xdocs/docs_0_90/your-project.xml status.xml
Date Fri, 04 Dec 2009 23:05:40 GMT
Author: bdube
Date: Fri Dec  4 23:05:40 2009
New Revision: 887433

Issue FOR-1000
Update custom skin documentation to show use of locationmap


Modified: forrest/trunk/site-author/content/xdocs/docs_0_90/your-project.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_90/your-project.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_90/your-project.xml Fri Dec  4 23:05:40
@@ -1126,30 +1126,41 @@
 <xsl:stylesheet version="1.0" xmlns:xsl="">
-  <xsl:import href="../../../common/xslt/html/document-to-html.xsl"/>
+  <xsl:import href="lm://"/>
   ]]><strong>... overrides of default templates ...</strong>
-          In order to use this feature in your custom skins you must copy the
-          common skin from the forrest distribution into your custom skins
-          directory (from <code>main/webapp/skins/common</code>). This will
-          protect your skin from changes in the Forrest common skin, but you
-          must remember to update this skin in order to take advantage of new
-          features added over time by the Forrest team.
+          Notice the use of the <em>lm</em> protocol in the import statement.
+          The <em>lm</em> protocol directs Forrest to use the
+          <a href="site:v0.90//locationmap">locationmap</a> to resolve the
+          location of the indicated stylesheet. If you trace this
+          call through the sitemap, you will find the following section of
+          <code>main/webapp/locationmap-transforms.xml</code>:
-        <note>
-          The above paragraph means that if you do copy an existing skin as this
-          section recomends you will also need to copy the common skin since all
-          existing skins import the common skin.
-        </note>
+        <source>
+    <match pattern="*.*.*">
+      <select>
+        <location src="{properties:skins-dir}/{1}/xslt/{2}/{3}.xsl"/>
+        <location src="{forrest:forrest.context}/skins/{1}/xslt/{2}/{3}.xsl"/>
+      </select>
+    </match>
+        </source>
-          This is particularly relevant for menu rendering (book-to-menu.xsl),
-          where the common stylesheet does the 'logic' of which item is
-          selected, and over-riding stylesheets define the presentation.
+          This means that the locationmap first checks your project space
+          (according to the <code>${project.skins-dir}</code> property of
+          your <code></code> file) and, if the file is
+          not found there, it then checks in your installation of Forrest.
+        <note>
+          It has been necessary in the past to copy the common skin to
+          your project when creating a custom skin. This is no longer the
+          case.
+        </note>
     <section id="webapp">

Modified: forrest/trunk/site-author/status.xml
--- forrest/trunk/site-author/status.xml (original)
+++ forrest/trunk/site-author/status.xml Fri Dec  4 23:05:40 2009
@@ -153,6 +153,10 @@
         Added document to facilitate
         <link href="site:upgrading_09">upgrading to v0.9</link>
+<!-- 2009-12 -->
+      <action context="code" type="update" dev="BMD" fixes-bug="FOR-1000">
+        Changed XSLT import statements in skins to use the LocationMap.
+      </action>
 <!-- 2009-11 -->
       <action context="code" type="update" dev="TWW">
         Replaced the custom caching implementation with EHCache in the

View raw message