forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thorsten Scherler (JIRA)" <>
Subject [jira] Commented: (FOR-521) static HTML in views
Date Mon, 06 Jun 2005 22:50:43 GMT
    [ ] 

Thorsten Scherler commented on FOR-521:

Actually pure html should be in a contract IMO. 

I thought about allowing <forrest:hook>text</forrest:hook> but that does not feels
right in the view. 

I think something like:
<forrest:contract name="site-branding">
  <forrest:properties contract="site-branding">
     <forrest:property name="site-name">new seed</forrest:property>
     <forrest:property name="site-tagline">powered by forrest:views</forrest:property>

Is handy for the reuse of contracts in different views with different properties. The template
would look like:
<xsl:template name="site-branding-body">
  <xsl:param name="site-name"/>
  <xsl:param name="site-tagline"/>
  <div id="site-name"><xsl:value-of select="$site-name"/> </div>
  <div id="site-tagline"><xsl:value-of select="$site-tagline"/></div>

Where this <forrest:properties contract="site-branding"> will be properly in the long
run not part of the views.fv but another config file (maybe generated out of somekind of metadata)


*Rember discussions on dev list*

> static HTML in views
> --------------------
>          Key: FOR-521
>          URL:
>      Project: Forrest
>         Type: Wish
>   Components: Skins (general issues)
>     Versions: 0.8
>     Reporter: Diwaker Gupta
>     Assignee: Thorsten Scherler
>     Priority: Minor

> A final touch for views would be the ability to add arbitrary static HTML to skins. For
instance, I want to put a header in all my pages (not a project logo, just some text like
"My Home Page" or something on top) Currently there is no easy way to do it, except of course
to write a contract for the header and then include that. Maybe there is some simpler mechanism
and I just don't know about it?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message