You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "Thorsten Scherler (JIRA)" <ji...@apache.org> on 2005/12/17 19:01:36 UTC

[jira] Commented: (FOR-768) Added 'linking to external css files' section to howto-structurer-dsl.xml

    [ http://issues.apache.org/jira/browse/FOR-768?page=comments#action_12360674 ] 

Thorsten Scherler commented on FOR-768:
---------------------------------------

We dropped the <forrest:css/> element because is was to much html
specific. We decided to use a contract for the same functionality:

<forrest:contract name="branding-css-links">
 <forrest:property name="branding-css-links-input">
  <css url="common.css"/>
 </forrest:property>
</forrest:contract>

It is working like described from Cyriaque because I used the same code
on which he is basing his description. The only difference is like you
see from the sample that I had to drop the forrest: namespace. 

So I reckon you can go into any detail. I will add this documentation as well to the contract. One reason why we are using contracts  is that you can have the documentation about the contract within the contract. ;-)

BTW can it be that you forgot to attach the patch, or did I missunderstood you.

> Added 'linking to external css files' section to howto-structurer-dsl.xml
> -------------------------------------------------------------------------
>
>          Key: FOR-768
>          URL: http://issues.apache.org/jira/browse/FOR-768
>      Project: Forrest
>         Type: Improvement
>   Components: Dispatcher (aka views), Documentation and website
>     Versions: 0.8-dev
>     Reporter: paul bolger
>     Priority: Minor

>
> I've added a section on simple linking to external css files to this How-To. At present I'm not sure it's worth getting into too much detail as views are changing very rapidly.
> This is the first time I've used SVN patching so I'm not sure if it has worked on not. Let me know if it hasn't and I'll try again.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira