Recently, I did something similar and am under the impression of using this:
ending up in this (temporarily available) result:
https://dl.dropboxusercontent.com/u/8231701/cdn-digitalmedia-clients/schumacher-merz/index.html
Requires jQuery and this init (in the before end body Tag and enclosed in a script-Tag):
/***************** OnePage Nav ******************/
var top_offset = $('#section-desktopNav').height() - 70;
$('#fwNav1').onePageNav({
currentClass: 'fwCurrent',
changeHash: false,
scrollOffset: top_offset,
scrollSpeed: 1250,
scrollThreshold: 0.5
});
The offset is for the fixed nav-item’s height (70px in this example). The name of the css-menu might be different as well (but should match as long it is the first implemented one).
To indicate the bg color of the current link, I created the following Tag-style in the styles-palette:
#fwNav1 .fwCurrent {
background: #E20019;
}
As ever the simple word of warning (disclaimer):
Dealing with external library (jQuery) may cause, that you have to drop other actions such as Scripty or FX (Scriptaculous/Prototype) to avoid any clash of the titans.
Furthermore I expect people knowing what they do. A “missing” feature or action is neither an excuse nor a constraint.
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at: