Help - Search - Members - Calendar
Full Version: One Huge Document
xFX JumpStart Public Forums > DHTML Menu Builder > Application Related > General
Ch33t0 BuRRit0
Hello.

I create many large documents that require a more simple means of navigation. So, when I create a menu, I would like the menu items to refer to an "element id", or other such means of identifying points on the same page.

I'm still a bit new with this application. But right now, my only concern is directing the menu to different points. Either on the same web page or others.

Thank you for any help you might provide.

Peace.
)
JimS
I dont see any reason why you cannot create named bookmarks within your pages for the points on the page that you require to reader to go to. Then in DHTML Menu Builder when you have created the link to the page manually add #bookmarkname. (Example C:\MyDocuments\webSite\WebPage.htm#bookmarkname)
Hope this helps
regards
Ch33t0 BuRRit0
I'm sorry. I failed to include enough information in my first post.

To elaborate:

In the "project properties" dialog, the "local path" to my "root web", for these purposes, reads: "E:\My Documents\Work. The "HTML" document that the menu will be install to, as well as, have links to is: "work.html". Within this html document, all of my major "<div>'s" are labeled with "id's" &/or "classes".

Selecting a "group" or "command" item in the "map window", I set the "mouseover" and "doubleclick" actions to "none". On the "click" tab, the "open url/execute script" action is selected. Additionally, at this point, I've tried the method described in the above post by JimS. In the "url/script" box, I've inserted the string: " E:\My Documents\Work\Work.html#home ". I had thought, previously, that this was the location to insert such things. However, this does not seem to work. I've completed the menu by installing it to "work.html", and compiling the menu files to the default locations (..\images and ..\menus), but this did not remedy the matter.

Scenario:

I wish to have the "menu group" or "command" items on my menu, jump throughout the document to the position specified; using "id's", "classes" or "names". Additionally, if I should desire to have one of the menu elements (i.e. group or command items) change any html element's properties (i.e. css properties or entire class of any elements).

Complaint:

If there are any of the software designers or engineers of this Menu Builder software reading through this post, please take note of the following:

I have read through all of the documentation provided. I've looked through the samples given on the web. Additionally, I have read reviews. This application seemed to be the "cat's meow" of menu builders. However, I think that there is too much talk of the design possiblities, as opposed to various methods to make the menus functionable.

Since functionality is the prime objective of any design, the look and feel of any such, should take a back seat. Please try to incorporate this sort of approach when designing any tutorials, helpfiles, and assorted documentations. Perhaps dialogs might be added to ease the use of any such command approaches, perhaps akin to that described above.

Though. I beleive that the sort of functionality I describe above is entirely within the capabilities of this application, the ease of implementing this simple menu seems to have been beyond my first, second, and even third glance. Additionally, since I do have some good basic working knowledge of the languages in use here (html, javascripts), and the fact that I still had difficulty discovering how to apply these simple operations to my menus, I believe some design changes are in order.

Thanks again for any help.

Ch33t0 cool.gif
JimS
This forum is run by users of the programme (not designers) who do their best to help those who are struggling. I suggest that with your grasp of software design you download the 'Developers' version and get on with it!!
Ch33t0 BuRRit0
Oh my. I've been completely humbled.

I don't know what I might have done the first few times trying this approach to have it come up wrong. But, I finally did get that approach to work Jim. The "url/script" box was the place to insert that string. Just as I had suspected, and you had instructed me. I wonder how that string is stored? I'm curious if it is just store with a relative address, versus, the literal "E:\My Documents\Work\work.html#home". It seems that the only need is for the relative addy. I ask this because it is not obvious. It seems to me, if it does store the literal address, moving the files from my computer "E:\" to the web would cause issues.

On another issue: I'm sorry if my last post seemed too stiff for you Jim. Judging from your response, you seem a bit put off by my last. I know that it can sometimes be difficult to express enough information to get ones point across. That was why I was as descriptive as I was with my verbage. And, as far as, my criticism per my last post is concerned: It was directed at those whom were stated. If that is not you, then there is no need to take it personal.

Anywayz, thanks again for the help Jim.

Ciao.
JimS
Dear Ciao

Although in the main window the programme sets up the links as per your local computer when you publish and compile your project to your web site the programme will automatically create the correct internal links and relationships within your site so that when published all the links work correctly.

The basic programme and tutorials have been designed by Xavier for people who want to create dynamic javascript menus with little or no programming knowledge or experience. The 'Developers Edition' has been designed for programmers who have the knowledge to go one stage further (perhaps yourself) Having bought the basic programme you can upgrade to the Developer Edition for free if you wish.

The support you will get there is just as good (not from me, I am not that clever)

Have a nice Christmas

regards
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2012 Invision Power Services, Inc.