SPRY 1.5 pre-release compatibility with CS3

Hi all
Does anyone know if SPRY pre-release v 1.5 will be
backward-compatible with the release version that is integrated
into Dreamweaver CS3? I'm about to start a project that uses AJAX
tabs and need to know if the current methods will be editable with
future versions of Dreamweaver.
Thanks
Paul

Understanding that I work for Adobe and I worked on Spry
features for DW CS3..
There isn't anything special about working in DW8 with Spry.
Your widget will render as exploded markup: easy to see content but
harder to determine layout. But as HTML and CSS, editing should be
straightforward.
But I am spoiled by having widget rendering and Spry code
coloring and hinting in DWCS3 for many months now.
Widgets render as they do in the browser and you can
add/remove tabs and switch between them.
Spry code hinting, esp with the data stuff, is quite fun.
But, for now, DW8 will do just fine for you.
Thanks,
Don

Similar Messages

  • Sp9 / pre-release / problem with jsp tags

              WLS 5.1, sp9 pre-release, solaris 2.7, WLCS 3.2
              JSP compile fails with the exception...
              weblogic.servlet.jsp.JspException: (line -1): Error in tag library
              at: 'wl':
              The Tag class 'weblogicx.jsp.tags.CacheTag' has no setter method
              corresponding to
              TLD declared attribute 'async', (JSP 1.1 spec, 5.4.1)
              at weblogic.servlet.jsp.StandardTagLib.jspException(StandardTagLib.java:138)
              at weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java:264)
              at weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java:146)
              at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
              at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:95)
              at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:3873)
              at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:3623)
              at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:3484)
              at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1817)
              at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1658)
              at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1548)
              at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:888)
              at weblogic.servlet.jsp.JspParser.doit(JspParser.java:69)
              at weblogic.servlet.jsp.JspParser.parse(JspParser.java:125)
              at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:109)
              at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:242
              

              It could just be me - I an un-jarred a version of weblogic-tags-510.jar where WLS
              could find it.
              mike
              Kumar Allamraju <[email protected]> wrote:
              >Yes, my JSP is referring the tag libs. I 'm using counter example given
              >in
              >examples/jsp/tagext/counter directory
              >
              ><NT Performance Pack> NATIVE: created IoCompletionPort successfully.
              >I
              >oPort=0x000001d4
              >Sun Apr 01 12:44:00 PDT 2001:<I> <WebLogicServer> WebLogic Server star
              >ted
              >Sun Apr 01 12:44:40 PDT 2001:<I> <NT Performance Pack> Allocating: '2'
              > NT reader threads
              >Sun Apr 01 12:44:41 PDT 2001:<I> <ServletContext-General> *.jsp: init
              >Sun Apr 01 12:44:41 PDT 2001:<I> <ServletContext-General> *.jsp: param
              > verbose initialized to: true
              >Sun Apr 01 12:44:41 PDT 2001:<I> <ServletContext-General> *.jsp: param
              > packagePrefix initialized to: jsp_servlet
              >Sun Apr 01 12:44:41 PDT 2001:<I> <ServletContext-General> *.jsp: param
              > compileCommand initialized to: c:/java/java122/bin/javac.exe
              >Sun Apr 01 12:44:41 PDT 2001:<I> <ServletContext-General> *.jsp: param
              > srcCompiler initialized to weblogic.jspc
              >Sun Apr 01 12:44:41 PDT 2001:<I> <ServletContext-General> *.jsp: param
              > superclass initialized to null
              >Sun Apr 01 12:44:41 PDT 2001:<I> <ServletContext-General> *.jsp: param
              > workingDir initialized to: D:\releases\510\myserver\classfiles
              >Sun Apr 01 12:44:41 PDT 2001:<I> <ServletContext-General> *.jsp: param
              > pageCheckSeconds initialized to: 1
              >Sun Apr 01 12:44:41 PDT 2001:<I> <ServletContext-General> *.jsp: Using
              > Encoding : ISO-8859-1 when constructing PrintWriter instead of Servle
              >tOutputStream
              >Sun Apr 01 12:44:41 PDT 2001:<I> <ServletContext-General> *.jsp: initi
              >alization complete
              >Sun Apr 01 12:44:42 PDT 2001:<I> <ServletContext-General> looking for
              >taglib uri /counter.tld as resource /WEB-INF/counter.tld in Web Applic
              >ation root:
              >Sun Apr 01 12:44:43 PDT 2001:<I> <ServletContext-General> Generated ja
              >va file: D:\releases\510\myserver\classfiles\jsp_servlet\_pagehits.jav
              >a
              >Sun Apr 01 12:44:45 PDT 2001:<I> <ServletContext-General> file: init
              >
              >
              >what's the change number you get from weblogic.Admin VERSION?
              >
              >
              >--
              >Kumar
              >
              >Mike Reiche wrote:
              >
              >> From the zip file.
              >>
              >> It has to be a jsp that references those tag libraries.
              >> Other than that it works like a charm.
              >>
              >> Mike
              >>
              >> Kumar Allamraju <[email protected]> wrote:
              >> >Did you extracted the SP9 zip or exe?
              >> >I do not see the following errors when accessing a jsp with SP9? Could
              >> >you tell us how to
              >> >reproduce it?
              >> >
              >> >BTW, i will ask our docs folks to correct the startup scripts..
              >> >
              >> >--
              >> >Kumar
              >> >
              >> >Mike Reiche wrote:
              >> >
              >> >> I had to remove the 'async' attribute from taglib.tld
              >> >>
              >> >> And when I use WLCS I have to remove it from weblogic.tld
              >> >>
              >> >> And the startup scripts provided do not include weblogic-tags-510.jar
              >> >> in the classpath.
              >> >>
              >> >> Mike
              >> >>
              >> >> "Mike Reiche" <[email protected]> wrote:
              >> >> >
              >> >> >WLS 5.1, sp9 pre-release, solaris 2.7, WLCS 3.2
              >> >> >
              >> >> >JSP compile fails with the exception...
              >> >> >
              >> >> >weblogic.servlet.jsp.JspException: (line -1): Error in
              >> >> >tag library
              >> >> >at: 'wl':
              >> >> >The Tag class 'weblogicx.jsp.tags.CacheTag' has no setter
              >> >> >method
              >> >> > corresponding to
              >> >> >TLD declared attribute 'async', (JSP 1.1 spec, 5.4.1)
              >> >> > at weblogic.servlet.jsp.StandardTagLib.jspException(StandardTagLib.java:138)
              >> >> > at weblogic.servlet.jsp.StandardTagLib.processTag(StandardTagLib.java:264)
              >> >> > at weblogic.servlet.jsp.StandardTagLib.processTagElements(StandardTagLib.java:146)
              >> >> > at weblogic.servlet.jsp.StandardTagLib.<init>(StandardTagLib.java:125)
              >> >> > at weblogic.servlet.jsp.JspLexer.loadTagLib(JspLexer.java:95)
              >> >> > at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE_BODY(JspLexer.java:3873)
              >> >> > at weblogic.servlet.jsp.JspLexer.mTAGLIB_DIRECTIVE(JspLexer.java:3623)
              >> >> > at weblogic.servlet.jsp.JspLexer.mDIRECTIVE(JspLexer.java:3484)
              >> >> > at weblogic.servlet.jsp.JspLexer.mSTANDARD_THING(JspLexer.java:1817)
              >> >> > at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java:1658)
              >> >> > at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java:1548)
              >> >> > at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:888)
              >> >> > at weblogic.servlet.jsp.JspParser.doit(JspParser.java:69)
              >> >> > at weblogic.servlet.jsp.JspParser.parse(JspParser.java:125)
              >> >> > at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:109)
              >> >> > at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:242
              >> >
              >
              

  • Current Release Compatibility with Lenovo IdeaPad U300

    Has anyone had the opportunity to use the current release (2011.08.19 at time of writing) on a Lenovo IdeaPad U300? I am thinking about picking one up but want to confirm hardware compatibility before I did so. I looked in the HCL in the Wiki, but didn't see this particular model listed.
    Thank you in advance for your help.

    Understanding that I work for Adobe and I worked on Spry
    features for DW CS3..
    There isn't anything special about working in DW8 with Spry.
    Your widget will render as exploded markup: easy to see content but
    harder to determine layout. But as HTML and CSS, editing should be
    straightforward.
    But I am spoiled by having widget rendering and Spry code
    coloring and hinting in DWCS3 for many months now.
    Widgets render as they do in the browser and you can
    add/remove tabs and switch between them.
    Spry code hinting, esp with the data stuff, is quite fun.
    But, for now, DW8 will do just fine for you.
    Thanks,
    Don

  • PSE 4.0 Compatibility with CS3?

    Simple question from a newbie. . .
    Are .psd files from CS3 downward comaptible with PSE 4.0?

    You might want to insure that the PSD files saved in CS3 are saved with "Maximize PSD file Compatibility" turned on in the preferences. I'd think you'd want that particular preference turned on to be on the safe side. Hopefully, Barbara or someone who knows for sure will have something to say about whether that particular preference needs to be on.

  • Future WLI Product release, compatibility with BPM

    Regarding Integration and BPM products from BEA I have the following queries:
    1) What is the next major release for Weblogic Integration product and what Enhancements will be there?
    2) Which BEA product is going to have Business Process Management (BPM) functionality supporting BPEL Server and BPEL designers?
    3) How BEA differentiates the BEA AquaLogic from BEA Weblogic Integration?
    regards,
    neeraj
    ?:|

    Miklos:
    There's really not much you can do after the site has been published to reduce the png's. But before, there are some changes you can make that will help considerably.
    1 - do not use any borders, etc. around photos.
    2 - don't use any reflections.
    3 - create your own navigation bar with linked text and turn of the iWeb Navigation bar. The nav bar is all png based.
    4 - use only the web safe fonts from the Font pane.
    5 - turn off smart quotes
    6 - do not use drop shadow on fonts.
    The above will reduce the number of png files associated with a web page considerably. You can run a test with a test site and publish to a folder. Then follow the hints above and publish to another folder and compare folders.
    One way to handle multiple sites is to use iWebSites. It lets me create multiple sites and multiple domain files. If you have multiple sites in one domain file here's the workflow is used to split them into individual site files with iWebSites.
    For me it makes updates several sites and publishing only one very easy.
    Do you Twango?

  • How to delete folio from pre-release?

    Hello, on some accounts we still have folios from pre-release, created with Content Bundler. How we can delete this folios?

    Hi Martin,
    I faced the same situation at one point and if I recall correctly, we uploaded the folio to the Folio Producer and then we built a new version of the app (with the latest Viewer Builder) and that new app pointed to the folio on Folio Producer.
    Oh and as far as I know, the old folios are still there, but the new app points to Folio Producer folio (and not the pre release).
    Hope that helps,
    dw

  • Spry Menu Bar css not compatible with IE7? or compatibility View on IE8?

    Well i've made my website
    . Swimmerbuddy.com
    Problem:I used the spry menu bar on a div tag. I've got it working fine on several browser and so on.. but hmm. i noticed that IE7 and only on compatibility view of IE8 it does not work...
    It seems like the drop down menus get cover by the main content underneath it..
    I started of with dwt i made my self.This is the DWT and the css that controll the dwt and the spry menu bar.
    PLZ HELP ME.. THANKS
    THIS IS THE DWT THAT THE PAGE RUNS ON
    <!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" />
    <!-- TemplateBeginEditable name="doctitle" -->
    <title>Untitled Document</title>
    <!-- TemplateEndEditable -->
    <link href="../CSS/main.css" rel="stylesheet" type="text/css" />
    <!-- TemplateBeginEditable name="head" -->
    <!-- TemplateEndEditable -->
    <style type="text/css">
    a:link {
    color: #000;
    text-decoration: none;
    </style>
    <script src="../SpryAssets/SpryMenuBar.js" type="text/javascript"></script>
    <link href="../SpryAssets/SpryMenuBarHorizontal.css" rel="stylesheet" type="text/css" />
    <style type="text/css">
    a:visited {
    color: #000;
    text-decoration: none;
    a:hover {
    text-decoration: none;
    color: #000;
    a:active {
    text-decoration: none;
    </style>
    </head>
    <body>
    <div id="wrapper">
      <div id="header">
        <div id="networkicons"><a href="http://www.facebook.com/?ref=logo#!/profile.php?id=100001554936595" target="_blank"><img src="../_images/facebook.png" alt="facebook.com" width="45" height="45" border="0" title="facebook.com"/></a><a href="http://www.myspace.com/swimmerbuddy" TARGET="_blank"> <img src="../_images/myspace.png" alt="myspace.com" width="44" height="45" border="0" title="myspace.com"/></a><a href="http://twitter.com/swimmerbuddy" TARGET="_blank"> <img src="../_images/twitter.png" alt="twitter.com" width="43" height="45" border="0" title="twitter.com"/></a><a href="http://www.youtube.com/swimmerbuddy1" TARGET="_blank"> <img src="../_images/youtube.png" alt="youtube.com" width="44" height="45" border="0" title="youtube.com"/></a></div>
        <div id="buyNow1">
          <p><a href="../order_now.html"><img src="../buynowbutton.png" alt="bt1" width="130" height="25" border="0" longdesc="Order Your Swimmer Buddy Today!!" /></a></p>
        </div>
      </div>
      <div id="mainNav">
        <ul id="mainNavcontent" class="MenuBarHorizontal">
          <li><a href="../index.htm">Home</a>        </li>
          <li><a href="../swimmer.html">Swimmer Buddy</a></li>
          <li><a href="../order_now.html">Order Now</a>        </li>
          <li><a href="#" class="MenuBarItemSubmenu">Gallery</a>
            <ul>
              <li><a href="../photo_gallery.html">Photos</a></li>
              <li><a href="../video_gallery.html">Videos</a></li>
            </ul>
          </li>
          <li><a href="#" class="MenuBarItemSubmenu">Zinger Products</a>
            <ul>
              <li><a href="http://www.winkyscoop.com/">Winky Scoop</a></li>
              <li><a href="http://www.1800succeed.com/">Hypmovation</a></li>
              <li><a href="http://www.1800succeed.org/">1800SUCCEED</a></li>
              <li><a href="http://www.zingerproducts.com">Zinger Store</a></li>
            </ul>
          </li>
          <li><a href="../about.html">About Us</a></li>
          <li><a href="../contact.html">Contact Us</a></li>
        </ul>
      </div>
      <!-- TemplateBeginEditable name="mainContent" -->
      <div id="pageInfo">
        <div id="info_page">
          <p class="regionID">Region ID</p>
          <hr class="breaklinePageInfo" />
          <p class="breadcrum">&gt; <a href="../index.htm">Breadcrum </a></p>
        </div>
        <div id="mainContent">
          <div id="content">
            <p>Main Content Goes her</p>
          </div>
        </div>
      </div>
      <!-- TemplateEndEditable -->
      <!-- TemplateBeginEditable name="buynow2" -->
       <div id="buyNow2"><a href="../order_now.html"><img src="../buynowbutton.png" width="130" height="25" /></a></div>
       <!-- TemplateEndEditable -->
      <div id="footer">
    <div id="footertext">
            <p class="footertextclass">Copyright © 2010 SwimmerBuddy.com. All rights reserved. SwimmerBuddy.com is part of <a href="http://www.zingerproducts.com" class="footertextclass">Zinger Products</a>. Designated Trademarks and brands are the property of their respective owners. This page was last modified Setember 28,2010. Swimmer Buddy - Pattent Pending 2010</p>
          </div>
        <div id="footerlinks">
            <p classs="footerlinkspacing"> <span class="footerlinkspacing"><a href="../Disclaimer.html">Disclaimer</a><a href="../terms.html"> Term of Service </a><a href="../contact.html">Contact Us</a></span>
    </div>
          </div>
    </div>
    <script type="text/javascript">
    var MenuBar1 = new Spry.Widget.MenuBar("mainNavcontent", {imgDown:"../SpryAssets/SpryMenuBarDownHover.gif", imgRight:"../SpryAssets/SpryMenuBarRightHover.gif"});
    </script>
    </body>
    </html>
    THIS IS THE MAIN.CSS
    @charset "utf-8";
    #networkicons {
    height: 50px;
    width: 200px;
    margin-top: 160px;
    margin-left: 15px;
    position: absolute;
    #wrapper {
    width: 933px;
    margin-top: 0px;
    margin-right: auto;
    margin-bottom: 0px;
    margin-left: auto;
    text-align: left;
    position: relative;
    #mainNav {
    text-align: center;
    position: relative;
    margin-right: auto;
    margin-left: auto;
    width: 934px;
    padding-bottom: 15px;
    clear: both;
    overflow: visible;
    #navwrapper {
    width: 935px;
    margin-right: auto;
    margin-left: auto;
    #mainContent {
    width: 910px;
    padding-left: 10px;
    padding-right: 10px;
    position: relative;
    padding-bottom: 20px;
    padding-top: 20px;
    #content {
    width: 910px;
    position: relative;
    #wrapper #footer #footerlinks p .footerlinkspacing a {
    margin-right: 20px;
    #footer {
    width: 930px;
    background-color: #fff;
    position: relative;
    margin-top: 5px;
    text-align: center;
    color: #000;
    padding-bottom: 10px;
    margin-bottom: 15px;
    #header {
    width: 930px;
    height: 209px;
    background-image: url(../_images/header.jpg);
    background-repeat: no-repeat;
    #buyNow1 {
    height: 25px;
    width: 140px;
    float: right;
    font-family: Arial, Helvetica, sans-serif;
    font-weight: bold;
    text-align: center;
    background-repeat: no-repeat;
    color: #666;
    padding: 5px;
    position: absolute;
    top: 160px;
    right: 150px;
    .buyNow1 {
    color: #666;
    #wrapper #pageInfo #info_page .breadcrum {
    color: #003;
    #wrapper #pageInfo #info_page .breadcrum a {
    color: #003;
    html, body {
    margin: 0px;
    padding: 0px;
    #buyNow2 {
    height: 25px;
    width: 130px;
    float: right;
    font-family: Arial, Helvetica, sans-serif;
    font-weight: bold;
    text-align: center;
    padding: 5px;
    position: relative;
    #wrapper #buyNow2 a img {
    position: absolute;
    top: -30px;
    right: 50px;
    border-top-width: 0px;
    border-right-width: 0px;
    border-bottom-width: 0px;
    border-left-width: 0px;
    border-top-style: none;
    border-right-style: none;
    border-bottom-style: none;
    border-left-style: none;
    #pageInfo {
    width: 930px;
    background-image: url(../_images/pageinfobackground.jpg);
    background-repeat: repeat-x;
    background-color:#FFF;
    text-align: left;
    padding-bottom: 15px;
    margin-top: 18px;
    position: relative;
    overflow: visible;
    visibility: visible;
    #wrapper #mainNav #mainNavcontent {
    position: absolute;
    left: 0px;
    width: 930px;
    .regionID {
    font-size: 2em;
    font-weight: bold;
    color: #FFC;
    margin-top: 1em;
    margin-bottom: 0em;
    text-align: left;
    margin-left: 5px;
    .breaklinePageInfo {
    margin-top: 0.5em;
    color: #FAFEAB;
    .breadcrum {
    color: #003;
    font-size: 1.1em;
    font-weight: bold;
    text-decoration: underline;
    margin-top: -0.2em;
    margin-left: 15px;
    #breadcrum {
    font-weight: bold;
    color: #003;
    #footertext {
    width: 910px;
    font-size: 0.6em;
    padding-left: 10px;
    padding-right: 10px;
    margin-top: 10px;
    #footerlinks {
    width: 930px;
    font-size: 0.7em;
    font-weight: bold;
    font-family: "Lucida Sans Unicode", "Lucida Grande", sans-serif;
    color: #000;
    position: relative;
    margin-top: 10px;
    margin-bottom: 5px;
    .footertextclass {
    color: #000;
    .footerlinkspacing {
    margin-top: -0.5em;
    color: black;
    height: 10px;
    font-style: normal;
    line-height: normal;
    font-variant: normal;
    letter-spacing: normal;
    p {
    margin: 0px;
    padding: 0px;
    body {
    text-align: center;
    margin-top: 5px;
    background-color: #073e78;
    background-image: url(../_images/background.jpg);
    background-repeat: repeat-x;
    background-attachment: scroll;
    font-size: 100%;
    THIS IS THE dropdown menu.css
    @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: 100%;
    cursor: default;
    width: auto;
    /* 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
    z-index: 1000;
    /* Menu item containers, position children relative to this container and are a fixed width */
    ul.MenuBarHorizontal li
    margin: 0px;
    padding: 0;
    list-style-type: none;
    font-size: 100%;
    position: static;
    text-align: center;
    cursor: pointer;
    width: 132.8px;
    float: left;
    overflow: visible;
    visibility: visible;
    /* 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
    margin: 0;
    padding: 0;
    list-style-type: none;
    font-size: 100%;
    z-index: 1020;
    cursor: default;
    width: 132.8px;
    position: absolute;
    left: -1000em;
    /* 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
    left: auto;
    /* Menu item containers are same fixed width as parent */
    ul.MenuBarHorizontal ul li
    width: 8.2em;
    /* Submenus should appear slightly overlapping to the right (95%) and up (-5%) */
    ul.MenuBarHorizontal ul ul
    position: absolute;
    margin: -5% 0 0 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: auto;
    top: 0;
    DESIGN INFORMATION: describes color scheme, borders, fonts
    /* Submenu containers have borders on all sides */
    ul.MenuBarHorizontal ul
    border: #333;
    color: #FFF;
    /* Menu items are a light gray block with padding and no text decoration */
    ul.MenuBarHorizontal a
    display: block;
    cursor: pointer;
    background-color: #FFF;
    padding: 0.5em 0.75em;
    color: #333;
    text-decoration: none;
    background-image: url(../_images/bar-top.png);
    background-repeat: no-repeat;
    /* Menu items that have mouse over or focus have a blue background and white text */
    ul.MenuBarHorizontal a:hover, ul.MenuBarHorizontal a:focus
    color: #003;
    background-image: url(../_images/bar-Bottom.png);
    /* 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
    color: #003;
    background-image: url(../_images/bar-Bottom.png);
    background-position: bottom;
    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(../_images/bar-topsub.png);
    background-repeat: no-repeat;
    background-position: right top;
    /* 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: 95% 50%;
    /* 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(../_images/bar-topsubhover.png);
    background-repeat: no-repeat;
    background-position: right bottom;
    /* 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(SpryMenuBarDownHover.gif);
    background-repeat: no-repeat;
    background-position: 95% 50%;
    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.MenuBarHorizontal iframe
    position: absolute;
    z-index: 1010;
    filter:alpha(opacity:0.1);
    /* 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.MenuBarHorizontal li.MenuBarItemIE
      display: inline;
      f\loat: left;
      background: #FFF;

    Thanks a lot for that tip. It does improve it by a whole lot.. i c what my mistake was.. however, something is still off
    .. The Drop down menu is not behaving well...
    As you may c by the picture, the drop down menu now moves to the right. and is not because of the object to its left, i've modified that. Zinger Products Drop Down Menu also does the same.

  • Firefox is trying to update my 8.0 version to 9.0.1. I'm not ready to do so because the Norton Toolbar is not yet compatable with the new Firefox release. How do I get firefox to stop trying to update every time I open the application?

    Question
    Firefox is trying to update my 8.0 version to 9.0.1. I'm not ready to do so because the Norton Toolbar is not yet compatable with the new Firefox release. How do I get firefox to stop trying to update every time I open the application?

    Swarnava wrote: '''''Firefox 9 is Compatible with Norton 2011, 2012, 360 v5'''''.
    This reads backwards, It is the other way as "Norton update is compatible with Firefox 9".

  • Flex obselete with the release of Flash CS3?

    Flash cs3 and its new components feature pretty much give the
    same functionality as flex's components.
    The only reason why i used flex was because of the
    components, ive only created a few applications but i cant see why
    i couldnt just make them with CS3 now?

    You could certainly make that attempt. Our goal is to give
    you as much choice as possible. Some people like the Flash IDE,
    others like Flex because you can use any text editor, not just Flex
    Builder. With Flash CS3, you need the Flash IDE to work with the
    FLA files.
    When you choose to work with Flex you can put your source
    files into a source code control system - you can do that with
    FLAs, but you lose change management. In other words, every time
    you edit your FLA, it changes so it is always going back into
    source code repository. With Flex and MXML and AS files, you save
    only those files which have changed.
    Flex provides a more traditional way to build SWFs. You can
    use Flash to supplement it. You'll find with Flex 3 that the
    reverse will be true, too - use Flex to supplement Flash.
    Anyway you want to do it, that makes you comfortable and
    successful, is the best way to go. We're glad to be able to offer
    you choices.

  • Problems with CS3 and Leopard

    Having a bit of a nightmare with Indesign and Photoshop CS3 since upgrading to Leopard. Running a Dual 2.5 GHz PowerPC G5 With 2GB DDR SDRAM. Anyone else having problems?

    Below is the Adobe Marketing Line (copied verbatim). It's what I was told by Adobe Sales and what I read at Adobe.com, FAQ, before buying CS3 in October 07. Imagine my surprise when I discovered all of the issues with CS3 and Leopard, even after the update to Acrobat 8.1.2 Professional which promised full compatibility (see chart at bottom).
    Apple and Adobe... ARGH.
    Oh yes, for all of the new suckers out there who are about to buy CS3 for their new Macs, the exact same FAQ is at Adobe.com, even now, Thursday, 12 Jun 2008.
    ADOBE CREATIVE SUTIE 3 Frequently Asked Questions
    Support for Mac OS X Leopard
    Q. Is Mac OS X Leopard (v10.5) important to Creative Suite 3 customers?
    A. Yes, Mac OS X Leopardthe latest version of Apples operating systemdelivers an elegant,
    productive new computing experience for creative professionals. Adobe and Apple have been
    collaborating closely for months to ensure that Adobe Creative Suite® 3 applications can run
    smoothly and reliably on Mac OS X Leopard. We are proud to support this impressive new
    operating system, and to ensure that our creative customers can take full advantage of the
    performance and value of using Creative Suite 3 applications and Mac OS X Leopard on
    Intel-based and PowerPC Macs.
    Q. Are Adobe Creative Suite 3 applications compatible with Mac OS X Leopard (v10.5)? If
    some are not fully compatible today, when will they be compatible?
    A. Thanks to close collaboration between Adobe and Apple, most of the CS3 applications and associated technologies, such as Adobe Bridge CS3, Version Cue CS3, and Device Central CS3, are compatible with Mac OS X Leopard without requiring additional updates. However, the following CS3 applications will require updates for full compatibility with Leopard: Adobe Acrobat 8 Professional and our professional video applications, including Adobe Premiere Pro CS3, After Effects CS3 Professional, Encore CS3, and Soundbooth CS3. We expect to publish free Leopard compatibility updates for the video applications in December 2007 and for Acrobat 8 Professional and Adobe Reader 8 in January 2008. For a complete overview of compatibility between Adobe creative applications and Mac OS X Leopard, see the chart on page 2 of this FAQ.
    Q. Will older versions of Adobe creative softwaresuch as Creative Suite 2 and
    Macromedia Studio 8 softwaresupport Mac OS X Leopard?
    A. While older Adobe applications may install and run on Mac OS X Leopard, they were
    designed, tested, and released to the public several years before this new operating system became available. You may, therefore, experience a variety of installation, stability, and reliability issues for which there is no resolution. Older versions of our creative software will not be updated to support Mac OS X Leopard. For a complete overview of compatibility between Adobe creative applications and Mac OS X Leopard, see the chart on page 2.
    Q. Will Adobe continue to test CS3 applications on Mac OS X Leopard?
    A. Yes. Adobe sets high standards of quality, stability, and reliability for our professional creative
    products, and we have worked closely with Apple to test Creative Suite 3 applications on both pre-release versions and the final shipping version of Mac OS X Leopard. While this testing showed that most CS3 applications perform well on Leopard (and that others run well but need updates for a few identified issues), we recognize that other issues may unexpectedly arise on any new operating system. We plan to continue testing and to monitor user experience closely to address any such issues. If you encounter any issues, please report them by going to www.adobe.com/misc/bugreport.html and clicking Report
    A Bug. Please note that we dont respond to submissions, but we do review them closely with the appropriate CS3 product teams.
    Q. Which CS3 applications will need patches to be compatible with Mac OS X Leopard?
    A. The following table summarizes compatibility between Adobe creative applications and Mac OS X Leopard. It notes which CS3 applications require updates for full Leopard compatibility and when Adobe expects to release those free updates.
    At A Glance: Mac OS X Leopard Compatibility
    ADOBE APPLICATION COMPATIBLE WITH REQUIRES UPDATE NOTES ABOUT
    Mac OS X Leopard For Mac OS X Leopard Compatibility
    Creative Suite 3 Design Premium ✔ Requires update to Acrobat 8.1.2
    Professional for full compatibility.
    Expected to be available
    in late January 2008.
    Creative Suite 3 Design Standard ✔ Requires update to Acrobat 8.1.2
    Professional for full compatibility.
    Expected to be available
    in late January 2008.
    Creative Suite 3 Web Premium ✔ Requires update to Acrobat 8.1.2
    Professional for full compatibility.
    Expected to be available
    in late January 2008.

  • Spry 1.6.1 released

    Hi All,
    As some of you early risers have noticed, we have formally
    released Spry 1.6.1, a dot release for Spry.
    This was mostly done to ensure compatibility with Adobe AIR,
    which was released today
    http://www.adobe.com/products/air/
    In order for Spry to work in AIR, we had to make some
    addition ways of working available to users. You can read about it
    here:
    http://labs.adobe.com/technologies/spry/articles/air/photo_gallery.html
    These changes introduce some cool new ways of coding your
    pages. Check out this new sample:
    http://labs.adobe.com/technologies/spry/samples/data_region/Function_colon.html
    Lots of good bug fixes, the new Rating widget is formally
    released, the Spry Updater for DW was updated.
    Download it and check it out.
    Thanks,
    The Adobe Spry Team

    Donald,
    Have you validated the javascript code to make sure that the
    behavior is the same on both IE7 and Firefox. The Accordion widget
    does not properly open large sets on IE7. See
    http://www.qualite1.com/ContactUs.html
    and select California to see the difference between Firefox and IE.
    Notice how the Javascript causes the focus to jump around on
    IE.

  • Before I update, is firefox 27.0.1 compatable with Skype click and call?

    Every time I update Firefox I lose Skype click and call and have to wait weeks for access to it again. I now will not update Firefox until I know it is comparable with Skype click and call.
    Is firefox 27.0.1 compatable with Skype click and call at this time?

    I presume ''"Skype click and call"'' is official [http://portableapps.com/apps/internet/firefox-portable-esr Skype] software.
    If you need skype and this happens on every update an unoficial solution would be to install Firefox portable ESR as an additional browser and then use that for skype whilst using the fully updated Firefox Release for all other browsing. (Firefox Portable is based on Mozilla Firefox, the ESR version probably will remain compatible with skype and not have problems on updates )
    * http://portableapps.com/apps/internet/firefox-portable-esr
    The official solution would be to use Firefox Releases and update Skype. Complaining to Skype as necessary when it is not compatible with the Firefox Releases. Skype will be aware of the Release dates and will be able to test and modify their software as necessary whilst using public pre release versions of Firefox. <br />Presumably Skype is controlled by MS and they would prefer you to always use IE and not use Firefox at all.

  • I get a message that says "This version of pre-release ios will expire in 7 days" What should I do? I am currently running ios 8 GM and I can't update to the public release version.

    I get a message that says "This version of pre-release ios will expire in 7 days" What should I do? I am currently running ios 8 GM and I can't update to the public release version. I am stuck in the beta. Itunes will not let me restore my iphone or update it. PLZ HELP ME

    Wondering if you have a current Backup on iTunes ...if yes you could put the iPhone in DFU Mode by holding the Home button while you plug in the lightning cable.  Then you could Restore the iPhone to Factory Settings on 8.0.2 and after a full Restore go back and then Restore from your Backup.  This happens every time a public release occurs.  Many folks on the Golden Master or otherwise in the AppleSeed program with a Beta version for some reason don't move to the official release ...then the software time-bomb hits and they can't upgrade.

  • Blue Ray Disk drive compatibility with DVD S Pro, Mac Pro

    Ok, I'll make this an official question, where might I find info on BDR drive compatibility with DVD S Pro, Mac Pro, etc? I'm a little surprised that there doesn't seem to be much info available.
    I can always use my Pioneer BDR-202 with a windows box, I have several, but I'm trying to get AWAY from them.
    Any thoughts, links, etc. welcome, thanks
    Les

    Blu-ray offers a level of interacivity that is not possible with DVDs, so it isn't just an different drive that you are getting with Blu-ray. Seeing how Apple didn't upgrade DVD SP with the new FCP Suite 2, it is reasonable to assume they are working on a separate Blu-Ray Studio Pro, that is going to be completely different than DVD SP. Adobe Encore's support for Blu-Ray is extremely buggy, so obviously moving from DVD programming to Blu-Ray programming isn't just a simple tweak to the code.
    Apple doesn't pre-announce software they are working on so this is all guess work, but it is reasonable to assume that they are working on a Blu-Ray programming application. Be patient. Do you really have the money to burn on the bleeding edge of new technology? A single Blu-Ray burnable disc sells for $20. Two months ago the exact same disc sold for $45. Prices will continue to fall as things stablize.

  • SAP R/3 4.7e compatable with Netweaver foundation ?

    Hi,
    could you please suggest me for below Queries .
    1. Does IS-Media is very much compatable with 4.7e?
    2. Will this present problems for us in any of the functionality we've
    been expecting? Does 4.7
    have the same Netweaver foundation, integration with XI and
    Portals, etc?
    3. Can i integrate 4.7e with other new dimentional products like
    Solman3.2,XI,BW3.5,Portals , etc ?
    4. Which SAP release is recomandable for IS-Media to work? 4.7e or ECC ?
    I appriciate if you could suggest me for this.
    Thanks,
    Ahmed

    Even in Sandbox landscape having R/3 & XI on the samebox is not recommended.
    Moreover SAP R/3E & XI 7.0 don't have the same WebAs version(R/3 WebAS- 6.40 & XI WebAs -7.00). Hence they cannot be installed due to product compatibility. It should be atleast ECC 6.0.
    -SM

Maybe you are looking for