I'm working on a large site (over 3,000 pages) and would like to have my navigation handled through dropdown menus. I've used several java script solutions that are nice, but don't meet all of my requirements.
So far I've found one JS solution that works this way, but only has one level of submenus, but I need two. All of the solutions that I've found with 2 levels require that the js file be in the directory with the HTML.
Am I missing something basic, any suggestions?
Geez, how did I miss this thread?! :eek:
Peter, which dropdown menu system are you using? It really sounds like to me that there is something simple missing, due to the fact that the vast majority of the time the code behind the DHTML dropdown menus are encapsulated in one file only.
*another thought* : can you show the full SSI command you're using? That may also be a cause.
Are there any advantages with using SSI instead tho'?
Well, gosh, I dunno. I've done it both ways but have never tested it. Anyone know what is the best method, for reasons of efficiency or other? School me...
I use a program called dHTML Menu Builder. (http://software.xfx.net/utilities/dmbuilder/index.html)
It only costs about $30 and it can handle multiple sub-levels. It works in Netscape and IE and it is RAD!
It makes it so easy to build great cross-platform menus that you could pound it out in an hour or two. Plus you can specify whereever you want to JS file to go.
Check it out. They have a demo you can preview. I do recommend that you get the BETA version of 3 though. Even though it is BETA, it works perferctly. I think it is within weeks of becoming a full release.
SSI is good in the event that a browser doesn't support scripting. But in your case (use of DHMTL), that seems to be beside the point.
You could use both, acutally, with the SSI containing a <noscript>blah, blah.</noscript>
I just reworked the whole site to use the src attribute of <script> instead of including the JS with SSI. I don't really know whether it's made the pages load faster or anything. However, one cool thing is that on CGI and other template pages, I can now include the JS rather than having to cut and paste it over! So that's a really good thing.
Yeah using both SSI and the src attribute together is proper wicked.
:) I started this thread with a simple question, and have really appreciated and learned from all of the posts. Turns out that my initial question, concerning using SSI to include a client side java script, was answered early on. As a result I've successfully used SSI to include both the .js file and the script for our pages. Haven't rolled it out yet, still in development, but I have been able to modify many pages at once by simply modifying the include file. Way Cool!
Currently I'm working on using another menuing system that requires an image map that I have also been able to include with SSI.
So, how about including an entire page? Any suggestions? On our intranet portal I'd like to embed an external page in a picture-in-picture style so that our users can get their fill of headlines, sports scores or whatever. I'm trying to avoid using frames for this.
Keep those cards and letters coming...