|
|
|
Navbar Down Buttons w Template |
|---|
| message from marywithani on 22 Jul 2004 |
OK - I'm really trying... I've got my navbar in my template, and all my pages
are working well. However, I really want the "down state" button to indicate
what page you're looking at. If, in my template, I go to the navbar setup and
check "show down initially", for each button, the down state for all of them
will show, won't it (it's late and I could try it from home using the VPN, but
my home monitor is little and it's too frustrating trying to maneuver graphical
things so I need to wait til tomorrow but....).
Can I have one template with my navbar built into it and still somehow have
each individual page load with the appropriate "down" button? I brought this
up before and something about a background image and CSS was mentioned... right
now the only thing I'm really using my external CSS for are basic text, links,
etc.
Help?!
|
| Murray *TMM* replied to marywithani on 22 Jul 2004 |
It sounds to me like you are using the DW NavBar function. If that's the
case, be aware that the down state thing will only work properly if you are
using it in a framed site. You aren't using frames, are you?
If you are not using frames, you should remove that navbar from your page
since it's too much overhead for the simple image swaps that it's doing.
Replace the navbar with ordinary rollover images and you will be on your way
to bliss.
Now - tell me - how good are you with CSS?
|
| marywithani replied to Murray *TMM* on 22 Jul 2004 |
Thank you THANK YOU! I will forget the DW navbar and make my own - no, I'm not
using frames.
Not so hot with CSS... Here's my situation... I work for a nonprofit of almost
300 people at 10 locations, in an MIS dept of 3 that's down to 2 with one new
mom out until who knows when. Like many in this field, I wear a LOT of hats.
I was asked a couple months ago if I would like to totally redo our website,
which had been done a few years ago by our host. Decided this would be an
awesome thing to learn (we had toyed with the idea of hosting it ourselves, but
will keep it outside and also now have the flexibility to make our own
modifications). Anyway, I thought this would be an awesome thing to learn.
However, I am totally on my own. I bought Dreamweaver, Freehand, the
Dreamweaver Bible and have been doing research online. I would love to even
just take a couple day workshop, or just sit down with someone who knows what's
going on, but all I get is, "I'm sure you're doing just fine...".
So, I managed to put together an external CSS file and applied that to my
template. It basically tells my template what color, font, and size to make
body, list, table, and link text. I think that's about it. I usually figure
out a way to make things work okay, but I often feel like there is probably a
better way.
Sorry for the babble - thanks for your help! I'm sure I'll be back...
|
| Murray *TMM* replied to marywithani on 22 Jul 2004 |
Once you have your navigation in simple rollovers, then what you need to do
is to create a way for each page to force its corresponding button to the
down state. This is quite a simple thing to do if you are using CSS
rollovers (i.e., where the a:link and the a:hover pseudo-classes have
different background images and it's the background image that is the button
image - you can see an example of this on my sites at
http://www.midwestespresso.com or at http://www.therobertshouse.com , but
it's a bit more of a challenge with image swaps as you are using. I'll see
if I can dig up an old post that describes how to do that....
|
| Murray *TMM* replied to Murray *TMM* on 22 Jul 2004 |
Here's one from last March -
If you are going to use the Template approach, then use Template Optional
regions for your menu buttons.
Each button would be placed on the Template page in *both* up and down
states, giving this arrangement -
button1up button1down button2up button2down....
Select button1down, and apply a Template Optional region named button1down
that is NOT shown by default. Select button1up and apply a Template
Optional region that is using an expression (the advanced tab) of
!button1down. Repeat this process for each pair of buttons. The end result
will be a template page that shows both button states for all buttons. In
other words, a scary mess.
However, the magic happens when you spawn a child page. Note that only one
of each button is shown on this page, and that you can change which button
is in the down state by using MODIFY | Template Properties.... and selecting
a button#down to be shown.
Interested?
|
|
