Here's what I need: a step by step, simple walk-through that will allow me to
create a shared (library) navigation bar with rollovers, hyperlinks, and drop
box subnavigation.

It's GOT to be possible, but I'll be damned if I can figure it out. I've spent
at least 20 hous on my own trying to do what should be one very straightforward
act. I've tried to:

[bullet][/bullet]create the whole thing in Fireworks 8 (I don't have CS3),
export it as HTML, and then convert it in Dreamweavr to an .lbi file. I lose
all the rollovers and drop boxes.

[bullet][/bullet]create the whole thing in Dreamweaver, as an .lbi file. I can
get the rollovers and hyperlinks, but not the drop boxes (subnavigation), which
I assume should be introduced as sprys, only that menu is disabled.

Either way, I end up trying to stitch together the code to make the thing work
in the library, and I'm failing dismally. THANK YOU FOR ANY HELP YOU CAN GIVE
ME.

Your approach is wrong from the beginning.

But first, tell me what you mean by "shared (library) navigation bar)",
please.

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================


"DianeHammond" <webforumsuser@macromedia.com> wrote in message
news:frs24p$fok$1@forums.macromedia.com...
> Here's what I need: a step by step, simple walk-through that will allow me
> to
> create a shared (library) navigation bar with rollovers, hyperlinks, and
> drop
> box subnavigation.
>

Here's the long view: I want to create a set of navigation links using
images/rollovers; hyperlinks; and secondary, drop-down menus.

I want to create this navigation bar so that it can be applied to all pages of
my website, but if/when things change, I only have to change them in one place.

I thought Dreamweaver stores such items in its library, and they're inserted
on each affected page.

Hopefully that clarifies things. I'm sure I'm a moron for not figuring this
out on my own, but I'm more than ready to say Uncle!

A problem is that image rollovers and dropdown menus have javascript
functions that need to go into the head section. A dw library item won't
properly put the script functions where they need to go in current versions.

You could use a dw template for this- just don't put any other files except
the .dwt file in the Template folder.

And if you are thinking of using the dw pop out menu behavior or some other
third party javascript menu, make the menu in the template using site root
relative or absolute full http paths.

--
Alan
Adobe Community Expert, dreamweaver

http://www.adobe.com/communities/experts/

Thank you--that makes sense.

> A dw library item won't
> properly put the script functions where they need to go in current
> versions.

Sure will....

> And if you are thinking of using the dw pop out menu behavior or some
> other
> third party javascript menu, make the menu in the template using site root
> relative or absolute full http paths.

I would caution against either of these approaches (the DW menus, or 3rd
party javascript menus).

I would use templates definitely. I would build the navigation element into
a server-side include. And that'll do the trick. To make the menu, I would
use one of the PVII menu extensions, or build it myself (it's not so hard,
if you follow the tutorials at the PVII site) -

http://www.projectseven.com/

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================


"Alan" <please_dont_mail_me@example.com> wrote in message
news:C4070887.2F2E60%please_dont_mail_me@example.c om...
>A problem is that image rollovers and dropdown menus have javascript
> functions that need to go into the head section. A dw library item won't
> properly put the script functions where they need to go in current
> versions.
>
> You could use a dw template for this- just don't put any other files
> except
> the .dwt file in the Template folder.
>
> And if you are thinking of using the dw pop out menu behavior or some
> other
> third party javascript menu, make the menu in the template using site root
> relative or absolute full http paths.
>
> --
> Alan
> Adobe Community Expert, dreamweaver
>
> http://www.adobe.com/communities/experts/
>
>
>

>> A dw library item won't
>> properly put the script functions where they need to go in current
>> versions.
>
> Sure will....

You can add a behavior in an .lbi file, and the function will be put in the
head of the file the library item is used in?

--
Alan
Adobe Community Expert, dreamweaver

http://www.adobe.com/communities/experts/

Thank you, too, Murray. I'm off to try the tutorial.

> You can add a behavior in an .lbi file, and the function will be put in
> the
> head of the file the library item is used in?

No. But if the Library item has a call to a behavior, DW will make sure
that the required js is located in the head of the parent document. You
must never *apply* a behavior to an existing Library item - the behavior
must have already been applied before the Library item is created. This
gets a bit dicey if you create the Library item, and then later decide you
need to have a behavior in it....

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================


"Alan" <please_dont_mail_me@example.com> wrote in message
news:C4072BB7.2F2E91%please_dont_mail_me@example.c om...
>
>
>>> A dw library item won't
>>> properly put the script functions where they need to go in current
>>> versions.
>>
>> Sure will....
>
> You can add a behavior in an .lbi file, and the function will be put in
> the
> head of the file the library item is used in?
>
> --
> Alan
> Adobe Community Expert, dreamweaver
>
> http://www.adobe.com/communities/experts/
>
>
>

> You
> must never *apply* a behavior to an existing Library item - the behavior
> must have already been applied before the Library item is created.

okay- that's what i was getting at. It worked in dwmx 6.0, then broke in the
MX 6.1 updater. Don't know if it's worth being worked on for the next
version.

If this site would smallish I'd use a dw template. If it would be larger or
possibly have frequent changes to this menu, i'd use SSI, one in the head
for the functions and one in the body for the nav menu.

--
Alan
Adobe Community Expert, dreamweaver

http://www.adobe.com/communities/experts/