Hey everybody!

We wanted to take this opportunity to wish each and everyone of you a merry Christmas and a happy and successful 2010!

We thank you for your continuous  support!

Note: Support will be scarce this holiday season.

Regards,
The Likno Software Team

 

 

- Performed changes to overcome possible issues with the registration process in Windows Vista and 7.

- Added an automatic hide of the UL/LI structure (when used), so that you may remove the "left:-999px" attribute if you wish. This has some pros and cons.

- Added some notes on the interface regarding the proper Image and Element positioning (ID is *case-sensitive*, etc.).

- Fixed a glitch in the previous build where changing the Assigned Style crashed the application (on certain configurations only).

- Fixed an issue where the item Background Color was not correct if a CSS value was applied to the document (Mozilla only).

- Added a note at the "Welcome" screen informing trial users that the compile/link functionality is not available on Trial Mode.

- Fixed an issue with the WordPress Add-in. If a "&" symbol existed, the "Insert/Update menu structure" process was not successful.

- Fixed a minor issue regarding the "Auto Item Highlight" feature when combined with the "Automatically open submenus" feature.

- Fixed an issue where the "Auto Item Highlight" didn't work properly in "Server-Side Menus API" implementations.

- Released new versions of the Server-Side Menus API, Joomla and WordPress Addins to include the "Auto Item Highlight" fix.

- Updated the IE6-only fix where the "Hide Fix" for hiding "select boxes" didn't work properly.

 

Tags: , , , , , , , , ,

 

Hey everybody!

Here is one of our Likno tips... read on!

About the "left:-999px;" attribute when you use the <UL><LI> menu structure method

The AllWebMenus engine automatically hides the <UL><LI> structure when it detects it, so that these links do not visually interfere with the contents of the page (the <UL><LI> structure is used to populate the menu, which is then displayed instead of the links).

The "left:-999px;" attribute on the 1st <UL> tag is used additionally, so that the <UL><LI> structure is hidden for a period of some milliseconds before AllWebMenus detects it and hides it with its own method.

While it is good to keep this attribute so that you do not see the structure "appear/disappear" for some milliseconds, you may decide not to keep it if you wish your links to be visible on browsers that do not support javascript (or have it disabled). Keep in mind however that this way the structure will always be visible until the menu starts loading (in the majority of users that do have javascript on their browsers).

 

Tags: , , , ,

 

Hey everybody!

We are happy to inform you that the latest version of AllWebMenus - v5.2 build #804 - has been released!

Check out the new features and fixes added in this version:

- New "SEO CSS Menu Addin": Create SEO friendly menus (dropdown menus or sliding menus) through "sitemap-based SEO" or "on-page SEO". read more

- Themes and Examples are now combined into a single form.

- Added a new example (mega drop-down menu) into the application.

- The interface now remembers the last selected tab in the "UL/LI structure" form.

- Fixed an issue (IE6 only) where the "Hide Fix" for hiding "select boxes" didn't work properly.

- Fixed an issue where if an image was used along with text in an item, the image did not properly align vertically.

- Fixed an issue where a warning appeared in firefox 3.5 regarding -moz-opacity css declaration.

- Fixed an issue with the "Auto Highlight" feature: a sliding submenu was not opening if its parent item was clicked (and page was changing).

- Fixed a menu positioning issue when the "UL/LI" option was used: the menu was not positioned correctly on its positioning element.

- Added support for the "onclick event" and "link target" on "UL/LI" menu structures.

You can download the latest version at
http://www.likno.com/download.html

 

Tags: , , , , , , , , , , , ,

 

The "Menu Structure Source" property allows you to specify how your menu is populated with menu items (and submenus):

Option 1
(default option)

Using the project's structure, i.e. items that you add to your AllWebMenus project. These items are fetched from its compiled project's file.

Option 2

"On-the-fly", using <UL><LI> items fetched from the loaded page that shows the menu.

Menu Structure (items/submenus that populate the menu)
Your menu uses the same menu structureon different pages.This structure is edited within AllWebMenus and compiled to a single javascript file used by all your web pages.With this option, you do not have to add any menu items (<UL><LI> HTML code) on each page of your website.

When you want to change your menu, you just edit it, re-compile and re-upload its related files and you are done (for all your web pages).

Your menu can use a different menu structure on different pages. (optional)How?

Since the menu is built "on-the-fly", based on <UL><LI> tags inside your pages' HTML code, you can use different tags for different pages, thus creating a menu with different items/submenus.

With this option, to update your menu structure requires that you update all web pages containing its <UL><LI> menu structure.

Styles (appearance/behavior)
The menu appearance is based on the styles of Style Editor andany *custom*, item-specific style values you add.Every single item/submenu can be different if you like. The menu appearance is based on the styles of Style Editor only.Any *custom*, item-specific style values are *ignored*.

All items using the same style appear the same (no further customizations).

(note: the project's structure is still used in "Menu Preview Pane" to show you sample items when designing your menu)

Menu execution/rendering
The menu starts executing while the page is still loading, not after. The menu always appears after the page is fully loaded.The menu engine starts building the menu only after the entire page is fully loaded. With this technique, the existence of any nested tags do not break the execution and rendering of the menu.The only minimal "effect" of this option is that your menu appears after the page is fully loaded, not as quickly as in the other option. However, this is very minimal and unnoticeable in most cases, as the menu files are cached after visiting the first page that contains them.
SEO capabilities
Both "sitemap-based SEO" and "on-page SEO" Read more on SEO options Both "sitemap-based SEO" and "on-page SEO"(note: "on-page SEO" is inherent here)

Example of the <UL><LI> menu structure (option 2):

<ul id="awmULLI-menu" style="position:absolute;left:-999px;">
<li><a href="index.html">Home</a></li>

<li><a href="item1.html">Item 1</a></li>

<li><a href="item2.html">Item 2</a>

<ul>

<li>Item 2.1

<ul>

<li><a href="item_211.html">Item 2.1.1</a></li>

<li><a href="item_212.html">Item 2.1.2</a></li>

<li><a href="item_213.html">Item 2.1.3</a></li>

<li><a href="item_214.html">Item 2.1.4</a></li>

</ul>

</li>

<li><a href="item_22.html">Item 2.2</a>

</li>

</ul>

</li>

<li><a href="item3.html">Item 3</a>

</li>

</ul>

When added to a page linked to your menu, the above <UL><LI> HTML code produces the following menu structure "on-the-fly":

<UL> <LI> sample menu structure

Online Example: http://www.likno.com/examples/seo-css-menu.html

You may also read the related HELP topic inside AllWebMenus, which provides more details on this feature.

 

Tags: , ,

 


© 2009-2013 Likno Blog – Drop-Down Menus, Javascript Menus, CSS Menus, jQuery Scrollers/Sliders, Modal Windows