forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thorsten Scherler <>
Subject RE: Re: voice stylesheet and views
Date Fri, 23 Sep 2005 21:27:42 GMT
El vie, 23-09-2005 a las 17:23 +0200, HANAX escribió:
> > El vie, 23-09-2005 a las 11:26 +0100, Ross Gardler escribió:
> > > HANAX wrote:
> > > > As I understood, contracts are points where to place xsl templates.
> > > 
> > > Yes, templates, but not complete stylesheets...
> >  
> > Hmm yes and no. You need to rip of the templates of the stylesheet. Have
> > a look at
> >
> >  
> Thanx, good inspiration :)


> > > > I noticed some some structure naming convention but I can't find where
it's explained. 
> > > 
> > > Because they are not, at least not in an easily accessible way. There 
> > > will be discussion in the mail archives, but they are not documented 
> > > anywhere. I'm afraid I can't tell you what they are.
> >  
> > First thread about naming convention:
> >
> >  
> > Another recent thread:
> >
> >  
> I've read it but I thought that ti will have something to do with fact that I need tu
suffix my template -head when it should be in head part.. correct?
> If I don't that I get error...

Actually you should not get any error. ;-) The most important thing is
that you define which part of the template you want to trigger. 
  format="xhtml" name="nav-section" inputFormat="xsl" body="true" head="false"/>

The important thing is that you define head or/and body. 
The reason is historical because views have been developed first for xhtml.
A xhtml document has the following basic form:

You can either put something in the head or/and in the body. Now what
Ross is trying to tell you is that the voice markup belongs to either
head or body of a html document. I did not had the chance to have a
closer look into the voice plugin because of time constraints. I can not
say whether that is right or not but I imagine that it is right because
you would need normally a visualization besides the voice part. That is
why he recommends to use views. You can add any contract to your plugin
that may not be used for the principle purpose of the plugin but will
enhance it for people that "just" want to *see* the page and not hear
> > > Small because they are not doing major transformations, they are simply 
> > > working with specific parts of the source document. However, yours will 
> > > be much larger since you are processing the whole document into a new 
> > > format.
> >  
> > They will do what you made them to do.
> Of course :)



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

View raw message