A new option has been added in AllWebMenus v5.1.796, allowing you to change the Doctype of the Preview Pane (additional to the existing Encoding option):

DocType in AllWebMenus Preview

Before Build #796, the Preview Pane was always using the Doctype "XHTML 1.0 Transitional".

However, if you used a different Doctype in your actual pages (where your menu was linked to), you may had experienced differences in how the menu was rendered at Preview Pane vs those pages. The same applied for Encoding.

This inconsistency is solved through the "Doctype" property, where you can use any of the following options for the Menu Preview Pane:

None
HTML 4.01 Transitional
HTML 4.01 Strict
XHTML 1.0 Transitional (default)
XHTML 1.0 Strict
XHTML 1.1

Now, it is important to understand that both the "Doctype" and the "Encoding" values are used in previewing the menu within AllWebMenus only and are not applied to your actual pages. Your pages will have their own HTML code for Doctype and Encoding and therefore the menu will be rendered according to those values; NOT according to the Menu Preview values. The Menu Preview options are there just to facilitate the preview.

 

 

Since AllWebMenus v5.1.764, your menus can use 3 different styles for their groups and 3 different styles for their items:

Main Group Style
(initially assigned to the Main Menu Group, i.e. 1st level group)

Main Items Style
(initially assigned to the items of the Main Menu Group, i.e. 1st level items)

Sub Groups Style
(initially assigned to the 1st submenus stemming from the Main Menu items, i.e. 2nd level groups)

Sub Items Style
(initially assigned to the 1st submenu items contained in the above submenus, i.e. 2nd level items)

Sub Groups Style+
(initially assigned to the rest of submenus stemming from the above items, i.e. 3rd level groups and beyond)

Sub Items Style+
(initially assigned to the rest of submenu items contained in the above submenus, i.e. 3rd level items and beyond)

This is how a menu would look if the <Background Color> and <Border> on every item or group had the above colors that demonstrate the initial style assignments:

Available Styles menu

Note: The above assignments are the initial ones. If you wish, you can later change the assignments as wish.


Why is the 3rd style (i.e. "Style+") useful?



1. You can use themes that have different appearance on 3rd-level submenus and beyond:

Themes that use this technique: Juice, Fading Purple, FlatSky, Orange Bubbles (free, contained in your AllWebMenus by default)
You may also find extra themes using this technique from Theme Pack 36 and above at: http://www.likno.com/awmthemes.php

For example, at theme "Olive Plastic" (Theme Pack 36), its 3rd-level items (and beyond) use less padding than its 2nd-level items:

At the SlideTreeXP sliding menu theme (Theme Pack 38, "Sliding Menu Add-in" required), the 3rd-level items do not use an icon, while the 2nd-level items do:

Such arrangements would not have been possible if all submenus had the same style.

2. You can apply very interesting behaviors to sliding menus (available through the extra "Sliding Menu Add-in"), that combine both "sliding" and "non-sliding" cascading submenus!

For example, the SlideSummer sliding menu theme below (Theme Pack 37, "Sliding Menu Add-in" required)) uses a sliding submenu for all its Main Menu items, while the rest of its submenus are the standard non-sliding ones. Such "sliding/non-sliding" menu combinations are very suitable in many website layouts and would not have been possible if all submenus had the same style.



3. The 3rd-level submenus can differ from the 2nd-level submenus by only a small but very important detail, that allows for a different design if the parent group is horizontal or vertical.

At the following examples the 2nd-level submenu does not have a "Header" (its <Has Header> property is set to "No"), while the 3rd-level submenu (and beyond) needs to have a "Header" so that the design closes properly at top:

At the following sliding menu themes (Theme Pack 38, "Sliding Menu Add-in" required) the 2nd-level submenus are different than the 3rd-level submenus, either in colors, images or indentation:

Different colors & indentation:

Different icons & indentation:

Different indentation:

 

 

The AllWebMenus Joomla Menu add-in & component combination is designed to retrieve your Joomla menu from your Joomla website and import it into the AllWebMenus application to create stylish, feature-rich navigation menus, but not only! Apart from creating menu items derived from your joomla menu structure, fully customize your menus adding your own non-joomla menu items with external or internal links, html-rich content, colors, borders, effects, designs of your choice and many more!

For instructions and suggestions about installation and use of the software combination, visit the relevant page in the Likno Web Site.

See examples of menus already inserted into a Joomla site in the AllWebMenus Joomla Menu examples page.

Now you can easily add in your Joomla site a stylish menu generated by the AllWebMenus PRO software!

Note: the AllWebMenus Joomla Menu add-in & component combination is supported in AllWebMenus PRO v5.1.758 and above.

 

 

These are the new features and fixes introduced in version 5.1.758 of AllWebMenus Web Menu Maker (released on December 3rd, 2008):

- The Joomla Menu Add-in & Component released and included in the distribution. Create stylish, feature-rich navigation menus based on the structure of your existing Joomla menu but not only! Fully customize your joomla menus adding your own non-joomla menu items with external or internal links, html-rich content, colors, borders, effects, designs of your choice and many more.

joomla menu addin

Joomla Menu examples

- New compile option added: The "Place dot.gif in" option, which allows the menu to function on rare server environments that require separate folders for javascripts and images. Read more

- Fixed an issue where the right image of an item (if used) did not appear properly (on Gecko browsers and some cases only).

- The Server-Side Menus API Add-in is now on version 2.0.9: Fixed an incompatibility between the API javascripts and MooTools (if used on your website).

- The WordPress Menu Add-in is now on version 1.0.4: It is now based on the new version 2.0.9 of the Server-Side Menus API Add-in (see above).

- Fixed an issue where the vertical scrollbar did not appear correctly in GUI when the user maximized the window.

 

 

These are the new features and fixes introduced in version 5.1.756 of AllWebMenus Web Menu Maker (released on November 11th, 2008):

- The GUI of the WordPress Menu Add-in has been enhanced.

- The "Tools -> Compile for..." command has been added for better handling of the Compile/Link process on different use cases or CMS/Tools.

text shortcuts

- Fixed an issue where the <Has Submenu Image> did not show properly in a vertical menu, on certain cases only.

 

 


© 2009 Likno Software Blog – Drop-Down Menus, Javascript Menus, DHTML Menus