All,
Can I impose upon you for some help with forrest?
Let's see if I can help a bit.
I'd appreciate some help/feedback designing the approach I take for the main aspects:
1) sitemap.xml or book.xml or both. 2) Directory structure 3) Templating/Site Customisation 4) Nice features (e.g. red/yellow/white)
1) I'm sorry but I never understood how forrest finds xdocs. My local
version seems to find all, yet Nick's doesn't. I know I should create a
book.xml per directory, and perhaps even/also a sitemap.xml,
That's site.xml
but I am looking for the easiest solution, since I have to code the creation of these. Can somebody suggest a strategy,.e.g. dynamically create book.xml per directory, and I'll code it.
I think that for generated pages the best bet it using site.xml as a default menu for the summaries and book.xml for each section.
2) I think I ought put things:
$LOG = Gump Workspace 'Log' directory = $GUMP_WORK/log (say)
$LOG/content $LOG/content/xdocs = the generated pages
$LOG/site = the output.
Is there a nicer way?
In which sense 'nicer'?
Ought I put xdocs into $GUMP_WORK/content/xdocs (not into log) and put site as $LOG?
Forrest builds from a content dir, that can contain not only xdocs but also resources or raw files (the default raw file location will change in the 0.6 release).
So I'd say that your suggested layout seems OK.
3) I need to allow templating (1) of default skin/images/etc. (2) use/site
overrides.
Can you please explain better the usecase? I reckon that a single Gump run will have a single skin to be used in the site generation.
As such I need to copy certain things into $LOG/content above from somewhere, two places (I think). What is the best place to store the defaults and allow the site to customise? Ought we start a jakarta-gump/templates/documentation/ tree that folks can add to, that gets copied to $LOG/content? Is there any way we can leverage the site/xdocs contents somehow?
4) I guess I need to dig into the documentation (I find it hard to grok) and/or ask the forrest mailing list on this one. I'll try to find time to do this.
Well, ATM to change coloring you can: 1 - output the pages as ehtml, that is plain html that gets just decorated with the top and left bars - drawbacks: only html output 2 - change the xdocs format and stylesheets - drawbacks: non standard xdocs and skins, cannot use readymade ones 3 - wait till we enable the "class" attribute in all elements and make a special Gump skin that enhances that Forrest one - drawbacks: non standard skins, cannot use readymade ones 4 - wait till I do a change in Forrest that will allow you to output also embedded xhtml in the xdocs - drawbacks: waiting for me ;-P (maybe it already works, haven't tried it) -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) ---------------------------------------------------------------------
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
