Gav.... wrote:
----- Original Message -----
From: "Ross Gardler" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, January 20, 2006 7:51 AM
Subject: Re: Example use case.
| Gav.... wrote:
|
| This is whole thing getting confusing. It feels like you are trying to
| solve all problems at once, and as a result are being recommended to
| approach it with a whole raft of technologies.
Ok, I agree, but all the answers have helped.
| Lets take it one step at a time. Here are the major tasks:
|
| 1) get a theme that you like
Back to using v2, this is the stage where I am at.
I have followed the Dispatcher Quickstart guide to the letter
and it works perfectly (forgets to mention to add
project.theme-extension=.fv
to forrest.properties) . So this I have completed no problem.
Patches to the doc are welcome, especially if you are able to highlight
some of the forthcoming changes in v3.
Now, instead of altering pelt.fv I thought I would instead copy it
and call it pili.fv, saving in the same folder as pelt.fv.
I then rename project.theme=pili in project.properties.
re-run forrest run and I get Internal Server Error with :-
"ElemTemplateElement error: Found more than one template named: noFt-body"
So I guess I cant create my own named theme just yet, or I missed something
not documented maybe. I will alter pelt.fv in the meantime.
For an example of creating your own theme see the o.a.f.themer.Coat
plugin in whiteboard. Don't be fooled by the fact that this looks like a
plugin, at present it is nothing more than a site that uses a new theme.
I still have to do a little work to make it an installable theme - I'm
waiting to see the necessary changes for v3.
Ross
