> That's site.xml So can I create a template site.xml, or do I need something dynamic? Sorry, looking for a big assist. :-)
> > Is there a nicer way? > > In which sense 'nicer'? I guess, more "traditional gump-like". Ought site be the log directory, ought I create content/xdocs in some other place. I guess trying to be more like traditional gump. > 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. I was thinking that we'd ship a Jakarta-Gump skin & resources, like the one the Jakarta-Gump site uses, but then a site might wish to override it's logo, it's skin, etc. I am setting up Gumps internally @ work, and much as I give Jakarta Gump credit I'd like to brand our results as Sybase (to make my target audience more accepting). > 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 I have *no clue* on forrest internals, so I am in no real position to judge if this is good/bad or ugly. That said, if I could easily add 'class=ERROR' or something to a <TR or <TD or whatever, wouldn't existing skins/stylesheets just ignore it? Could I not somehow cascade a small stylesheet for this feature on top of existing ones? [Forgive me if I am confusing old CSS stuff w/ forrest stuff & talking junk... :-)] regards, Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
