AllWebMenus Lets You Create Unique and User Friendly Menus
Web publishers and developers today are luckier as they can enjoy so many advanced and affordable tools readily available on the internet in upgrading their websites. One of these is the menu maker which allows users to provide a site to their visitors that can easily be navigated when searching for specific categories.
The AllWebMenus is a popular name when it comes to creating menus. It is a DHTML/JavaScript menu maker that can be used even by an amateur web master or publisher. Whatever type of menu you want, it can help you create one that suits your style. No need for any experience on Dynamic HTML or JavaScript as long as you follow instructions correctly.
AllWebMenus is capable of creating different types of menus in absolutely unique designs and shapes such as the popup, hidden and drop-down. For the drop down menu, you can customize it to be the vertical or horizontal type and according to the designs you like at a very minimal fee. You can choose whether you’d want your menu to remain visible while scrolling, feature static or animated images, borders or be the movable type. Users also have a choice when using special effects such as the CSS, AJAX and the sliding effects.
The best part is the availability of attractive themepacks and templates you can use, many of which you may have not seen before on websites. They boast of great color combinations very unlike the usual white background you see on many sites. Additionally, you won’t have to worry about compatibility issues with platforms because this tool supports the DHTML of all platforms – Windows, Mac and Unix. It also works well with all browsers such as the Internet Explorer, Firefox, Mozilla, Safari and Chrome.
It’s simple to create a menu using DHTML or JavaScript as you only need to apply the tree-like approach. Customization can then be achieved using several features via the Properties Pane or by selecting a predefined look from the theme gallery. When you have finally completed your settings for your menu, it’s quick to do the finishing touches. You just use the Compile menu and Link menu commands so that your newly designed web menu shows on your web pages. It’s really that easy. No complex codes needed, just your patience and creativity.
This tool, you should know, can help in search engine optimization as well through its sitemap feature. It lets you create an optimized page with all the links found in your menu. All you need is to add a link to this page from your site’s index page and the search engines will be happy to crawl all the URLs in your menu.
Indeed so many amazing things are happening these days on web development and this AllWebMenus menu builder is definitely one of them that should not be taken for granted. If you’d like to increase your site’s traffic and earn more profits, you have to take a closer look at your menu and consider using this latest menu builder to achieve your goals. This is truly a must have tool for any web developer.
(Sponsored Post)
Want an avatar? Get a gravatar! • You can link to this comment
Navigation is certainly one of the key elements of a good website, but I’m not entirely sure I can agree with your glowing review. I can’t speak for AWM’s current version, so maybe it’s improved drastically since I last dealt with it a year ago, but: I used to be the webmaster for a site whose navigation menu used AllWebMenus code, and it was just atrocious to deal with. Navigation that should have been described via meaningful markup as an unordered list with a series of list items was instead locked up in one of the no fewer than eight .js files (most of them obfuscated) that the menu required in order to work properly. In order to one single item to the navigation, you had to dig through literally hundreds of lines of javascript to find the menu declaration, then add the item by adding a ridiculous line like:
m.add(0, 0, 0, "", 0, null, "", "Home", "index.html", "", "", null, 0);On top of the difficulty in maintaining the menu, there was of course the issue that because the actual content of the navigation was hidden in a .js file and not contained in the markup sent to the browser, screen readers or other users without javascript enabled would never see that content and could not navigate around the site.
Finally, after two years of faithful service, the thing began to be prone to display issues (aside from the ones that it had exhibited throughout its life, including off-by-fifteen-pixels behavior that made the thing more of a puzzle than a navigation system in FireFox) and had to be replaced. So, I wrote a replacement using jQuery, and replaced the eight obfuscated .js files representing hundreds of lines of code with one file which contained forty, ten of which were comments. It’s really not that hard to make a drop-down menu with jQuery, so if you’re able to, I’d really advise just doing it instead of using prefab code like AWM’s.
In short: I had a basically terrible time inheriting and maintaining AllWebMenus code, and would not in fact recommend it; given the strength of Lorraine’s recommendation, though, maybe things have changed. I guess what I’m trying to say is: be careful
Want an avatar? Get a gravatar! • You can link to this comment
Yikes. Sponsored much?
Want an avatar? Get a gravatar! • You can link to this comment
Ha. Hm. Definitely didn’t see the “(sponsored post)” text. That’d basically explain the situation.
Want an avatar? Get a gravatar! • You can link to this comment
Hello,
We are Likno Software, creators of AllWebMenus. We thank you for your feedback and are sorry to hear that you where not satisfied with the program or its functionality.
We have carefully read your comments about the program and would like to address the points you make in order to help users better understand the use of the program and its implementation.
– > I used to be the webmaster for a site whose navigation menu used AllWebMenus code, and it was just atrocious to deal with. Navigation that should have been described via meaningful markup as an unordered list with a series of list items was instead locked up in one of the no fewer than eight .js files (most of them obfuscated) that the menu required in order to work properly. In order to one single item to the navigation, you had to dig through literally hundreds of lines of javascript to find the menu declaration, then add the item by adding a ridiculous line like:
m.add(0, 0, 0, “”, 0, null, “”, “Home”, “index.html”, “”, “”, null, 0);
Indeed, the point you make regarding the code being Obfuscated is correct. The reason for this is that AllWebMenus is a program that is meant to be used via its interface, and not through its code. We do not encourage the manual editing of the code created for reasons such as:
1. Changes to the code alter possible editing when recompiling the menus. In other words compiling will not include changes made externally.
2. Changes to the code may ruin the end-result if you miss-out on something, while the use of the interface guarantees that all required changes are made to create the result you want.
Finally, about the use of 8 .js files: Basically, not all files are called/used. Only the one related to the browser being used. There is an internal ‘sniffing code’ that determines the browser used and the specific .js related to the browser is then called. What this offers is optimization for each and every browser.
– > On top of the difficulty in maintaining the menu, there was of course the issue that because the actual content of the navigation was hidden in a .js file and not contained in the markup sent to the browser, screen readers or other users without javascript enabled would never see that content and could not navigate around the site. Finally, after two years of faithful service, the thing began to be prone to display issues (aside from the ones that it had exhibited throughout its life, including off-by-fifteen-pixels behavior that made the thing more of a puzzle than a navigation system in FireFox) and had to be replaced.
We would have to check the project file to be able to determine the cause for this issue, as this might have been a result of what we already stated above, which is that manual changes to the code do cause problems.
Finally, we would like to encourage you and any other users facing difficulties or problems with the program, to use our support email and contact us with any issues. We are more than glad to help. You can contact us at: support@likno.com and one of our agents will assist you accordingly.