I don't mind having a go, but I'm not sure where that doc is. I gave it a try and yes, common.fv seems to work. I haven't checked the others yet, and won't write it up until I've tested it. Re. the SVN: I have it installed and it seems to work (I'm using the tortoise extensions). I'm more unclear about protocols, if I edit one of the Howtos how do I submit it? If I'm unsure about whether something is correct how do I pass it on for a second opinion?
On 12/6/05, Ross Gardler <[EMAIL PROTECTED]> wrote: > David Crossley wrote: > > Ross Gardler wrote: > > > >>Diwaker Gupta wrote: > >> > >>>Paul Bolger wrote: > >>> > >>> > >>>>[views: .fv files] Is there a way to specify one .fv file for multiple > >>>>input files, or does every page need an individual file? > >>> > >>>Yes. If you search through the archives, you'll find several emails from > >>>Thorsten covering the resolving mechanism. I believe its something like > >>>this (this is not authoritative, but indicative): > >>> > >>>o for pagename.html, first check if pagename.fv exists > >> > >>if not, look for one in the directory of the source file with the same > >>name as the default *.fv (as defined in forrest.properties) > >> > >>if not, look for themename.fv in the PROJECT_HOME/resources/themes directory > >> > >> > >>>o if not, look for themename.fv in the resources/themes directory > >> > >>(in the themer plugin) > >> > >> > >>>o if not, use default.fv that ships with Forrest. > > > > > > Someone should document that. > > It's documented in the structurer locationmap ;-) > > (just a hint for anyone who may have the time to work on such documentation) > > Ross > -- Paul Bolger 19 Raggatt St Alice Springs NT 0870 08 8953 6780
