opinion on something

Unfortunately the client is the boss after all. So pretty much all you can do is 'try' to pursuade them that your proposed course of action is the better way to go....

Your text link menu is an interim solution but I would think there are some Opera compatible menus around. You are using a script from dynamicdrive, I would suggest the Bratta version or even the heirmenus version from webreference.com. Good luck anyway

Checked it in NN4.7 and 6 no problems I can see. Someone else have Opera Loaded? coz I dont!

ACK...i see now in Opera, some of the text links disappear. I suppose this is due to the menu using layers...not sure.

I was waiting on Bratta to come out with his new Lite version. Haven't checked lately to see if he was finished with it or not. I have also looked at the one from webreference and it is sweet but very confusing when i looked at the installation directions.

I guess I will have to leave as is (without the text links) until I can figure out one of the other ones.

I have removed the text links from the site mentioned above so nevermind on this one for now.

thanks detox for your input:)

no charge!

Disaster-Master,

What I would most recommend, since you can't get your clients to understand the draw back, is to use browser detection to achieve your goals -- basically augment the menu.

What you can do is test for the browser -- if Netscape 4.x or Opera anything, display this wee file (a .js file with HTML in it for the text links), otherwise, go ahead with the dhtml menu.

Suzanne

Hi Suzanne,

You always seem to come through for me. That is what i was originally wanting to do several months ago but i couldn't figure out how to do that. Someone offered to help but never followed through. Can't say i blame them.

If you could recommend a link or site that will instruct me on how to do this that would help a bunch because I don't even know where to begin. Maybe like "Browser Detect How-To for Complete Idiots.":D

ha ha ha .... I don't know of one for complete idiots, sorry!

It wouldn't be for you, anyway.

Script 2.9 at javascriptworld.com (good book, I recommend it) will serve your needs for basic understanding but you will probably run into some glitches for Opera. If people using Opera choose to look like they are using something else, then they takes their chances.

You'll want more than just the browser name, though. You'll also need a version. (navigator.appName, navigation.version).

For the Mother of All Browser Sniffing...

http://www.mozilla.org/docs/web-developer/sniffer/browser_type.html

Do you need help with the rest of it?

Suzanne.

Here you go. There are hundreds of browser checks out there. Sorry disaster-master, I assumed you already had a browser check as a part of the menu. Should have looked harder!

here is a link to the mother of all browser sniffers. It looks up AOL Opera IE NN hot Java web TV pretty much anything.....

http://www.mozilla.org/docs/web-developer/sniffer/browser_type.html

Damn Suzanne, you beat me to it!!!!

i believe there is a browser detect in the script for the menu because this noscript thing is there. It is place just below the body tag in my code along with the file paths for the menu.
Your browser is not JavaScript-enabled.
Am I correct on this?

If that is a browser detect above, should I use another browser detect as well as the one that is already with the menu or do I try and tweak the one that I already have to make it show the text links for browsers that do not display the menu?

Thanks for the link....headed that way now.

There is probably a browser detect script as part of the DHTML menu. However, you want to do different things, so if it detects for Opera and N4.x, you can use the same variables to set up things, yes.

If it doesn't, then you'll have to use something else (the link Detox gave you above).

The tag is not browser detect, that's just in case someone has JavaScript disabled.

Suzanne

P.S. Ha ha, Detox. It's not on purpose, you know! I'm amused we used the same title for it (mother of all...) ha ha.

Just stole a quick look at your js files for the detect script (all menus like this have it) and yes you do have it. It is checking for Opera 5, not 6. This seems to be a fairly old style of menu; it is not looking for version 6 of any browser.
Will have a closer look at the script but I would suggest a better menu system. If the onbly problem with changing is to do with organising it. Simply post back and we can all help. I have set up (in fact most of us probably) these styles of menu's quite often.
Get back to us here and let us know what you want to do.

Detox,

I just took a shot at something....don't really know what I am doing here. anyway, I copied the code off of that site that you gave me and made a file called "detect.js". I put it just below the menu scripts exmplmenu_var.js and menu_com.js. I know that there is something else that needs to be done but I am lost here. Am I even on the right track by doing what I just did with the detect.js that I created?

What next?

Oh, I looked at brattas stuff in Opera....NOT. And the heirarch menu at webreference doesn't show up in Opera either. I am thinking that the menu i have is fine as long as i can do something to make just plain text links show up in browsers that do not show the menu. Do you agree with me?

disaster-master,
what the browser detect does is taylor specific functions of the menu to different browsers, NN and IE interpret and execute layers etc in different ways. If you want the menu to work on Opera you will have to do more, but if you want to simply redirect to a text menu for opera then you can use the browser detect in the current menu system and simply add opera 6 to the detections. Once the menu sniffs out Opera 6 you can trigger the displaying of the text menu.

which one do you want?

i want to redirect to a text menu.

do i add the following to the detect.js file?

var is_opera5 = (agt.indexOf("opera 6") != -1 || agt.indexOf("opera/6") != -1);