Author: thorsten
Date: Sat Dec 17 18:00:00 2005
New Revision: 357414
URL: http://svn.apache.org/viewcvs?rev=357414&view=rev
Log:
Patch for FOR-768. Documentation enhancement from paul bolger. thx paul
Modified:
forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-dsl.xml
Modified:
forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-dsl.xml
URL:
http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-dsl.xml?rev=357414&r1=357413&r2=357414&view=diff
==============================================================================
---
forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-dsl.xml
(original)
+++
forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-dsl.xml
Sat Dec 17 18:00:00 2005
@@ -404,9 +404,50 @@
</source>
<p> We are now able to place contracts into the layout container and add
custom css to the structurer. </p>
- <fixme author="thorsten"> Add more information of recent threads around
css in the structurer
+ </section>
+ <section>
+ <title>Linking to an external css file</title>
+ <note>This will change for the next version of views (v3) where we use a
+ generic contract instead of the standalone element (forrest:css).
</note>
+ <p>Make sure your project has the following directory structure. If it
+ doesn't you'll have to create it. "common" is the fallback for all
+ themes, if you want to override the css for a specific theme replace
+ "common" with "themeName". This is where Forrest will look for
external
+ css stylesheets. </p>
+ <source>
+ $projectHome\src\documentation\resources\themes\common\css</source>
+ <p>Where $projectHome is the directory where your project exists.</p>
+ <p>Put your css stylesheets in this directory. For arguement's sake
let's say
+ it's called mystyles.css</p>
+ <p>Edit your common.fv structurer (or whatever structurer (theme) you
are using). This
+ will probably be some where in: </p>
+ <source>$projectHome\src\documentation\content\xdocs</source>
+ <p>or if you want to override it for the whole project in:</p>
+ <source>$projectHome\src\documentation\resources\themes\</source>
+ <p>Add the following element to the *.fv file:</p>
+ <source><![CDATA[<forrest:css url="styles.css" media="screen"
theme="pelt"/>]]>
+ </source>
+ <p><strong>Important!</strong> This must appear straight after the "view
+ type" element (as first child): </p>
+ <source><![CDATA[<forrest:view type="html">]]></source>
+ <source><![CDATA[<forrest:css url="mystyles.css" media="screen"
theme="pelt"/>]]>
+ </source>
+ <p>The attributes are: </p>
+ <ol>
+ <li>the url where the css exist (NOTE: it will be rewritten to
"../themes/mystyles.css").</li>
+ <li>the media type, you can set different styles for screen and print.
+ This is really useful if you want to hide elements such as
navigation
+ in the print output (#nav-section{display:none} for example).</li>
+ <li>the theme, "pelt" is the default theme (another is the "common"
theme). Change this if you
+ are using your own theme.</li>
+ </ol>
+ <p>You can have as many css links as you like, and they'll appear in the
+ head of your document in same order as they are in the .fv file.</p>
+ <fixme author="thorsten"> Add more information of recent threads around
+ css in the structurer and information how you add an @import? Use e.g.
+ <a
+
href="http://marc.theaimsgroup.com/?t=113471292700001&r=1&w=2";>http://marc.theaimsgroup.com/?t=113471292700001&r=1&w=2</a>
</fixme>
- <!--<fixme author="thorsten">This section is next to be
writen/finished</fixme>-->
</section>
</steps>
<extension title="Further Reading">
