i wanna make a web-based menu-navigation out of documents in a view.
the navigation structure looks like this and has also a view with documents that corresponds to it:
startpage
about us\history
about us\investor relations
products
solutions
contact us
The menu-nav on the “startpage” should be:
startpage
about us
products
solutions
contact us
The menu-nav on the “about us/history” should be:
startpage
about us
__history
__investor relations
products
solutions
contact us
Is it possible to write lotusscript that walks the view and puts the appropiate code to each document so it looks like this.
Of course should it be flexible if “other” topics are inserted in the navigation
please!
/l
Subject: Plz, any lotusscript-experts out there, Menu-navigation expertise needed.
http://www.lotusgeek.com/SapphireOak/LotusGeekBlog.nsf/d6plinks/ROLR-63V6J5
Subject: Plz, any lotusscript-experts out there - Sorry no JavaScript
Thanks for the post, but no javascript is allowed!
I want a menu with breadcumbs. HTML with some CSS in order to make the hilite to work is OK.
I think of an LS-agent that build menu-navigations on these documents on scheduled basis.
It should act on each of the documents and put the navigation as mentioned earlier.
It should allow deeper levels than two
/l
Subject: RE: Plz, any lotusscript-experts out there - Sorry no JavaScript
Why not just use an embedded view, then, and use CSS to deal with the clicked link?
Subject: Good idea, but…
I dont want to do the menu on the fly, since i’ve got other stuff to compute when it comes to render.
I’m actually thinking of making the menu whenever it comes new menu-documents.
Maybe the embedded view can be of use in my agent in conjunction with computewithform, i’ll have a look on that.
Thanks!
/l
Subject: RE: Good idea, but…
An example agent that writes html to the browser on the fly. Taken from sametime…I have played around with it and you can really make it jump through hoops. For example, you can write code to call various agents based upon conditions…according to the results of those conditions, you can write appropriate pages via the agents. Naturally, the agents can access values in your existing documents, and write those values to the browser as you would write string variables to a document. HTH.
Print||
Print|<HEAD>|
Print|<STYLE TYPE="text/css">|
Print|<!--|
Print|BODY { font-family: Arial, Helvetica, sans-serif;|
Print|background-color: #FFCC00;|
Print|background-image: URL(| + pathrelroot + |sametime/images/stbackground.gif); |
Print|background-repeat: repeat;|
Print|}|
Print|TR, TD, TH { font-family: Arial, Helvetica, sans-serif; }|
Print|-->|
Print|</STYLE>|
Print|</HEAD>|
Print|<BODY text="#000000" link="#990000" vlink="#990000" alink=\"#333333">|
Print |<table width=625 valign=top border=0>|
Print|<tr>|
Print|<td valign="top">|
Print|<a href="| + pathrelroot + |stcenter.nsf"><img src="| + pathrelroot + |sametime/images/stwordmark.gif" width=225 height=66 alt="| + GetString(40) + |" border=0></a>|
Print|</td>|
Print|</tr>|
Print|</table>|
Print|<br>|
Print |<DIV STYLE="font-size:large; font-weight:bold;">|
Print GetString(39)
Print |</DIV>|
Print |<br>|
Print displayMessage
Print |<br><br>|
Print |<a href="| + pathrelroot + |stcenter.nsf">Wheelock Online Meeting Center Home</a>|
Print|</BODY>|
Print|</HTML>|