Menu behind spry slideshow dreamweaver cs5?

Using Dreamweaver CS5
Hi.  I have a site with a css3 dropdown menu that seems to work fine on all of my pages except my photo gallery page. The menu appears behind the Spry Slideshow with Filmstrip that I got from the Widget Browser.
The site is not live and only on my local machine but here is the page html in a text doc: http://www.210usa.com/index.txt
Here is the main css: http://www.210usa.com/css_prob.txt
Here is the slideshow css: http://www.210usa.com/css_slideshow.txt
I have changed the z index but that is not helping at all.  I found this for problems with flash docs but I am a real novice and do not know how to even put these tags in my code.  Any help would be greatly appreciated.
Thanks

Grüss Dich sailor,
in my opinion "SpryTabbedPanels" actually only do what they should to do and so it inevitably leads to the covered menu items. I played a little bit around with the width from your "css3menu1/style.css"
height:22px;line-height:22px;border-width:0 0 3px 0;border-style:none;border-color:#009900;border-radius:10px;-moz-border-radius:10px;-webk it-border-radius:10px;padding:3px 10px; width: 650px;}
and I got this:
so you can see what I mean. To correct this you had to put down your "photo gallery for Mystic Pizza II" so far, till there is enough space for the panel. And therefore I would prefer a solution by using a "SpryMenuBarVertical" leftmost on your page (if you mean it's necessary so too on the right).
Glück auf!
Hans-Günter

Similar Messages

  • Spry tooltips dreamweaver cs5

    hi
    i'm new in the forum and hope i'm doing things right...
    searched the forum for hours and couldnt find a solution. my problem:
    built a tooltipp for a small image (100x100px) and replace it with a bigger one (300px sq). when i set the offset both to negative, the tooltip is shaking like mad when i hover over. there is only the img in the div. i added some margin and padding to the the class '.tooltipContent'.
    tried to do it in a new html file (dreamweaver template, without any additional css) but it didnt work out - many thanks for any help!!
    would be a great tool and a shame if i couldn't use it!
    raphael

    hi gramps
    many thanks! when i turn on the second box (according the reccommendation), the flickering is gone.
    i'm not sure if have to remove the width and heigth as well - seems to work without removing it. please let me know if there are any reason to do so.
    again many thanks - searched the forum for a long time, but im not english and didnt look up "flicker" ...
    nice weekend
    raphael

  • Help with Dreamweaver CS5 spry menus. Menu is not dropping down in IE7.

    Hello.
    We recently upgraded from GoLive CS3 to Dreamweaver CS5. Wow! This has been a big change for us. We are having trouble with a website that we are building, specifically the Spry Menu drop downs not appearing correctly in IE7 and older. While the dropdown menu appears in other browsers, it is not dropping down at all in IE7 and earlier versions. After researching this topic on many websites, including this forum, we are still unable to resolve our particular issue. We have tried many of the suggestions that are common to our problem, but have not found a solution as yet. Could someone please check out this page for us, and possibly give us some advise. We are working on Mac OSX. Thank you in advance for any suggestions you may offer.
    http://www.advertools.net/pgtdemo/index.html

    When I added the following to the document
    <style>
    #main_image {position:static;}
    </style>
    the menu items appeared albeit in the wrong position.
    The reason for the hidden menu items is because #main_image had a position of relative, effectively creating a flow of its own rather than following the natural flow of the document.
    Now for the postion of the submenu. If I add the following style rules to the document the submenu items are in the correct position
    ul.MenuBarHorizontal li {text-align: left;}
    ul.MenuBarHorizontal a {text-align: center;}
    In the first line I have reset the rule that you had changed to center align and in the second line (which is not in the original CSS) I have aligned the text in the anchor tag to align center.
    The reason is that IE<8 behaves differently to other browsers when it comes to list items causing the nested list items (submenu) to align themselves to the center of the text of the parent list item.
    I hope the above helps.
    Gramps

  • Please can someone provide me with Spry Menu Bar Horizontal code for Dreamweaver CS5.5?

    Please can someone provide me with Spry Menu Bar Horizontal code for Dreamweaver CS5.5?

    Log-in to the Adobe Exchange with your Widget Browser and grab "Spry Menu 2.0."
    http://labs.adobe.com/technologies/widgetbrowser/
    In Widget browser, style the menu as desired and Save files to your DW Local Site folder.
    Nancy O.

  • Dreamweaver CS5 cannot access blue spry menu

    Whenever I use a spry menu I have this problem where it is not possible to see the little blue menu bar that allows you to edit your menus.
    WHY? I have searched forums, searched the internet but no answers. Okay I have seen other people ask the same problem but als their threads end with no solution. Sometimes it shows, mostly it doesn't
    So please can someone help as to why I cannot see or access the little blue spry menu bar?
    Cheers Dean

    Thanks for the help.
    I have created a new document and inserted a horizontal spry menu, I still have the same problem
    Here is hopefully the code you require.
    Thanks
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <title>Untitled Document</title>
    <style type="text/css">
    <!--
    body {
        font: 100%/1.4 Verdana, Arial, Helvetica, sans-serif;
        background: #42413C;
        margin: 0;
        padding: 0;
        color: #000;
    /* ~~ Element/tag selectors ~~ */
    ul, ol, dl { /* Due to variations between browsers, it's best practices to zero padding and margin on lists. For consistency, you can either specify the amounts you want here, or on the list items (LI, DT, DD) they contain. Remember that what you do here will cascade to the .nav list unless you write a more specific selector. */
        padding: 0;
        margin: 0;
    h1, h2, h3, h4, h5, h6, p {
        margin-top: 0;     /* removing the top margin gets around an issue where margins can escape from their containing div. The remaining bottom margin will hold it away from any elements that follow. */
        padding-right: 15px;
        padding-left: 15px; /* adding the padding to the sides of the elements within the divs, instead of the divs themselves, gets rid of any box model math. A nested div with side padding can also be used as an alternate method. */
    a img { /* this selector removes the default blue border displayed in some browsers around an image when it is surrounded by a link */
        border: none;
    /* ~~ Styling for your site's links must remain in this order - including the group of selectors that create the hover effect. ~~ */
    a:link {
        color: #42413C;
        text-decoration: underline; /* unless you style your links to look extremely unique, it's best to provide underlines for quick visual identification */
    a:visited {
        color: #6E6C64;
        text-decoration: underline;
    a:hover, a:active, a:focus { /* this group of selectors will give a keyboard navigator the same hover experience as the person using a mouse. */
        text-decoration: none;
    /* ~~this fixed width container surrounds the other divs~~ */
    .container {
        width: 960px;
        background: #FFF;
        margin: 0 auto; /* the auto value on the sides, coupled with the width, centers the layout */
    /* ~~ the header is not given a width. It will extend the full width of your layout. It contains an image placeholder that should be replaced with your own linked logo ~~ */
    .header {
        background: #ADB96E;
    /* ~~ These are the columns for the layout. ~~
    1) Padding is only placed on the top and/or bottom of the divs. The elements within these divs have padding on their sides. This saves you from any "box model math". Keep in mind, if you add any side padding or border to the div itself, it will be added to the width you define to create the *total* width. You may also choose to remove the padding on the element in the div and place a second div within it with no width and the padding necessary for your design. You may also choose to remove the padding on the element in the div and place a second div within it with no width and the padding necessary for your design.
    2) No margin has been given to the columns since they are all floated. If you must add margin, avoid placing it on the side you're floating toward (for example: a right margin on a div set to float right). Many times, padding can be used instead. For divs where this rule must be broken, you should add a "display:inline" declaration to the div's rule to tame a bug where some versions of Internet Explorer double the margin.
    3) Since classes can be used multiple times in a document (and an element can also have multiple classes applied), the columns have been assigned class names instead of IDs. For example, two sidebar divs could be stacked if necessary. These can very easily be changed to IDs if that's your preference, as long as you'll only be using them once per document.
    4) If you prefer your nav on the right instead of the left, simply float these columns the opposite direction (all right instead of all left) and they'll render in reverse order. There's no need to move the divs around in the HTML source.
    .sidebar1 {
        float: left;
        width: 180px;
        background: #EADCAE;
        padding-bottom: 10px;
    .content {
        padding: 10px 0;
        width: 780px;
        float: left;
    /* ~~ This grouped selector gives the lists in the .content area space ~~ */
    .content ul, .content ol {
        padding: 0 15px 15px 40px; /* this padding mirrors the right padding in the headings and paragraph rule above. Padding was placed on the bottom for space between other elements on the lists and on the left to create the indention. These may be adjusted as you wish. */
    /* ~~ The navigation list styles (can be removed if you choose to use a premade flyout menu like Spry) ~~ */
    ul.nav {
        list-style: none; /* this removes the list marker */
        border-top: 1px solid #666; /* this creates the top border for the links - all others are placed using a bottom border on the LI */
        margin-bottom: 15px; /* this creates the space between the navigation on the content below */
    ul.nav li {
        border-bottom: 1px solid #666; /* this creates the button separation */
    ul.nav a, ul.nav a:visited { /* grouping these selectors makes sure that your links retain their button look even after being visited */
        padding: 5px 5px 5px 15px;
        display: block; /* this gives the link block properties causing it to fill the whole LI containing it. This causes the entire area to react to a mouse click. */
        width: 160px;  /*this width makes the entire button clickable for IE6. If you don't need to support IE6, it can be removed. Calculate the proper width by subtracting the padding on this link from the width of your sidebar container. */
        text-decoration: none;
        background: #C6D580;
    ul.nav a:hover, ul.nav a:active, ul.nav a:focus { /* this changes the background and text color for both mouse and keyboard navigators */
        background: #ADB96E;
        color: #FFF;
    /* ~~ The footer ~~ */
    .footer {
        padding: 10px 0;
        background: #CCC49F;
        position: relative;/* this gives IE6 hasLayout to properly clear */
        clear: both; /* this clear property forces the .container to understand where the columns end and contain them */
    /* ~~ miscellaneous float/clear classes ~~ */
    .fltrt {  /* this class can be used to float an element right in your page. The floated element must precede the element it should be next to on the page. */
        float: right;
        margin-left: 8px;
    .fltlft { /* this class can be used to float an element left in your page. The floated element must precede the element it should be next to on the page. */
        float: left;
        margin-right: 8px;
    .clearfloat { /* this class can be placed on a <br /> or empty div as the final element following the last floated div (within the #container) if the #footer is removed or taken out of the #container */
        clear:both;
        height:0;
        font-size: 1px;
        line-height: 0px;
    -->
    </style>
    <script src="SpryAssets/SpryMenuBar.js" type="text/javascript"></script>
    <link href="SpryAssets/SpryMenuBarHorizontal.css" rel="stylesheet" type="text/css" />
    </head>
    <body>
    <div class="container">
      <div class="header"><a href="#"><img src="" alt="Insert Logo Here" name="Insert_logo" width="180" height="90" id="Insert_logo" style="background: #C6D580; display:block;" /></a>
        <!-- end .header --></div>
      <div class="sidebar1">
        <ul class="nav">
          <li><a href="#">Link one</a></li>
          <li><a href="#">Link two</a></li>
          <li><a href="#">Link three</a></li>
          <li><a href="#">Link four</a></li>
        </ul>
        <p> The above links demonstrate a basic navigational structure using an unordered list styled with CSS. Use this as a starting point and modify the properties to produce your own unique look. If you require flyout menus, create your own using a Spry menu, a menu widget from Adobe's Exchange or a variety of other javascript or CSS solutions.</p>
        <p>If you would like the navigation along the top, simply move the ul.nav to the top of the page and recreate the styling.</p>
        <!-- end .sidebar1 --></div>
      <div class="content">
        <h1> </h1>
        <ul id="MenuBar1" class="MenuBarHorizontal">
          <li><a class="MenuBarItemSubmenu" href="#">Item 1</a>
            <ul>
              <li><a href="#">Item 1.1</a></li>
              <li><a href="#">Item 1.2</a></li>
              <li><a href="#">Item 1.3</a></li>
            </ul>
          </li>
          <li><a href="#">Item 2</a></li>
          <li><a class="MenuBarItemSubmenu" href="#">Item 3</a>
            <ul>
              <li><a class="MenuBarItemSubmenu" href="#">Item 3.1</a>
                <ul>
                  <li><a href="#">Item 3.1.1</a></li>
                  <li><a href="#">Item 3.1.2</a></li>
                </ul>
              </li>
              <li><a href="#">Item 3.2</a></li>
              <li><a href="#">Item 3.3</a></li>
            </ul>
          </li>
          <li><a href="#">Item 4</a></li>
        </ul>
        <p> </p>
        <p> </p>
        <h1> </h1>
        <h1> </h1>
        <h1>Instructions</h1>
        <p>Be aware that the CSS for these layouts is heavily commented. If you do most of your work in Design view, have a peek at the code to get tips on working with the CSS for the fixed layouts. You can remove these comments before you launch your site. To learn more about the techniques used in these CSS Layouts, read this article at Adobe's Developer Center - <a href="http://www.adobe.com/go/adc_css_layouts">http://www.adobe.com/go/adc_css_layouts</a>.</p>
        <h2>Clearing Method</h2>
        <p>Because all the columns are floated, this layout uses a clear:both declaration in the .footer rule.  This clearing technique forces the .container to understand where the columns end in order to show any borders or background colors you place on the .container. If your design requires you to remove the .footer from the .container, you'll need to use a different clearing method. The most reliable will be to add a &lt;br class=&quot;clearfloat&quot; /&gt; or &lt;div  class=&quot;clearfloat&quot;&gt;&lt;/div&gt; after your final floated column (but before the .container closes). This will have the same clearing effect.</p>
        <h3>Logo Replacement</h3>
        <p>An image placeholder was used in this layout in the .header where you'll likely want to place  a logo. It is recommended that you remove the placeholder and replace it with your own linked logo. </p>
        <p> Be aware that if you use the Property inspector to navigate to your logo image using the SRC field (instead of removing and replacing the placeholder), you should remove the inline background and display properties. These inline styles are only used to make the logo placeholder show up in browsers for demonstration purposes. </p>
        <p>To remove the inline styles, make sure your CSS Styles panel is set to Current. Select the image, and in the Properties pane of the CSS Styles panel, right click and delete the display and background properties. (Of course, you can always go directly into the code and delete the inline styles from the image or placeholder there.)</p>
        <h4>Backgrounds</h4>
        <p>By nature, the background color on any div will only show for the length of the content. This means if you're using a background color or border to create the look of a side column, it won't extend all the way to the footer but will stop when the content ends. If the .content div will always contain more content, you can place a border on the .content div to divide it from the column.</p>
      <!-- end .content --></div>
      <div class="footer">
        <p>This .footer contains the declaration position:relative; to give Internet Explorer 6 hasLayout for the .footer and cause it to clear correctly. If you're not required to support IE6, you may remove it.</p>
        <!-- end .footer --></div>
      <!-- end .container --></div>
    <script type="text/javascript">
    var MenuBar1 = new Spry.Widget.MenuBar("MenuBar1", {imgDown:"SpryAssets/SpryMenuBarDownHover.gif", imgRight:"SpryAssets/SpryMenuBarRightHover.gif"});
    </script>
    </body>
    </html>

  • Drop-down menu in Dreamweaver CS5.5 not displaying

    Thanks for anyone's help.  I'm a first time user of the forum so please excuse any protocol errors.
    I can't get my drop-down menu to display on my web page (http://www.cglcontracting.com/) on a Windows platform using Dreamweaver CS5.5.
    Thanks very much for any advice/help.

    Hi again -
    My previous suggestion did not seem to make any difference, the CSS still did not validate.
    I seems to be choking on your Browser Hack section.
    http://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Fwww.cglcontracting.com%2FSpr yAssets%2FSpryMenuBarHorizontal.css&profile=css3&usermedium=all&warning=1&vextwarning=&lan g=en
    I re-wrote the bottom Browser Hack section and it now validates.
    I'll paste the whole CSS file here, Save it as "SpryMenuBarHorizontal.css" and give it a try.
    @charset "UTF-8";
    /* SpryMenuBarHorizontal.css - version 0.6 - Spry Pre-Release 1.6.1 */
    /* Copyright (c) 2006. Adobe Systems Incorporated. All rights reserved. */
    LAYOUT INFORMATION: describes box model, positioning, z-order
    /* The outermost container of the Menu Bar, an auto width box with no margin or padding */
    ul.MenuBarHorizontal
        margin: 0;
        padding: 0;
        list-style-type: none;
        font-size: 90%;
        cursor: default;
        width: auto;
        color: rgb(153,153,153);
        text-transform: uppercase;
        font-family: "Trebuchet MS", Arial, Helvetica, sans-serif;
        text-align: center;
        background-color: rgb(255,255,255);
        vertical-align: middle;
    /* Set the active Menu Bar with this class, currently setting z-index to accomodate IE rendering bug: http://therealcrisp.xs4all.nl/meuk/IE-zindexbug.html */
    ul.MenuBarActive
        color: rgb(153,153,153);
        z-index: 1000;
    /* Menu item containers, position children relative to this container and are a fixed width */
    ul.MenuBarHorizontal li
        margin: 0;
        padding: 0;
        list-style-type: none;
        font-size: 100%;
        position: relative;
        text-align: left;
        cursor: pointer;
        width: 8em;
        float: left;
        color: rgb(0,255,0);
        overflow: hidden;
        visibility: inherit;
    /* Submenus should appear below their parent (top: 0) with a higher z-index, but they are initially off the left side of the screen (-1000em) */
    ul.MenuBarHorizontal ul
        padding: 0;
        list-style-type: none;
        font-size: 100%;
        z-index: 1020;
        cursor: default;
        width: 8.2em;
        color: rgb(204,204,204);
        top: 0px;
        overflow: auto;
        visibility: inherit;
        margin-top: -5%;
        margin-left: 95%;
    /* Submenu that is showing with class designation MenuBarSubmenuVisible, we set left to auto so it comes onto the screen below its parent menu item */
    ul.MenuBarHorizontal ul.MenuBarSubmenuVisible
        color: rgb(204,204,204);
        font-family: "Trebuchet MS", Arial, Helvetica, sans-serif;
        font-variant: small-caps;
        text-transform: uppercase;
        background-color: rgb(255,0,0);
        left: auto;
        width: auto;
        z-index: auto;
        visibility: inherit;
    /* Menu item containers are same fixed width as parent */
    ul.MenuBarHorizontal ul li
        text-align: left;
    /* Submenus should appear slightly overlapping to the right (95%) and up (-5%) */
    ul.MenuBarHorizontal ul ul
        background-color: rgb(204,204,204);
        margin-top: -5%;
        margin-right: 0;
        margin-bottom: 0;
        margin-left: 95%;
    /* Submenu that is showing with class designation MenuBarSubmenuVisible, we set left to 0 so it comes onto the screen */
    ul.MenuBarHorizontal ul.MenuBarSubmenuVisible ul.MenuBarSubmenuVisible
        left: 100px;
        background-color: rgb(204,204,204);
    DESIGN INFORMATION: describes color scheme, borders, fonts
    /* Submenu containers have borders on all sides */
    ul.MenuBarHorizontal ul
        border: 0px none #CCC;
        margin-top: 0%;
        margin-right: 0%;
        margin-bottom: 0%;
        margin-left: 0%;
    /* Menu items are a light gray block with padding and no text decoration */
    ul.MenuBarHorizontal a
        display: block;
        cursor: pointer;
        background-color: #F00;
        color: #003;
        text-decoration: none;
        text-align: center;
        font-family: Arial, Helvetica, sans-serif;
        padding-top: 1.2ex;
        font-weight: bold;
        vertical-align: middle;
        padding-bottom: 0.53em;
    /* Menu items that have mouse over or focus have a blue background and white text */
    ul.MenuBarHorizontal a:hover, ul.MenuBarHorizontal a:focus
        background-color: #000;
        color: rgb(255,255,255);
        text-align: center;
    /* Menu items that are open with submenus are set to MenuBarItemHover with a blue background and white text */
    ul.MenuBarHorizontal a.MenuBarItemHover, ul.MenuBarHorizontal a.MenuBarItemSubmenuHover, ul.MenuBarHorizontal a.MenuBarSubmenuVisible
        background-color: #900;
        color: #066;
        text-align: center;
        vertical-align: middle;
    SUBMENU INDICATION: styles if there is a submenu under a given menu item
    /* Menu items that have a submenu have the class designation MenuBarItemSubmenu and are set to use a background image positioned on the far left (95%) and centered vertically (50%) */
    ul.MenuBarHorizontal a.MenuBarItemSubmenu
        background-image: url(SpryMenuBarDown.gif);
        background-repeat: no-repeat;
        background-position: 98% 50%;
        background-color: rgb(255,0,0);
        color: rgb(0,0,51);
    /* Menu items that have a submenu have the class designation MenuBarItemSubmenu and are set to use a background image positioned on the far left (95%) and centered vertically (50%) */
    ul.MenuBarHorizontal ul a.MenuBarItemSubmenu
        background-image: url(SpryMenuBarRight.gif);
        background-repeat: no-repeat;
        background-position: 98% 50%;
        background-color: rgb(204,204,204);
        visibility: inherit;
    /* Menu items that are open with submenus have the class designation MenuBarItemSubmenuHover and are set to use a "hover" background image positioned on the far left (95%) and centered vertically (50%) */
    ul.MenuBarHorizontal a.MenuBarItemSubmenuHover
        background-image: url(SpryMenuBarDownHover.gif);
        background-repeat: no-repeat;
        background-position: 98% 50%;
        background-color: rgb(153,0,0);
        visibility: visible;
    /* Menu items that are open with submenus have the class designation MenuBarItemSubmenuHover and are set to use a "hover" background image positioned on the far left (95%) and centered vertically (50%) */
    ul.MenuBarHorizontal ul a.MenuBarItemSubmenuHover
        background-image: url(SpryMenuBarRightHover.gif);
        background-repeat: no-repeat;
        background-position: 98% 50%;
        background-color: rgb(153,153,153);
    BROWSER HACKS: the hacks below should not be changed unless you are an expert
    /* HACK FOR IE: to make sure the sub menus show above form controls, we underlay each submenu with an iframe */
    ul.MenuBarVertical iframe
        position: absolute;
        z-index: 1010;
    /* HACK FOR IE: to stabilize appearance of menu items; the slash in float is to keep IE 5.0 from parsing */
    @media screen, projection
        ul.MenuBarVertical li.MenuBarItemIE
            display: inline;
            f\loat: left;
            background: #FFF;

  • Dreamweaver CS5 webdesign lay-out problem + spry

    Hello there
    I'm making a site, but I'm encountering some problems. I'm making one in Dreamweaver CS5 with CSS-styles. I decided to work with percentages to build up my site.
    So my container has following measurements: containeris min-width: 640, max-width: 1920, width: 75% (to have 2 white backgroundcolums next to my site).
    My sidebar is width: 21%, float:left and content is width 79%, float:right
    I arranged the lay-out of my menu with submenu, placed in sidebar, with a sprymenubarvertical from Dreamweaver.
    When I open up the site on my Dell E6510 laptop, the site looks as the first picture of below, so everything works fine!
    When some computers, especially older ones open it up, the get the second picture.
    So can anyone help me figuring out why:
    - The content is now placed UNDER my menu and not next to eachother?
    - Why did my menu turn white, did I loose my background image of it, and does he show the a:hover as normal?
    - Same as above for the submenu...
    Then I'm having another problem: If I make the screen smaller of my browser, like half of the page, he shrinks the sidebar and content, but he doesnt shrink the font + the gallery from my content doesn't shrink either.
    Also, the slideshow, made with Aleo slideshow maker, doesn"t show on mac.
    Could this be solved by just making the widths fixed or is there another solution? Also, the slideshowgallery has a fixed width(as imported), how to make that automaticely go smaller if you shrink the screen?
    Any tips would we convenient!
    (http://www.maxx-it.be/Aanbod/Webdesign/mira.html)
    The first picture is how it should be, second one is taken from how other computers see the site, third one is if I shrink the screen
    Thanks alot you guys
    Greetz
    MasterJ09

    I'm sorry didn't mean to send any corrupted files or links.
    In case it would help I added a link here where I uploaded my style.css, and my sprymenubar styles, with the basic template and the indexhtmlpage through Megaupload. I added the printscreens as well. I hope this will work.
    If this isn't the right method of posting please tell me how to?
    Thanks in advance!

  • Download spry table for Dreamweaver CS5

    Hi All,
    I have upgraded to dreamweaver CS5 recently.
    However, I cannot find the spry table in the menu.
    Where can I download the spry table from interenet?
    Thanks for help
    Kenny

    Han-G,
    Thanks for you help.
    Actually, the spry table is installed but the spry table icons were missed in the menu bar.
    Kenny

  • Creating a slideshow using dreamweaver cs5

    Hi guys I was wondering how do you create a slideshow in dreamweaver cs5, I was watching a guy do it in dreamweaver cs4 but i could not find the flash elements panel.
    Thanks

    Do a Google search on "jQuery Slideshows"   Behold! A wonderland of slideshow plug-ins!
    Cool this is about jQuery slide-shows is that they all work basically the same way, so once you go through the learning curve of implementing one you'll be able to use any of them. This way you don't have to be locked in to a particular look. You can use what will look best for each site.
    Enjoy!
    Lawrence Cramer - *Adobe Community Professional*
    http://www.Cartweaver.com
    Shopping Cart for Adobe Dreamweaver
    available in PHP, ColdFusion, and ASP
    Stay updated - http://blog.cartweaver.com

  • CSS Menu Maker Dreamweaver CS5

    Hi folks,
    Newb to Dreamweaver CS5 & CSS (yay!) I've read the online tutorials and quite frankly, I'm about ready to smash my head against my desk. This is very confusing. I haven't made any progress with my web site....unless staring at a white screen mocking me is progress.
    I got some good feedback from a few users in my first post (this is my 2nd post)  for which I'm very greatful btw and figured out that frames aren't the way to go. CSS confused the heck out of me, so I did some research and stumbled upon a website : http://www.cssmenumaker.com
    I was able to create & download a horizontal CSS menu that looks very appealing. Problem is, I can't seem to get it to work using Dreamweaver CS5. Perhaps somebody can help me. (God how I hope somebody can help me!) 
    For starters, I've created a "site" in Dreamweaver CS5. The site in Dreamweaver CS5 connects successfully to my hosting server. The directory structure on my hard drive that holds my files is :
    C:\HTML
    C:\HTML\images (where I keep any images used for my site)
    C:\HTML\menu (this was produced by the CSS menumaker website - has a CSS file in it & an "images" subdirectory within)
    Below are the instructions that were included when I unzipped the cssmenumaker's zip file :
    INSTALLATION INSTRUCTIONS
    1) Upload the "Menu" folder to the root directory of your  website.
    2) Copy and paste the code below to the desired spot in your site.
    <head>
         <link rel="stylesheet" href="/menu/menu_style.css"  type="text/css" />
    </head>
    <div class="menu bubplastic horizontal aqua">
         <ul>
             <li class="highlight"><span class="menu_r"><a  href="index.html" target="_self"><span  class="menu_ar">Home</span></a></span></li>
             <li><span class="menu_r"><a  href="products-services" target="_self"><span  class="menu_ar">Products/Services</span></a></span></li>
             <li><span class="menu_r"><a href="faq"  target="_self"><span  class="menu_ar">FAQs</span></a></span></li>
             <li><span class="menu_r"><a href="contactus"  target="_self"><span class="menu_ar">Contact  Us</span></a></span></li>
         </ul>
         <br class="clearit" />
    </div>
    NOTE:
    1) Open the "sample.html" to view a sample of your menu.DO NOT use this code in your site.
    2) If you run into a problem getting your menu to work or have  suggestions for the site please Contact Us and  let us know. We will try to help as much as possible.
    Can somebody walk me through this step by step? I thought it was fairly simple but obviously I'm doing something wrong.

    John,
    As I mentioned in my first post I've been through the tutorials already. I just can't seem to get this to work. Working off what I told you in my first post, assume you're working with a blank index.html and you enter in the CSS Menu Maker's code to the blank html file.
    The HTML code should look like this, should it not ?  :
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <!--
    Generated via www.cssmenubuilder.com, visit us to get a super cool menu for your site
    -->
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <title>Untitled</title>
    <link rel="stylesheet" href="/menu/menu_style.css" type="text/css" />
    </head>
    <div class="menu bubplastic horizontal aqua">
        <ul>
            <li class="highlight"><span class="menu_r"><a href="index.html" target="_self"><span class="menu_ar">Home</span></a></span></li>
            <li><span class="menu_r"><a href="products-services" target="_self"><span class="menu_ar">Products/Services</span></a></span></li>
            <li><span class="menu_r"><a href="faq" target="_self"><span class="menu_ar">FAQs</span></a></span></li>
            <li><span class="menu_r"><a href="contactus" target="_self"><span class="menu_ar">Contact Us</span></a></span></li>
        </ul>
        <br class="clearit" />
    </div>
    <body>
    </body>
    </html>

  • Dreamweaver CS5 and Spry

    I'm been looking into Spry, and I'm wondering if there's something that has basically replaced it.
    Some of the help in Spry goes back to 2008 or so, and some of the widgets are impossible to get(like autosuggest).
    There are also other pages that don't exist any more.
    It looks like a technology that has seen its day. So should I be looking in a different direction?
    Basically, I'm interested in Javascript/JQuery/Ajax user-interface-type coolness for front-end Web design.
    I just downloaded the Yahoo YUI library and am looking into that.
    This all started as I was using ColdFusion and wanted to use Ajax to return form results to the same page
    and use autosuggest or autocomplete(I don't know what the difference is) for a drop-down of names
    that a potential registrant could choose from.
    These simple, form-based ideas have led me on an adventure of discovery. For example, I saw some nice
    Adobe videos about YUI calendar and other things, from Jorge and somebody else, two very good-looking guys
    who do a great job of presenting Dreamweaver, but the videos were from 2008.
    So it's hard to escape the feeling that I'm missing something major here and that there is a current technology
    that I should be looking at instead of what's inside Dreamweaver.

    To add to your misery, there are two directions that Spry has evolved into, the original Spry based on version 1.6.1 (pre-release) and the so-called UI widgets which are based on version 1.7 (pre-release). The two versions are not compatible so you need to choose beforehand.
    Donals Booth and Kin Blas are the authors of Spry see here http://tv.adobe.com/watch/closeup-developer-interviews/donald-booth-and-kin-blas/
    Donald Booth did start on a jQuery dataset based on Spry see here https://github.com/jblas/jquery-dataset; but Donald nowadays seems to be pre-occupied with jQuery-mobile see here https://github.com/jblas.
    With no progress being made with Spry, I tend to use widgets that which is readily available now, such the menubar, accordionpanel validation etc, maily because they are easily implemented using Dreamweaver. I shy away from the UI widgets because I think that they only complicate things. Instead I try to use jQuery widgets where possible. Some of these are easily implemented using the Widget Browser, see here http://www.adobe.com/cfusion/exchange/index.cfm?s=5&from=1&o=desc&cat=335&l=-1&event=produ ctHome&exc=3
    I continue to use SpryDataSets. I have yet to come across a better solution.
    Having said the above, I think that when Adobe included Spry with Dreamweaver, they should have at least come with a final release instead of leaving us in limbo with their pre-release products. Spry is a winner! it will be a sorry day if there is no further support for this product as Adobe has done with ADDT the Adbobe Developer Toolbox, see here http://forums.adobe.com/community/dreamweaver/addt
    Gramps

  • Adobe recommends: Enhanced support for CSS3 in Dreamweaver CS5.5

    Over  the past week, we publicized some high-value content from adobe.com and other community sites. Hopefully you enjoyed these posts and found the resources useful. Today is our last day of the "Adobe Recommends" series.
    Continuing our trip along the CSS highway, we now move to CSS3 with our next recommendation, by Preran Kurnool:
    Enhanced support for CSS3 in Dreamweaver CS5.5
    This blog post takes you through using box shadow, text shadow, border radius, and border image properties in Dreamweaver CS5.5.
    Give it a spin and let us know what you think!
    Previous recommendation threads:
    Use Dreamweaver CS 5.5 to package your web application for iOS and Android devices
    Customizing a Spry Menu Bar widget
    Spry Menu Bar resources
    Layout 101
    CSS page layout basics
    New CSS features in Dreamweaver CS5
    Automatically attaching style sheets to new documents

    Aegis Kleais wrote:
    Sorry, Al, but I couldn't disagree more.  Where I respect the fact that, as coders, we're rather ingrained with our workflow processes and, at times, hesitant to change, I've found LESS' benefits to be very worthwhile.
    No need to apologize. Preprocessing is a topic on which there are differing opinions. You have one. I have one. There are advocates:
    http://blog.urbaninsight.com/2012/04/12/ten-reasons-you-should-be-using-css-preprocessor
    There are those who are not sold:
    http://blog.millermedeiros.com/the-problem-with-css-pre-processors/
    http://www.skybondsor.com/blog/css-preprocessors
    There are those mostly sold:
    http://css-tricks.com/musings-on-preprocessing/
    There are even those who have been converted (but who might reverse at some later point):
    http://cognition.happycog.com/article/preprocess-this
    Heck, even I might be converted someday - or not
    Bottom line for me, right now? I know I can write CSS that is better than most, more efficient than most, and easier to follow than most, and a preprocessor would add unwanted complexity. But that's for me. For someone not able to be organized intutively, or for a large - but carefully coordinated - team, a preprocessor could be a positive.
    But not for me.
    There are evolving trends - popular aspects of the technology that may and should find themselves being adapted into CSS. But I've been around this business as long as CSS has. I've seen buzzwords and trends and I've historically been spot-on in predicting the one that will stick. I think preprocessing will stick - but only insofar as it will be a catalyst for features in future versions of CSS. As a separate technology it makes no sense - to me

  • Adobe recommends: New CSS features in Dreamweaver CS5

    Over  the next week, we are going to be publicizing some high-value content from adobe.com and other community sites. We have been tracking what's    been most important to our users, and feel that getting this content out to the larger community will go a long way toward helping people tackle some of their most pressing challenges.
    Continuing our trip along the CSS highway, our next recommendation is a video by Dremeaver superstar Brian Wood:
    New CSS features in Dreamweaver CS5
    The video demonstrates some of the most exciting new CSS features in Dreamweaver: new CSS layouts, CSS inspect, and CSS enable/disable.
    Give it a spin and let us know what you think!
    Previous recommendation threads:
    Use Dreamweaver CS 5.5 to package your web application for iOS and Android devices
    Customizing a Spry Menu Bar widget
    Spry Menu Bar resources
    Layout 101
    CSS page layout basics

    Thanks for the answer this is very useful however I still find that Dreamwever defaults back to writing in CSS, I have to go to the manel every time and switch from CSS style to Inline style which is very irritating. Is there any way to disable writing in CSS all together like their used to be in CS3..in the preferences.
    Much appreciated

  • How do I make the menu title a different color when it is the active menu in Spry horizontal menu?

    How do I make the menu title a different color when it is the active menu in Spry horizontal menu?
    Dreamweaver CS5.5
    Apple OS X.6.8
    View site at: http://dorsay-easton-indian-law.com/staging/index.html
    Steps:
    1. Click link to land on Home page
    2. View Home link in Spry horizontal navigation menu
    Actual:
    Home menu title is the same color as all of the others.
    Expected:
    The title of the active menu is       color: #FFC.
    I was hoping that a:active would give me this functionality, but that's not how it is described. Any suggestions are welcome!

    Nothing I have tried in the template makes the BODY tag editable. That's why I'm wondering how to disconnect the template from the individual pages. Adding an ID to each body tag is a prerequisite of the how-to page you supplied.
    You don't make the <body> tag editable in a Template.
    You make attributes of the <body> tag editable.
    Don't disconnect the Template from the child pages.
    Specify editable tag attributes in a template
    http://help.adobe.com/en_US/dreamweaver/cs/using/WScbb6b82af5544594822510a94ae8d65-7aa3a.h tml
    In the Template:
    Select the <body> tag (either in the Tag selector or click inside the <body> tag in Code View)
    Modify > Templates > Make Attribute Editable
    Select ID from the Attribute dropdown menu
    If there's no existing ID attribute then click Add and type ID into the next dialogue box
    Attribute: ID
    Check the box to "Make attribute editable"
    Enter anything into the Label field as a default e.g. foo
    OK
    Dreamweaver will change the <body> tag to read <body id="@@(foo)@@"....
    Now the ID is editable
    Save the Template and update the child page
    In each child page:
    Modify > Template Properties
    Select the id attribute from the list (it's probably the only one listed)
    Change its name in the box to whatever name matches your CSS rule for the active state for that page
    OK
    Save
    Upload

  • Dreamweaver CS5.5 Bugs

    We've encountered some bugs in what is otherwise a great application and a great job by Adobe. We would, like to start a public discussion to see if anyone else has been able to reproduce any of the issues. Recently, we put a new production machine to work in the office and since it is a clean machine, with a fresh install of only Dreamweaver CS5.5, the issues would seem to be reproducible - rather than restricted to a specific machine or configuration. So here is the first test page:
    http://www.projectseven.com/testing/cs5.5-bugs/
    There are other bugs we'd like to test, but let's focus on a few for now.
    Happy Hunting :-)

    My specs before I go into answers:
    Apple Macbook Pro
    Mac OSX 10.6.8
    2.8 Ghz Core 2 Duo
    4GB Ram
    GeForce 9600M GT/9400M
    Touchpad + Logitech V400 wireless mouse
    1.  Didn't have time to test this one yet but I will later.
    2.  I haven't noticed anything too bad since I switched my web host and am now using FTPS (FTP over SSL Explicit).  But on regular FTP I used to see that all the time.  Although the whole FTP part of DW should be rebuilt it is behind even free solutions available in both features and speed and there is no need for it.
    3.  The "li" bug - Reproducible.  My only question here is if the user stays in Design View what would generate a new bullet?  Tab?
    Loss of Text Cursor - I'm unable to reproduce this one.  Only time I lose the cursor is on darker backgrounds where it blends in more. 
    To your comments on Design View in general I agree 100%.  They made Live View to show how the page will render and the example I like to point to is their own Spry code.  The 1.0 code would render in Design View whereas the new 2.0 (Spry UI) code will only render in Live View and show up as a list in Design View.  With the way DW and the web are going, Design View might as well be deprecated.  And I do agree that the Live View builds could be updated.  Small updates on a regular basis with the webkit updates would be nice here.
    I'm just keeping my fingers crossed about Lion.  No word on Adobe's website and unofficial ones have found nothing wrong with DW so far, although not all Adobe CS programs have been so lucky.

Maybe you are looking for