Similarly to the "Relative to Window" option, this option does not require any additional code on the page (apart from the menu-linking code). Relative to an Image on the page (eg: "logo.gif") You must also make sure when designing your menu that you choose the "Relative to an Element" positioning at the property of the Main Menu group, as shown in the picture below:įailing to do so will cause your menu to appear at the "Relative to Window" position instead (if this default option is selected on the project). This automatically inserts a span element that contains the related "Anchor ID" at that particular location of your page. To do so, place your cursor at your desired location inside your page and then press the "Position linked menu at cursor's position" command. However, if you want your menu to be positioned related to a page element, then some extra piece of code needs to be inserted next to that page element. Relative to an Element on the page (eg: span, div, table, td, etc.) In this case you do not need to take any further action to position your menu, apart from just linking the menu to the page. There are three ways to position your menu:īy default, the menu appears at its "Relative to Window" positioning coordinates that are specified at design time within AllWebMenus. In DreamWeaver your web site structure will appear as follows: Step 2: Specify your Site Root folder in AllWebMenusĪllWebMenus needs to know where your web site is locally stored.Īs shown below, click on "Tools Project Properties", select the "Folders" option and enter the "Site_Root folder": Step 3: Choose your positioning method This means that the HTML files that you wish to contain your menu are located inside that folder: Suppose that you are using your favorite web authoring tool to create a web site under the C:\SiteRoot local folder. Step 1: Specify the HTML pages where your menu will appear The Dreamweaver Extension is not required for using AllWebMenus with Dreamweaver however, it strongly facilitates the menu-linking and menu-positioning processes. Update: version 0.6 adds support for rel-license, and is loaded up with CC defaults.AllWebMenus has a very simple and intuitive way for linking your menus to your web pages, with or without the help of the Dreamweaver Extension. Update: version 0.5.1 now supports rel-tag too. All that will depend on your feedback, of course, so you can either leave a comment here, email me, or email the WaSP and let us know what you think. Hopefully we can improve those three and add some more in the near future. The first public beta is available on the WaSP site.Īt the moment we only have support for hCalendar, hCard and XFN, but it’s a start. So whilst listening to Tantek’s Microformats presentation at SXSW, I thought it would be pretty cool if we at the DWTF put together some basic extensions to help provide support in Dreamweaver. As a rapidly evolving area of development, it makes more sense for support for Microformats to be implemented as a Dreamweaver Extension rather than wait for a 18 month-ish product cycle to come around only to find it’s all changed. Whilst a lot of our effort to date has been to work alongside Macromedia (after all, there’s no point us tell you guys to use standards if the tool makes it hard to do so), there are some things it’s not reasonable to expect the Dreamweaver engineers to tackle right away. The other part of the remit of the Dreamweaver Task Force is to work with the online Dreamweaver community to encourage and assist in the adoption of web standards. The fact that web standards have become a strong selling point over the last few years means that they’ve had the opportunity to devote a lot of time to standards in the most recent couple of version. Fortunately for us, this has been pretty easy as the guys over at Macromedia are very receptive and very smart. For the last five years or so, this has meant working with the Dreamweaver team to try and encourage them to fix things that generate bad markup and to add better support for things like CSS. As you may or may not know, one of my jobs over at the Web Standards Project is to be involved with the Dreamweaver Task Force.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |