On Mar 1, 2008, at 09:01, The Web Maestro wrote:
Hi
Just noticed this:
On Fri, Feb 29, 2008 at 2:18 AM, Vincent Hennebert
Also, have you looked at disabling the menu auto-rolling feature? If
not, I will ;-)
Fixing that should be as easy as adding this to the bottom of the
<extra-css> block in src/documentation/skinconf.xml:
<extra-css>
.menuitemgroup{ display: block;}
</extra-css>
I just added a change to skinconf.xml in svn. Unfortunately, the
change did not show in my local build. Nevertheless that's how Forrest
works.
That would make all the nodes expanded by default, but if I interpret
Vincent correctly, it's not /that/ simple...? :/
Just checked a few other projects' sites and the 'annoying' behavior
mentioned earlier is also present there, most notably also Forrest's
own homepage.
BTW: Checking the HTML and JavaScript source, I don't see any sign of
something session-persistent. The structure is relatively simple: if
you switch to tab B, then the browser will be redirected to a new
page, forgetting what the state of the menu on tab A was. Switching
back to A means reloading the page corresponding to the first tab
from scratch.
It could turn out to be not too much effort to add, I guess.
Unfortunately, I'm not fluent in Forrest, so I have no idea how far a
user can go in terms of embedding custom scripts. If they do not
already have something for this, I may just know enough HTML/
JavaScript to hack this together, and if it works well on our end,
donate it back to Forrest one day. Right now, I know little more than
how to generate the site. I know roughly what the resulting pieces of
script should look like, and how the generated HTML should be
modified, but not enough Forrest-related configuration details to
know /where/ to make those changes...
Cheers
Andreas
