Significant difference within design view Dreamweaver CC

Hi all
I am making a site in Dreamweaver CC and if honest, I have just noticed something that has stopped me in my tracks that I am hoping is a common occurrence. The site in question is using Dreamweaver's media queries and I have not touched the boilerplate.
Design view pre CSS styling;
Live view seems to ignore this arrangement and puts everything on the page to 100%
The HTML for this section is;
<!--START mortgage_choices section -------------------------------------->
<div class="light_grey_backround">
  <div class="gridContainer clearfix">
    <div class="fluid mortgage_choices_title">
      <h1 class="dk_blue_text">Which type of new mortgage are you most interested in?</h1>
    </div>
    <div class="fluid mortgage_choices_subtitle">
      <h2 class="dk_grey_text">Simply pick the category that you fall into for more information on how we can help you with your mortgage. </h2>
    </div>
    <div class="fluid mortgage_choices_box zeroMargin_tablet zeroMargin_desktop">
    <figure class="fluid mortgage_choices_image">
        <img src="_images/newhomesmortgages_htb.jpg" alt="Help to Buy Mortgages"/>
        </figure>
    <div class="fluid mortgage_choices_title">
        <h3>HELP TO BUY MORTGAGES</h3>
        </div>
    <div class="fluid mortgage_choices_copy">
        We specialise in the Governament backed Help to Buy mortgage scheme and the fantastic mortgage schemes available with it. Enjoy the huge
        </div>
        <div class="fluid mortgage_choices_action">
        TELL ME MORE...
        </div>
    </div><div class="fluid mortgage_choices_box">
    <figure class="fluid mortgage_choices_image">
        <img src="_images/newhomesmortgages_mortgage_ftb.jpg" alt="First Time Buyer Mortgages"/>
        </figure>
    <div class="fluid mortgage_choices_title">
        <h3>HELP TO BUY MORTGAGES</h3>
        </div>
    <div class="fluid mortgage_choices_copy">
        We specialise in the Governament backed Help to Buy mortgage scheme and the fantastic mortgage schemes available with it. Enjoy the huge
        </div>
        <div class="fluid mortgage_choices_action">
        TELL ME MORE...
        </div>
    </div><div class="fluid mortgage_choices_box zeroMargin_tablet">
    <figure class="fluid mortgage_choices_image">
        <img src="_images/newhomesmortgages_mortgage_ntb.jpg" alt="Next Time Buyer Mortgages"/> </figure>
    <div class="fluid mortgage_choices_title">
        <h3>HELP TO BUY MORTGAGES </h3>
    </div>
    <div class="fluid mortgage_choices_copy">
        We specialise in the Governament backed Help to Buy mortgage scheme and the fantastic mortgage schemes available with it. Enjoy the huge
        </div>
        <div class="fluid mortgage_choices_action">
        TELL ME MORE...
        </div>
    </div>
    <div class="fluid mortgage_choices_box">
    <figure class="fluid mortgage_choices_image">
        <img src="_images/newhomesmortgages_mortgage_b2l.jpg" alt="Buy to Let Mortgages"/> </figure>
    <div class="fluid mortgage_choices_title">
        <h3>HELP TO BUY MORTGAGES</h3>
        </div>
    <div class="fluid mortgage_choices_copy">
        We specialise in the Governament backed Help to Buy mortgage scheme and the fantastic mortgage schemes available with it. Enjoy the huge
        </div>
        <div class="fluid mortgage_choices_action">
        TELL ME MORE...
        </div>
    </div>
  </div>
</div>
<!--END mortgage_choices section ---------------------------------------->
The CSS
@charset "UTF-8";
/* Simple fluid media
   Note: Fluid media requires that you remove the media's height and width attributes from the HTML
   http://www.alistapart.com/articles/fluid-images/
img, object, embed, video {
  width: 100%;
/* IE 6 does not support max-width so default to width 100% */
.ie6 img {
  width:100%;
  Dreamweaver Fluid Grid Properties
  dw-num-cols-mobile: 4;
  dw-num-cols-tablet: 8;
  dw-num-cols-desktop: 12;
  dw-gutter-percentage: 25;
  Inspiration from "Responsive Web Design" by Ethan Marcotte
  http://www.alistapart.com/articles/responsive-web-design
  and Golden Grid System by Joni Korpi
  http://goldengridsystem.com/
.fluid {
  clear: both;
  margin-left: 0;
  width: 100%;
  float: left;
  display: block;
.fluidList {
    list-style:none;
    list-style-image:none;
    margin:0;
    padding:0;       
/* Mobile Layout: 480px and below. */
.gridContainer {
  margin-left: auto;
  margin-right: auto;
  width: 85.5%;
  padding-left: 2.25%;
  padding-right: 2.25%;
  clear: none;
  float: none;
#div1 {
.title_index {
.subtitle_index {
.content_introduction {
.content_introduction_para_2 {
.mortgage_choices_title {
width: 100%;
margin-left: 0;
.mortgage_choices_subtitle {
.mortgage_choices_box {
  background-color: #FFFFFF;
  margin-bottom: 40px;
  border-radius: 7px;
  overflow-x: hidden;
  overflow-y: hidden;
  -webkit-box-shadow: 1px 1px 1px 1px #797979;
  box-shadow: 1px 1px 1px 1px #797979;
  width: 100%;
  clear: both;
  margin-left: 0;
.mortgage_choices_image {
width: 100%;
margin-left: 0;
.mortgage_choices_copy {
width: 100%;
margin-left: 0;
.mortgage_choices_action {
width: 100%;
margin-left: 0;
.rate_slider {
.rate_slider_header_title {
.rate_slider_subtitle {
.ratetitle {
  font-family: 'Source Sans Pro', sans-serif;
  font-size: 30px;
  color: #0F232A;
  margin-top: 35px;
  font-weight: 300;
  width: 90%;
  margin-left: 5%;
  line-height: 35px;
  margin-bottom: 10px;
  text-align: center;
.rate {
  font-family: 'Source Sans Pro', sans-serif;
  font-size: 30px;
  color: #3FB0B9;
  font-weight: 600;
  width: 90%;
  margin-bottom: -10px;
  text-align: center;
  margin-left: 5%;
.dealterm {
  font-family: 'Source Sans Pro', sans-serif;
  font-size: 22px;
  color: #666666;
  margin-bottom: 10px;
  width: 90%;
  margin-left: 5%;
  line-height: 23px;
  text-align: center;
.ltv {
  font-family: 'Source Sans Pro', sans-serif;
  font-size: 20px;
  color: #666666;
  margin-bottom: 10px;
  width: 90%;
  margin-left: 5%;
  text-align: center;
.costs {
  font-family: 'Source Sans Pro', sans-serif;
  font-size: 17px;
  color: #ccc;
  font-weight: 300;
  width: 49.1525%;
  width: 90%;
  margin-left: 5%;
  margin-bottom: 10px;
  text-align: center;
.erc {
  font-family: 'Source Sans Pro', sans-serif;
  font-size: 17px;
  color: #ccc;
  font-weight: 300;
  width: 66.1016%;
  width: 90%;
  margin-left: 5%;
  line-height: 20px;
  margin-bottom: 10px;
  text-align: center;
.revert {
  font-family: 'Source Sans Pro', sans-serif;
  font-size: 17px;
  color: #ccc;
  font-weight: 300;
  width: 90%;
  margin-left: 5%;
  line-height: 20px;
  text-align: center;
  margin-bottom: 30px;
.protection_choices_title {
  color: #3FB0B9;
  width: 100%;
  margin-left: 0;
.protection_choices_subtitle {
.protection_choices_box {
  background-color:#0F232A;
  margin-bottom: 40px;
  width: 100%;
  clear: both;
  margin-left: 0;
.protection_choices_image {
width: 100%;
margin-left: 0;
.protection_choices_copy {
  color: #FFFFFF;
  overflow-y: hidden;
  overflow-x: hidden;
  border-radius: 7px;
  -webkit-box-shadow: 1px 1px 1px 1px #666666;
  box-shadow: 1px 1px 1px 1px #666666;
  width: 100%;
  margin-left: 0;
.protection_choices_action {
  color: #3FB0B9;
  width: 100%;
  margin-left: 0;
.protection_question {
.protection_subquestion {
  margin-bottom:40px;
.contact_us_number {
.contact_us_email {
.contact_us_form {
.whole_of_market_title {
.whole_of_market_subtitle {
.whole_of_market_lenders {
.downloads_library_title {
.downloads_library_subtitle {
.download_cover {
.zeroMargin_mobile {
margin-left: 0;
.download_cover_container {
.download_cover_graphic {
width: 100%;
clear: both;
margin-left: 0;
.zeroMargin_mobile {
margin-left: 0;
.hide_mobile {
display: none;
/* Tablet Layout: 481px to 768px. Inherits styles from: Mobile Layout. */
@media only screen and (min-width: 481px) {
.gridContainer {
  width: 87.75%;
  padding-left: 1.125%;
  padding-right: 1.125%;
  clear: none;
  float: none;
  margin-left: auto;
#div1 {
.title_index {
.subtitle_index {
.content_introduction {
.content_introduction_para_2 {
.mortgage_choices_title {
width: 100%;
margin-left: 0;
.mortgage_choices_subtitle {
.mortgage_choices_box {
width: 48.7179%;
margin-left: 2.5641%;
clear: none;
.mortgage_choices_image {
width: 48.7179%;
margin-left: 0;
.mortgage_choices_copy {
width: 100%;
margin-left: 0;
.mortgage_choices_action {
width: 100%;
margin-left: 0;
.rate_slider {
.rate_slider_header_title {
.rate_slider_subtitle {
.ratetitle {
.rate {
.dealterm {
.ltv {
.costs {
.erc {
.revert {
.protection_choices_title {
width: 100%;
margin-left: 0;
.protection_choices_subtitle {
.protection_choices_box {
width: 48.7179%;
margin-left: 2.5641%;
clear: none;
.protection_choices_image {
width: 100%;
margin-left: 0;
.protection_choices_copy {
width: 100%;
margin-left: 0;
.protection_choices_action {
width: 100%;
margin-left: 0;
.protection_question {
.protection_subquestion {
.contact_us_number {
.contact_us_email {
.contact_us_form {
display: block;
.whole_of_market_title {
.whole_of_market_subtitle {
.whole_of_market_lenders {
.downloads_library_title {
display: block;
.downloads_library_subtitle {
display: block;
.download_cover_container {
.download_cover_graphic {
width: 100%;
clear: both;
margin-left: 0;
.hide_tablet {
display: none;
.zeroMargin_tablet {
margin-left: 0;
/* Desktop Layout: 769px to a max of 1232px.  Inherits styles from: Mobile Layout and Tablet Layout. */
@media only screen and (min-width: 769px) {
.gridContainer {
  width: 78.6666%;
  max-width: 1232px;
  padding-left: 0.6666%;
  padding-right: 0.6666%;
  margin: auto;
  clear: none;
  float: none;
  margin-left: auto;
#div1 {
.title_index {
.subtitle_index {
.content_introduction {
.content_introduction_para_2 {
.mortgage_choices_title {
width: 100%;
margin-left: 0;
.mortgage_choices_subtitle {
.mortgage_choices_box {
width: 23.7288%;
clear: none;
margin-left: 1.6949%;
.mortgage_choices_image {
width: 100%;
margin-left: 0;
.mortgage_choices_copy {
width: 100%;
margin-left: 0;
.mortgage_choices_action {
width: 100%;
margin-left: 0;
.rate_slider {
.rate_slider_header_title {
.rate_slider_subtitle {
.ratetitle {
.rate {
.dealterm {
.ltv {
.costs {
.erc {
.revert {
.protection_choices_title {
width: 100%;
margin-left: 0;
.protection_choices_subtitle {
.protection_choices_box {
width: 23.7288%;
clear: none;
margin-left: 1.6949%;
.protection_choices_image {
width: 100%;
margin-left: 0;
.protection_choices_copy {
width: 100%;
margin-left: 0;
.protection_choices_action {
width: 100%;
margin-left: 0;
.protection_question {
.protection_subquestion {
.contact_us_number {
.contact_us_email {
.contact_us_form {
display: block;
.whole_of_market_title {
.whole_of_market_subtitle {
.whole_of_market_lenders {
.downloads_library_title {
display: block;
.downloads_library_subtitle {
display: block;
.download_cover_container {
.download_cover_graphic {
width: 15.2542%;
margin-left: 1.6949%;
clear: none;
.zeroMargin_desktop {
  margin-left: 0;
.hide_desktop {
display: none;
Any help is appreciated as I am happy with what I have in design view, but it's live view that I am publishing...
Thanks in advance

Thank you for looking, I have resolved this issue. I was to do with the image %'s. When I changed this, it all fell into place.

Similar Messages

  • Why can't I drag images from Finder to Design View Dreamweaver CC?

    Hey Guys,
    I'm using OS X Mavericks (10.9) and Adobe DW CC
    For some reason in both CC and CS6 I can no-longer drag files from Finder (Mac OS X's Explorer) into the design view ( for eg: adding images to a table cell ), the browse button doesn't work properly either... The "browse for file" button only works if there is an image already there and then it will update the image, otherwise if there's no image in the table cell it will bring up the browse dialogue box but does nothing if I select a file and press "open".
    Is there a setting that was introduced in CS 6 that affects this behavior?

    Hi All,
    This bug has been fixed in the latest version of Dreamweaver CC 2014, which is now available for download.
    Download it from https://creative.adobe.com/ or directly through the Creative Cloud desktop app.
    We’re excited to hear back from you. Please share your feedback.

  • Code view not in synch with Design view (Dreamweaver CS3)

    Hello All,
    On my main work PC, I am running Dreamweaver CS3. When I am
    working in split view (with both Design and Code view visible) when
    I click on an element (say, a button) in Design view, the code view
    automatically shows me the code for the element that I am working
    on. That way, if I need to manually edit the code, I can click on
    the Code view and make the appropriate changes.
    On my laptop I am also running Dreamweaver CS3 However, when
    I am working in split view and I click on a element in Design view,
    my code view does NOT update itself and continues to show the last
    bit of code I was working on in Code view. While this could come in
    handy at times where i want design view and code view to show me
    two different things, I mostly would like code view to update
    automatically. Currently the only way I can get code view to update
    on my laptop is to hit the "refresh design view (F5)" button. Is
    there a way to do this automatically? Is this an option in
    Dreamweaver preferences because I don't see it anywhere.
    Thanks so much for your help.

    Ethereal_Mike wrote:
    > Does the new version of Dreamweaver CS3 print the code
    in color?
    No. If you feel that it's an important enhancement that you
    would like
    to see in future versions, submit a feature request:
    http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
    The more people who request a specific feature, the more
    likely it is to
    be implemented.
    David Powers, Adobe Community Expert
    Author, "Foundation PHP for Dreamweaver 8" (friends of ED)
    Author, "PHP Solutions" (friends of ED)
    http://foundationphp.com/

  • Design view dreamweaver compatibility

    Importing project from Proto to Dreamweaver 5.5 through adobe cloud, CSS files can only edit in Code view, Design view button is dissabled. Can Design view be activated?

    Marcfbcn wrote:
    Importing project from Proto to Dreamweaver 5.5 through adobe cloud, CSS files can only edit in Code view, Design view button is dissabled. Can Design view be activated?
    When you are editing a CSS file then it can only be done in code view because the file contains the styles to your markup.  To see the design,  you need to be in HTML files.
    Hope this helps.

  • Problem getting to second page of an existing form within Design View

    Hello, I am having a problem adjusting data within a preeixsting form.  I can see all the pages of the form in the hierarchy section and within XML.  However, I do not know how to appropriately adjust the coding in XML and want to adjust in the design view.  I just don't know how to get past the first page of the data.
    I figure this is a simple issue; however, I could not find assistance in the help documents.  Additionally, I have called the customer service number and spoken with technical support and have not had any assistance.  When I called on Monday I waited on hold for 8 hours and finally hung up.  I called on Tuesday and got an operator who told me that I would receive a call back within 4 hours.  Again, I waited at my desk for 4 hours and no call back.  At 4 hours and 50 minutes I got a call back, but had to arrange for another time to speak due to meetings.  I was told I would receive a call back during a 4 hour window yesterday and did not receive a call back.
    I called this morning and spoke with an operator who promised me a call back within a 2 hour time slot and again, no call back.
    Very poor customer service!  I also spoke with the technical "help" online and they were not helpful either!

    it could be to do with masterpages and the way the pagination is set up. Have a look at your pages in the heirarchy and if they are masterpages you need to have set the pagination for those pages at minimum 1 page each so they will show up.

  • Dreamweaver CC crashes when switching from code view to design view

    I am experiencing a recent problem with a file I am currently working. When I switch from code view to design view Dreamweaver crashes and requests a shut down. Other files seem to work without a problem. This particular files has 3 cascading EdgeAnimation CC files that are selected by media queries. I can test the page online without a problem but not in design or live view.

    Since your new page didn't crash, this leads me to believe that you have some critical errors and/or conflicts in your other page(s).
    Try running your code through the W3C validation tools. 
    CSS - http://jigsaw.w3.org/css-validator/
    HTML - http://validator.w3.org/
    Also debug JavaScript. 
    JavaScript - http://www.jslint.com/
    Nancy O.

  • Design View Renders YUI CSS Incorrectly

    I am evaluating Dreamweaver CS3 and find that opening a web
    page using YUI reset-fonts-grids CSS does not render correctly
    within design view. I'm rather surprised by this since improved CSS
    support is supposed to be a major feature of this version.
    Am I missing something? Or does rendering CSS styled pages
    remain a problem with Dreamweaver?

    SumBodyElze wrote:
    >> And interestingly enough, neither do the browsers.
    So you will always need to
    > test your
    > > pages in the browsers that matter to your end
    users.
    >
    > True. But the whole point of using YUI's CSS is to
    minimize the discrepancies
    > from browser to browser.
    Remember that that CSS is optimized for display in browsers,
    not within development tools. Dreamweaver won't respond to the
    hacks (see below) the same way a browser will.
    > Anyway, here's the actual page:
    >
    http://www.eugenebarnes.com/dw_cs3_test/index.php
    >
    > And here's a screen capture of the same page from
    Dreamweaver CS3:
    >
    http://www.eugenebarnes.com/dw_cs3_test/DW_CS3_screen.gif
    >
    > As you can see, Dreamweaver fails to stretch the inner
    DIVs to their full
    > width in display view. It doesn't even come close.
    There no way I'm going to go through all the compressed
    mashed up code for the CSS that you have attached to your document
    to see if there are any issues with some specific CSS in there.
    A casual glance at the CSS code *seems* to indicate that the
    code does include some CSS hacks to accomplish what it does for
    browsers. Because DW isn't a browser, it won't have the same CSS
    parsing issues as a browser has (not to say that it won't have any
    issues). It will react differently than browsers will to the hack
    code, and potentially to "regular" code as well. Once you throw a
    hack into the mix, you're really not working in a realm that
    Dreamweaver will be able to accurately represent the hacks.
    You might be able to work around some of the issues by
    creating a new CSS file and attach it as a design time style sheet
    ( Text -> CSS Styles -> Design time) , and set the width of
    the wrapper for the columns to something that displays what you
    want it to, perhaps it's 100% or perhaps its a fixed width. That
    may allow Dreamweaver to display the content similar to the way
    that your browser does.
    HTH
    Danilo Celic
    | Extending Knowledge Daily :
    http://CommunityMX.com/
    | Adobe Community Expert

  • Link to CSS problem (in Design View)

    Hello Dreamweaver experts,
    In the Design View Dreamweaver CS3 is not picking up the
    styles specified in a linked stylesheet. Let me explain...
    I am using an application in our office that relies upon HTML
    (but does not use a standard web browser).
    I need to refer to linked stylesheets using a variable like
    so;
    [example #1]
    <link href="{FILES_DIR}/path/css/stylesheet.css"
    rel="stylesheet" type="text/css" />
    The use of the variable construction "{FILES_DIR}" eliminates
    the need to hard code a drive letter into the link which is
    preferrable. Without "{FILES_DIR}" I have to hard-code the drive
    letter like so;
    [example #2]
    <link
    href="file:///K|/additional-path-details/path/css/stylesheet.css"
    rel="stylesheet" type="text/css" -->
    Both examples above yield the same result in the application
    (the stylesheet is found and its styles properly applied).
    However, only with example #2 does Dreamweaver's "design
    view" pick up and apply the stylesheet. Dreamweaver cannot find the
    stylesheet or apply its styles using example #1.
    My question is how can I make Dreamweaver understand and
    apply what "{FILES_DIR}" means.
    Any tips, tricks or pointers would be most welcome...

    "horse.badorties" <[email protected]> wrote
    in message
    news:fh9o12$80d$[email protected]..
    > Hello Dreamweaver experts,
    >
    > In the Design View Dreamweaver CS3 is not picking up the
    styles specified
    > in a
    > linked stylesheet. Let me explain...
    >
    > I am using an application in our office that relies upon
    HTML (but does
    > not
    > use a standard web browser).
    >
    > I need to refer to linked stylesheets using a variable
    like so;
    >
    >
    [example #1]
    > <link href="{FILES_DIR}/path/css/stylesheet.css"
    rel="stylesheet"
    > type="text/css" />
    >
    > The use of the variable construction "{FILES_DIR}"
    eliminates the need to
    > hard
    > code a drive letter into the link which is preferrable.
    Without
    > "{FILES_DIR}"
    > I have to hard-code the drive letter like so;
    >
    >
    [example #2]
    > <link
    href="file:///K|/additional-path-details/path/css/stylesheet.css"
    > rel="stylesheet" type="text/css" -->
    >
    > Both examples above yield the same result in the
    application (the
    > stylesheet
    > is found and its styles properly applied).
    >
    > However, only with example #2 does Dreamweaver's "design
    view" pick up and
    > apply the stylesheet. Dreamweaver cannot find the
    stylesheet or apply its
    > styles using example #1.
    Did you look into "design-time" styles sheets? That may solve
    your problem.
    It won't take care of the path in the document though...
    Thierry
    Articles and Tutorials:
    http://www.TJKDesign.com/go/?0
    http://www.divahtml.com/products/scripts_dreamweaver_extensions.php
    - divaGPS - Add "you are here" highlighting to virtually any
    menu
    - divaFAQ - Create FAQ pages that toggle (show/hide) the
    answers
    - divaPOP - Easy, clean, standards-compliant popup windows.

  • JSF design view - visual components are shrinking

    Hello,
    I have some strange issue while using Design view for JSF and data binding.
    Once I drop any data control elements into visual component (panel, etc) my visual components are shrinking to such size, that I cannot distinguish any elements within design view. I cannot use design view since then and have to place all elements base on structure panel.
    How to reproduce:
    1. Create new JSF page with wizard and accept defaults.
    2. Drop one of the panels (panel box, panel group layout) into JSF layout
    At this stage my visual elements occupy 100% of design view screen and represent anticipated outcome
    3. Drag and drop one of the data control elements (data control panel) into created panels on JSF and create table or form
    Immediately after it visual panel where data control was dropped shrinks to approximately 1/4 of the screen and I cannot see neither available space nor created table for my data components.
    I figured out, that if I remove created by wizard default <af:messages> tag from the top of my JSF, then design view representation fixes. Not sure if I should remove <af:messages> from all my pages.
    Above all looks to me as and bug.
    Environment:
    -Jdeveloper 11g
    -Windows Vista 64b
    -Not bundled JDK 6

    Hi Shay,
    Thank you for response.
    1. I tried to play with screen size without result
    2. I checked your video post, but this does not resolve my issue
    3. This issue occures with all JSF pages and can be reproduced even when following official Oracle step by step tutorials.
    4. I figured out, that removing <af:messages> tag resolves the issue ?! It seems this tag is added by default during drag and drop binding.
    5. On this link http://drop.io/jdev_001 you can see how design view is changes with and without <af:messages> tag
    6. Below is code example from one of the tutorials, that leads to shrinking as well:
    7. Once app is deployed and running page get normal view in IE as expected, so it seems to me, it is issue with Jdev design view, probably influenced by my environment, if nobody reported it before.
    Thank you for your help.
    ===========================================================================
    <?xml version='1.0' encoding='windows-1252'?>
    <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html"
    xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
    <jsp:directive.page contentType="text/html;charset=windows-1252"/>
    <f:view>
    <af:document id="d1">
    <af:messages id="m1"/>
    <af:form id="f1">
    <af:panelStretchLayout id="psl1">
    <f:facet name="center">
    <!-- id="af_one_column_stretched" -->
    <af:decorativeBox theme="dark" id="db1">
    <f:facet name="center">
    <af:decorativeBox theme="medium" id="db2">
    <f:facet name="center">
    <af:panelFormLayout id="pfl1">
    <af:inputText value="#{bindings.p_name.inputValue}" label="#{bindings.p_name.hints.label}"
    required="#{bindings.p_name.hints.mandatory}" columns="#{bindings.p_name.hints.displayWidth}"
    maximumLength="#{bindings.p_name.hints.precision}" shortDesc="#{bindings.p_name.hints.tooltip}" id="it1">
    <f:validator binding="#{bindings.p_name.validator}"/>
    </af:inputText>
    <af:commandButton actionListener="#{bindings.getEmployeesFindByName.execute}" text="getEmployeesFindByName"
    disabled="#{!bindings.getEmployeesFindByName.enabled}" id="cb1"/>
    <af:panelFormLayout id="pfl2">
    <af:inputText value="#{bindings.commissionPct.inputValue}" label="#{bindings.commissionPct.hints.label}"
    required="#{bindings.commissionPct.hints.mandatory}" columns="#{bindings.commissionPct.hints.displayWidth}"
    maximumLength="#{bindings.commissionPct.hints.precision}" shortDesc="#{bindings.commissionPct.hints.tooltip}"
    id="it4">
    <f:validator binding="#{bindings.commissionPct.validator}"/>
    <af:convertNumber groupingUsed="false" pattern="#{bindings.commissionPct.format}"/>
    </af:inputText>
    <af:inputText value="#{bindings.email.inputValue}" label="#{bindings.email.hints.label}"
    required="#{bindings.email.hints.mandatory}" columns="#{bindings.email.hints.displayWidth}"
    maximumLength="#{bindings.email.hints.precision}" shortDesc="#{bindings.email.hints.tooltip}" id="it7">
    <f:validator binding="#{bindings.email.validator}"/>
    </af:inputText>
    <af:inputText value="#{bindings.employeeId.inputValue}" label="#{bindings.employeeId.hints.label}"
    required="#{bindings.employeeId.hints.mandatory}" columns="#{bindings.employeeId.hints.displayWidth}"
    maximumLength="#{bindings.employeeId.hints.precision}" shortDesc="#{bindings.employeeId.hints.tooltip}"
    id="it6">
    <f:validator binding="#{bindings.employeeId.validator}"/>
    <af:convertNumber groupingUsed="false" pattern="#{bindings.employeeId.format}"/>
    </af:inputText>
    <af:inputText value="#{bindings.firstName.inputValue}" label="#{bindings.firstName.hints.label}"
    required="#{bindings.firstName.hints.mandatory}" columns="#{bindings.firstName.hints.displayWidth}"
    maximumLength="#{bindings.firstName.hints.precision}" shortDesc="#{bindings.firstName.hints.tooltip}" id="it3">
    <f:validator binding="#{bindings.firstName.validator}"/>
    </af:inputText>
    <af:inputDate value="#{bindings.hireDate.inputValue}" label="#{bindings.hireDate.hints.label}"
    required="#{bindings.hireDate.hints.mandatory}" shortDesc="#{bindings.hireDate.hints.tooltip}" id="id1">
    <f:validator binding="#{bindings.hireDate.validator}"/>
    <af:convertDateTime pattern="#{bindings.hireDate.format}"/>
    </af:inputDate>
    <af:inputText value="#{bindings.jobId.inputValue}" label="#{bindings.jobId.hints.label}"
    required="#{bindings.jobId.hints.mandatory}" columns="#{bindings.jobId.hints.displayWidth}"
    maximumLength="#{bindings.jobId.hints.precision}" shortDesc="#{bindings.jobId.hints.tooltip}" id="it2">
    <f:validator binding="#{bindings.jobId.validator}"/>
    </af:inputText>
    <af:inputText value="#{bindings.lastName.inputValue}" label="#{bindings.lastName.hints.label}"
    required="#{bindings.lastName.hints.mandatory}" columns="#{bindings.lastName.hints.displayWidth}"
    maximumLength="#{bindings.lastName.hints.precision}" shortDesc="#{bindings.lastName.hints.tooltip}" id="it8">
    <f:validator binding="#{bindings.lastName.validator}"/>
    </af:inputText>
    <af:inputText value="#{bindings.phoneNumber.inputValue}" label="#{bindings.phoneNumber.hints.label}"
    required="#{bindings.phoneNumber.hints.mandatory}" columns="#{bindings.phoneNumber.hints.displayWidth}"
    maximumLength="#{bindings.phoneNumber.hints.precision}" shortDesc="#{bindings.phoneNumber.hints.tooltip}"
    id="it9">
    <f:validator binding="#{bindings.phoneNumber.validator}"/>
    </af:inputText>
    <af:inputText value="#{bindings.salary.inputValue}" label="#{bindings.salary.hints.label}"
    required="#{bindings.salary.hints.mandatory}" columns="#{bindings.salary.hints.displayWidth}"
    maximumLength="#{bindings.salary.hints.precision}" shortDesc="#{bindings.salary.hints.tooltip}" id="it5">
    <f:validator binding="#{bindings.salary.validator}"/>
    <af:convertNumber groupingUsed="false" pattern="#{bindings.salary.format}"/>
    </af:inputText>
    <f:facet name="footer">
    <af:panelGroupLayout layout="vertical" id="pgl1">
    <af:panelGroupLayout layout="horizontal" id="pgl2">
    <af:commandButton actionListener="#{bindings.First.execute}" text="First" disabled="#{!bindings.First.enabled}"
    partialSubmit="true" id="cb2"/>
    <af:commandButton actionListener="#{bindings.Previous.execute}" text="Previous" disabled="#{!bindings.Previous.enabled}"
    partialSubmit="true" id="cb3"/>
    <af:commandButton actionListener="#{bindings.Next.execute}" text="Next" disabled="#{!bindings.Next.enabled}"
    partialSubmit="true" id="cb4"/>
    <af:commandButton actionListener="#{bindings.Last.execute}" text="Last" disabled="#{!bindings.Last.enabled}"
    partialSubmit="true" id="cb6"/>
    </af:panelGroupLayout>
    <af:commandButton text="Save" id="cb5" actionListener="#{bindings.mergeDepartments.execute}"
    disabled="#{!bindings.mergeDepartments.enabled}" action="browse"/>
    </af:panelGroupLayout>
    </f:facet>
    </af:panelFormLayout>
    </af:panelFormLayout>
    </f:facet>
    </af:decorativeBox>
    </f:facet>
    </af:decorativeBox>
    </f:facet>
    </af:panelStretchLayout>
    </af:form>
    </af:document>
    </f:view>
    </jsp:root>
    Edited by: user555411 on May 2, 2010 2:08 PM

  • Flash Builder 4.7 and design view question

    I have programmed a large, commercial level mobile application using Flash Builder 4.6. It is working GREAT when ran on both iOS and Android devices. 
    I was using the trial version of Flash Builder 4.6 to develop this application. I used the states feature that FB has built in to handle Portrait, Landscape, and Phone / Tablet configs. This means that I built 4 different layouts for all 8 of my views in my mobile application. Using the design view in FB 4.6 was what allowed me to do this.
    I have to say that I LOVE Flash Builder so far. GREAT tool. 
    My trial ended just last week. I had to purchase version 4.7 of the software, only to find out that they REMOVED the design view from the software.
    All complaining aside, what have other programmers who are in the same boat as me done as a solution? I would like to continue to program in AS and Flash Builder as I have taken the time to write the application and learn the whole platform. 
    As it stands now, I am in the process of downgrading my liscence keys from 4.7 to 4.6, but in order to do this I had to RETURN my retail version of FB 4.7 premium (bought online) and buy a volume liscening version (NOT through adobe, only allowed to do this through a reseller such as CDW). then once I have a key for 4.7 through volume liscencing, it can be downgraded to 4.6.
    I'm hoping to get input from others in the same boat. Did you change Programming languages? if so, to what? Did you change IDE's? If so, to what?

    Joe -
         I actually never completed the downgrade to 4.6 so I've been using 4.7 without the design view.    In 4.6, I would put a control on the view within design view.  Then I would change each state, move it around, and it would be placed that way.  In my case, each view has 4 states - portraitPhone, landscapePhone, portraitTablet, and landscapeTablet.   I had to do this 4 times for each control under 4.6
         So I went back and looked at my code in 4.7 and all the resulting code was these explicit x, y, height, and width values.  See the code below:
    <s:states> <s:State name="portraitPhone" stateGroups="phone,portrait"
    />
     <s:State name="landscapePhone" stateGroups="phone,landscape"/>
     <s:State name="portraitTablet" stateGroups="tablet,portrait"/>
     <s:State name="landscapeTablet" stateGroups="tablet,landscape"/>
     </s:states>
     <s:List id="lstMake" x="10" y="19" height="25%" allowMultipleSelection="false"borderVisible="
    true" click="changeMake(event)" labelField="label"width.landscapePhone="
    295" height.landscapePhone="105"x.landscapeTablet="
    25" y.landscapeTablet="54" width.landscapeTablet="461"height.landscapeTablet="
    292" fontSize.landscapeTablet="24"width.portraitPhone="
    182" height.portraitPhone="175"x.portraitTablet="
    16" y.portraitTablet="35" width.portraitTablet="399"height.portraitTablet="
    360" fontSize.portraitTablet="24">
     <s:dataProvider>
     <s:ArrayList id="makeCollection">
     <fx:Object label="Cadillac" data="18"/>
     <fx:Object label="Chevrolet" data="1"/>
     <fx:Object label="Dodge" data="2"/>
     <fx:Object label="Ford" data="3"/>
     <fx:Object label="GMC" data="4"/>
     <fx:Object label="Isuzu" data="6"/>
     <fx:Object label="Jeep" data="7"/>
     <fx:Object label="Licoln" data="8"/>
     <fx:Object label="Mazda" data="9"/>
     <fx:Object label="Mercury" data="10"/>
     <fx:Object label="Nissan" data="11"/>  
    <fx:Object label="Oldsmobile" data="12"/>
     <fx:Object label="Sterling" data="20"/>
     <fx:Object label="Suzuki" data="13"/>
     <fx:Object label="Toyota" data="14"/>
     </s:ArrayList>
     </s:dataProvider>
     </s:List>
     <s:Label x="10" y="8" fontSize="11" text="Vehicle Make"x.landscapeTablet="
    10" y.landscapeTablet="23" fontSize.landscapeTablet="24"fontSize.portraitTablet="
    24"/>
     <s:Label x="143" y="11" fontSize="11" text="Vehicle Year"x.landscapePhone="
    354" y.landscapePhone="10"x.landscapeTablet="
    517" y.landscapeTablet="23" width.landscapeTablet="143"height.landscapeTablet="
    26" fontSize.landscapeTablet="24"x.portraitPhone="
    204" y.portraitPhone="8"x.portraitTablet="
    446" y.portraitTablet="11" fontSize.portraitTablet="24"/>
     <s:List id="lstYear" x="145" y="20" height="25%" allowMultipleSelection="false"borderVisible="
    true" click="doYearChange(event)" dataProvider="{yearCollection}"labelField="
    value"x.landscapePhone="
    313" y.landscapePhone="19" width.landscapePhone="157"height.landscapePhone="
    105"x.landscapeTablet="
    524" y.landscapeTablet="54" width.landscapeTablet="343"height.landscapeTablet="
    292" fontSize.landscapeTablet="24"x.portraitPhone="
    200" y.portraitPhone="19" height.portraitPhone="194"x.portraitTablet="
    453" y.portraitTablet="37" width.portraitTablet="276"height.portraitTablet="
    358" fontSize.portraitTablet="24">
     </s:List>
     <s:List id="lstModel" x="10" y="147" height="30%" borderVisible="true"dataProvider="
    {modelCollection}" labelFunction="lblFunct"width.landscapePhone="
    460" height.landscapePhone="99"x.landscapeTablet="
    13" y.landscapeTablet="384" width.landscapeTablet="992"height.landscapeTablet="
    309" fontSize.landscapeTablet="24"x.portraitPhone="
    10" y.portraitPhone="221" width.portraitPhone="301"height.portraitPhone="
    184" allowMultipleSelection="false"click="doModelSelected(event)" fontSize.portraitPhone="
    12"x.portraitTablet="
    16" y.portraitTablet="428" width.portraitTablet="742"height.portraitTablet="
    521" fontSize.portraitTablet="24"></s:List>
     <s:Label x="12" y="132" fontSize="11" text="Vehicle Model"x.landscapeTablet="
    10" y.landscapeTablet="354" fontSize.landscapeTablet="24"x.portraitPhone="
    10" y.portraitPhone="207"x.portraitTablet="
    10" y.portraitTablet="401" width.portraitTablet="154"height.portraitTablet="
    21" fontSize.portraitTablet="24"/>
      So instead of continuing to try and modify these values by hand, then run the program, using trial and error, I took a different tact.   I removed ALL x y height and width values.  Then, I wrapped all the mxml code in either <s:HGroup or <s:Vghroup tags depending on what I wanted.  Then I would just set the vertical and horizontal align on these groups.  This allows everything to scale correctly based on the size of the view (each device really is a little different).   Finally,  I hand entered things like font sizes by using State Groups like this:   fontSize.phone="12"  fontSize.tablet="22".    It still took testing on the screen to see how my layouts worked but it just makes the UI so much easier to change around and works so much better with out all the static stuff in it.
    If you have some time , I would suggest taking one of your 4.6 views that has all these static variables and trying to modify it to work like I said above.    My modified code (to do the same thing as above) is below:
    <s:states> <s:State name="portraitPhone" stateGroups="phone,portrait"
    />
     <s:State name="landscapePhone" stateGroups="phone,landscape"/>
     <s:State name="portraitTablet" stateGroups="tablet,portrait"/>
     <s:State name="landscapeTablet" stateGroups="tablet,landscape"/>
     </s:states>
     <s:VGroup height="100%" width="100%" verticalAlign="top">
     <s:HGroup paddingTop="10" width="100%" height="50%">
     <s:VGroup width="60%" paddingLeft="5">
     <s:Label fontSize="11" text="Vehicle Make"fontSize.tablet="
    24"/>
     <s:List id="lstMake" width="100%" allowMultipleSelection="false"borderVisible="
    true" click="changeMake(event)" labelField="label"fontSize.tablet="
    24" fontSize.phone="12">
     <s:layout>
     <s:VerticalLayout horizontalAlign="contentJustify" requestedMaxRowCount.portraitTablet="8" requestedMaxRowCount.phone="6" requestedMaxRowCount.landscapeTablet="4"gap="
    0" rowHeight.phone="28" variableRowHeight="false" rowHeight="55"verticalAlign="
    middle"/>
     </s:layout>
     <s:dataProvider>
     <s:ArrayList id="makeCollection">
     <fx:Object label="Cadillac" data="18"/>
     <fx:Object label="Chevrolet" data="1"/>
     <fx:Object label="Dodge" data="2"/>
     <fx:Object label="Ford" data="3"/>
     <fx:Object label="GMC" data="4"/>
     <fx:Object label="Isuzu" data="6"/>
     <fx:Object label="Jeep" data="7"/>
     <fx:Object label="Lincoln" data="8"/>
     <fx:Object label="Mazda" data="9"/>
     <fx:Object label="Mercury" data="10"/>
     <fx:Object label="Nissan" data="11"/>  
    <fx:Object label="Oldsmobile" data="12"/>
     <fx:Object label="Sterling" data="20"/>
     <fx:Object label="Suzuki" data="13"/>
     <fx:Object label="Toyota" data="14"/>
     </s:ArrayList>
     </s:dataProvider>
     </s:List>
     </s:VGroup>
     <s:VGroup width="30%">
     <s:Label fontSize="11" text="Vehicle Year"fontSize.tablet="
    24"/>
     <s:List id="lstYear" width="100%" allowMultipleSelection="false" borderVisible="
    true" click="doYearChange(event)" dataProvider="{yearCollection}"labelField="
    value" fontSize.phone="12" fontSize.tablet="24">
     <s:layout>
     <s:VerticalLayout horizontalAlign="contentJustify" requestedMaxRowCount.portraitTablet="8" requestedMaxRowCount.phone="6" requestedMaxRowCount.landscapeTablet="4"gap="
    0" rowHeight.phone="28" variableRowHeight="false" rowHeight.tablet="55"verticalAlign="
    middle"  
    />
     </s:layout>
     </s:List>
     </s:V

  • Design View is black

    After adding my site to CS4, the Design View of all pages is
    black. Code View works. Live View works. It's only Design View
    that's giving me trouble. Without Design View, Dreamweaver is
    useless to people like me who aren't proficient in code. I've tried
    working through this with the customer support folks and the person
    who designed my webiste. No one can figure it out. Help!
    Note that I can go back to an old version of the page located
    elsewhere on my computer, open it, and it shows up fine.

    >
    http://www.shccnet.org/contracts/appraisers.asp
    Are you using includes, or is it just bad syntax?
    There are TWO sets of <body> tags.
    Sort it out and it should display.
    Delete this, lines 11 to 19
    <head>
    <title>Appraisers | SHCC</title>
    <meta name="generator"
    content="BBEdit 8.5" />
    <link rel="stylesheet" type="text/css"
    href="../css/shcc-default.css" media="all" />
    <!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>
    <title>Untitled
    Page</title>
    </head>
    <body>
    </body>
    </html>
    If it doesn't display then, next thing to look at would be
    the css file.
    Alan
    Adobe Community Expert, dreamweaver
    http://www.adobe.com/communities/experts/

  • Design view issue - CSS and html

    Hi
    I was wondering if anyone can help me with this. Someone has
    created a page for me using html and CSS as requested. The problem
    is that whenever I try to open the index.html file in design view
    or code and design view, Dreamweaver crashes and I have to restart.
    I am attaching the html and CSS below. Just as an aside, I have
    asked them to create the code using CSS rather than tables and have
    ended up with div hell.
    Cheers
    Julie
    @charset "utf-8";
    * {padding:0; margin:0;}
    body {padding:10px 0 10px 0; background-color:#fff; margin:0
    auto; width: 976px; font-family:Arial, Helvetica, sans-serif;
    font-size:11px; color:#333;}
    #wrap {margin:0 auto; padding:0; position:relative; width:
    976px;}
    a:link { color:#999; text-decoration: underline; }
    a:visited { color:#999; text-decoration: underline; }
    a:hover{ color:#666; text-decoration: none; }
    img { border:none; padding:0; margin:0;}
    h1 {font-size: 36px;}
    h2 {font-size: 24px;}
    h3 {font-size: 18px;}
    h4 {font-size: 16px;}
    h5 {font-size: 14px;}
    h6 {font-size: 11px;}
    input { position:relative; font-weight: normal;cursor:
    pointer;vertical-align: middle;padding: 0 3px;font-size:
    13px;font-family: Verdana, Helvetica, Arial, sans-serif;
    border:#a09f6f 1px solid;}
    select {font-family: Verdana, Helvetica, Arial,
    sans-serif;font-weight: normal;cursor: pointer;vertical-align:
    middle;border: 1px solid #999;padding: 1px;background-color:
    #FAFAFA;}
    option {padding-right: 2px;}
    textarea {font-family: "Lucida Grande", Verdana, Helvetica,
    Arial, sans-serif; width: 60%;padding: 2px;font-size:
    1em;line-height: 1.4em; border:#a09f6f 1px solid; width:390px;
    height:170px;}
    /* Header Part Start */
    #header {margin:0; padding:0; position:relative;
    background:url(../images/index_01.jpg); width:976px; height:97px; }
    #header .headprt {margin:0; padding:0; position:relative }
    #header .headprt .headprtr { float:right; width: 500px;
    margin:0; padding:0; position:relative }
    #header .headprt .headprtr .padhr { color:#fff; margin:0;
    padding:16px 44px 0 0; position:relative; text-align:right;}
    #header .headprt .headprtl {margin:0 500px 0 0; padding:0;
    position:relative;}
    #header .headprt .headprtl .padhl{ color:#fff; margin:0;
    padding:40px 0 0 44px; position:relative }
    .hhllb { font-size:16px;}
    .hhlld { font-size:16px; font-weight:bold}
    .hhllc { font-size: 20px; font-weight:bold}
    .hhlls { font-size:14px}
    .kulay { color:#e55b68}
    /* Header Part End */
    /* Main Part Start */
    #maincontent {margin:0; padding:0; clear:both;
    position:relative; display:block; background-color:#fff }
    #maincontent .boxmainbgl {margin:0; padding:0;
    position:relative; background: url(../images/index_10.jpg) repeat-y
    top left; }
    #maincontent .boxmainbgl .boxmainbgr {margin:0; padding:0;
    position:relative; background: url(../images/index_11.jpg) repeat-y
    top right; }
    #maincontent .boxmainbgl .boxmainbgr .boxmainbgtopl
    {margin:0; padding:0; position:relative;
    background:url(../images/index_02.jpg) no-repeat top left; }
    #maincontent .boxmainbgl .boxmainbgr .boxmainbgtopl
    .boxmainbgtopr {margin:0; padding:0; position:relative;
    background:url(../images/index_05.jpg) no-repeat top right; }
    #maincontent .boxmainbgl .boxmainbgr .boxmainbgtopl
    .boxmainbgtopr .boxmainbgbotl {margin:0; padding:0;
    position:relative; background:url(../images/index_15.jpg) no-repeat
    bottom left; }
    #maincontent .boxmainbgl .boxmainbgr .boxmainbgtopl
    .boxmainbgtopr .boxmainbgbotl .boxmainbgbotr {margin:0; padding:0;
    position:relative; background:url(../images/index_16.jpg) no-repeat
    bottom right; }
    #maincontent .boxmainbgl .boxmainbgr .boxmainbgtopl
    .boxmainbgtopr .boxmainbgbotl .boxmainbgbotr .boxpadzki {margin:0;
    padding:8px 48px 0 49px; position:relative; height: 1340px;}
    .mainconup {margin:0; padding:0; position:relative;
    clear:both; display:block; overflow:hidden; height:485px }
    .mainconup .mmtoprt { float: right; width:615px; margin:0;
    padding:0; position:relative }
    .mainconup .mmtoprt .mmrtM {margin:0; padding:0;
    position:relative; background:url(../images/picpic.jpg) no-repeat
    top left; height:479px; }
    .mainconup .mmtoprt .mmrtM .mmrtA {margin:0; padding:200px 0
    0 10px; position:relative; width:600px; }
    .mainconup .mmtoprt .mmrtM .mmrtA .mmppr { float:right;
    width: 195px; margin:0 0 0 -3px; padding:0; position:relative }
    .mainconup .mmtoprt .mmrtM .mmrtA .mmppc {margin:0 195px 0 0;
    padding:0; position:relative;}
    .mainconup .mmtoprt .mmrtM .mmrtA .mmppc .mmppx {float:right;
    width: 205px; margin:0; padding:0; position:relative}
    .mainconup .mmtoprt .mmrtM .mmrtA .mmppc .mmppl {margin:0
    205px 0 0; padding:0; position:relative; height:100px}
    .bkspdC { font-size: 22px; font-weight:bold; color:#fff;
    margin:0; padding:30px 0 0 0; position:relative; line-height:20px}
    .bkspdB { font-size: 22px; font-weight:bold; color:#fff;
    margin:0; padding:20px 0 0 0; position:relative; line-height:20px}
    .bkspdA { font-size: 22px; font-weight:bold; color:#fff;
    margin:0; padding:30px 0 0 10px; position:relative;
    line-height:20px}
    .mainconup .mmtoplt {margin:0 615px 0 0; padding:0;
    position:relative }
    .mainconup .mmtoplt .logo {margin:0; padding:2px 0 0 3px;
    position:relative }
    .mainconup .mmtoplt .linek {margin:10px 20px 7px 3px;
    font-size:2px; padding:0; position:relative; border-top: #e7e7e7
    2px solid }
    .mainconup .mmtoplt .pargs {margin:0; padding:10px 20px 0
    3px; position:relative; line-height:13px }
    .hhllw { font-size: 22px; font-weight:bold; color:#23a9e8}
    .maincentr { clear:both; margin:0; padding:0;
    position:relative; background-color:#2774c2; display:block; }
    .maincentr .mckbb {margin:0; padding:10px 10px 20px 20px;
    position:relative; color:#fff; }
    .maincentr .mckbb .mckrt {margin:0; padding:0;
    position:relative; float:right; width:290px }
    .maincentr .mckbb .mcklt {margin:0 290px 0 0; padding:0;
    position:relative }
    .maincentr .mckbb .mcklt .mcklrr {margin:0; padding:0;
    position:relative; float:right; width:290px; height:170px;
    background:url(../images/bgline.jpg) no-repeat right 10px; }
    .maincentr .mckbb .mcklt .mcklcc {margin:0 290px 0 0;
    padding:0; position:relative; height:170px;
    background:url(../images/bgline.jpg) no-repeat right 10px; }
    .maincentr .cbgc {margin:0; padding:0; position:relative;
    background:url(../images/bgline2.gif) repeat-x top left;
    height:2px; font-size:2px}
    .customks {margin:0; padding:0; position:relative;
    font-size:20px; font-weight:bold }
    .quotep {margin:0; padding:20px 20px 0 0; position:relative }
    .quotep .quotea {margin:0; padding:0; position:relative;
    background:url(../images/qouteleft.jpg) no-repeat top left; }
    .quotep .quotea .quoteb {margin:0; padding:0;
    position:relative; background:url(../images/qouteright.jpg)
    no-repeat bottom right }
    .quotep .quotea .quoteb .quotez {margin:0; padding:28px 0 0
    0; position:relative; font-size:12px; line-height:13px; }
    .xquotep {margin:0; padding:20px 20px 0 20px;
    position:relative }
    .xquotep .xquotea {margin:0; padding:0; position:relative;
    background:url(../images/qouteleft.jpg) no-repeat top left; }
    .xquotep .xquotea .xquoteb {margin:0; padding:0;
    position:relative; background:url(../images/qouteright.jpg)
    no-repeat bottom right }
    .xquotep .xquotea .xquoteb .xquotez {margin:0; padding:28px 0
    0 0; position:relative; font-size:12px; line-height:13px; }
    .mainbut {margin:6px 0 0 0; padding:0;
    position:relative;clear:both; display:block }
    .mainbut .mainbbj {margin:0; padding:0; position:relative }
    .mainbut .mainbbj .mainbbrt {margin:0; padding:0;
    position:relative; float: right; width: 167px }
    .mainbut .mainbbj .mainbbrt .sshots {margin:0; padding:0 0
    2px 0; position:relative; width: 167px }
    .mainbut .mainbbj .mainbbrt .sshots .higfx {margin:0;
    padding:0; position:relative; width: 167px; height:122px;
    overflow:hidden }
    .mainbut .mainbbj .mainbblt {margin:0 167px 0 0; padding:0;
    position:relative }
    .mainbut .mainbbj .mainbblt .mainbbrr {margin:0; padding:0;
    position:relative; float: right; width: 425px }
    .mainbut .mainbbj .mainbblt .mainbbrr .mainbbpads {margin:0;
    padding:10px 26px 0 26px; position:relative; font-size:12px;
    line-height:14px }
    .mainbut .mainbbj .mainbblt .mainbbcc {margin:0 425px 0 0;
    padding:0; position:relative; background:#3a3a3a; color:#fff }
    .mainbut .mainbbj .mainbblt .mainbbcc .mainccpads {margin:0;
    padding:20px 25px 25px 18px; position:relative; font-size:12px;
    line-height:15px }
    .hhllt { font-size: 20px; font-weight:bold; color:#23a9e8}
    .hhllk { font-size: 18px; color:#23a9e8}
    /* Main Part End */
    /* Footer Part Start */
    #footer {margin:0; padding:0; clear:both; position:relative;
    display:block }
    #footer .footboxbg {margin:0; padding:0; position:relative;
    background: url(../images/index_18.jpg) repeat-x top left; }
    #footer .footboxbg .footboxlt {margin:0; padding:0;
    position:relative; background: url(../images/index_17.jpg)
    no-repeat top left; }
    #footer .footboxbg .footboxlt .footboxrt {margin:0;
    padding:0; position:relative; background:
    url(../images/index_20.jpg) no-repeat top right; height:36px }
    /* Footer Part End */

    Web Dynpro doesn't allow for the inclusion of custom HTML and CSS.  It is far building business application in a client rendering abstracted framework. 
    If you need some common header, then you should consider the usage of the NetWeaver Portal.

  • How to hide content in design view within Dreamweaver?

    How can I hide content in design view within Dreamweaver?
    I have a tabbed content menu that uses some javascript. Everything looks great in Live view, but when I go to design view, all the content goes way beyond the div. How can I make it to where I can hide the content in that div in design view or wrap it completely inside of there? It's really hard to explain which is why I provided some pictures!
    LIVE VIEW
    DESIGN VIEW
    Thank you in advance for all the help!
    Dalton

    Humm....... you want to hide it in Design View whilst working on the rest of the site?
    If that is the case set the menu container <div> to display: none; -
    <div id="menu" style="display: none;">This is the content menu</div>
    Then either set it to display: block; when you're ready to view it live or remove the style completely.

  • Dreamweaver 8 Design View render issue

    I was wondering if anyone else has noticed a highly
    irritating issue with DW8 that is apparently not an issue in the
    Design View of DW MX 2004.
    In DW 8 for some reason I'm getting an extra 150 pixels of
    white space to the right of my #content container. It only appears
    to happen when the content within the #content container does NOT
    exceed the length of the content in my menu container (#priNav2).
    In other words, if the content is longer then the menu, it renders
    fine.
    See here:
    Dreamweaver
    8
    But, in DW mx2004 the exact same file shows up how it should.
    Dreamweaver
    MX 2004
    Does anyone have any suggestions on how to resolve this issue
    or have a clue as to why this is happening? It's really one of the
    only bugs left preventing me from upgrading to DW 8 anymore.
    Thanks,
    - Paul

    After some tinkering around and a call to Tech. Support I
    eventually resolved this issue by pointing out a bug to Adobe.
    Apparently the problem is the View / Visual Aids / Invisible
    Elements option. If this is turned on, and you have a website set
    up similiarly to
    this one, you will
    experience this sporatic, extranenous white space that shifts your
    content around. It is not an issue in DW MX 2004, only DW 8.
    The solution is to just simply turn OFF the "Invisible
    Elements" option. Then the page will render the way it should.
    A bug report has been submitted.

  • Dreamweaver CS3 Design View messed up

    I'm not quite sure why, but the design view is all messed up
    when I am
    editing my webpage.
    Here is what it looks like.
    http://img257.imageshack.us/img257/4749/sammesseduphl2.jpg
    but as you can see by going here
    http://sdsusammys.com/rush.php
    that
    the page works perfectly.
    I was reading some of the other peoples posts and I noticed
    people who
    Include php files usually have this same problem.
    The beginning of the code for my rush.php page is as follows
    <?php
    include("includes/header.html");
    ?>
    <?php
    include("includes/navbar.php");
    ?>
    Would that have anything to do with it?
    Thanks

    Sammy,
    As for "viewing" your web page inside Dreamweaver, it is not
    a good idea. Dreamweaver is a basically a HTML editing application.
    Ideally speaking, best if you view your web page with any web
    brower. Also check with your web page with many browsers, where you
    will notice some beheavior or such difference in those two or many
    browsers. It depends on how you code your HTML code per se.
    Hope that helps.
    Cheers, Brian
    quote:
    Originally posted by:
    Sammy.BE
    I'm not quite sure why, but the design view is all messed up
    when I am
    editing my webpage.
    Here is what it looks like.
    http://img257.imageshack.us/img257/4749/sammesseduphl2.jpg
    but as you can see by going here
    http://sdsusammys.com/rush.php
    that
    the page works perfectly.
    I was reading some of the other peoples posts and I noticed
    people who
    Include php files usually have this same problem.
    The beginning of the code for my rush.php page is as follows
    <?php
    include("includes/header.html");
    ?>
    <?php
    include("includes/navbar.php");
    ?>
    Would that have anything to do with it?
    Thanks

Maybe you are looking for

  • PI 7.1 and Oracle JDBC driver: missing com.sap.aii.adapter.lib.sda

    Hello, I want to deploy the JDBC driver for Oracle databases as described in OSS 1138877 on a brand-new PI7.1 (SP06 Stack) installation. Unfortunately, I can't find com.sap.aii.adapter.lib.sda on the system, so I can't add the ojdbc14.jar file and de

  • How to change local file Permissions as a default

    I have a mavericks Imac with certian permissions on a folder. when users copy and paste the folder on a server for others to use, some users are not able to acess the files.I know how to change the permissions on the folder manually. But I want to kn

  • Outlook 2010 shared mailbox in cache mode not updating Inbox automatically

    I have a user who has XP on his desktop, running Outlook 2010, connecting to a Exchange 2010 w/SP2.  I recently added a shared mailbox for him to monitor. I did it the old way by adding additional mailbox to his client (outlook 2010) pc.. I understan

  • Java Servlet BUG (Possibly)-Servlet classname replaces retrieved doc name

    I created a test servlet (TestServlet.java) which reads data from a file which could be pdf/doc/xls/zip etc and presents the file to the user for download. When the user clicks on the save option to save the file the default name before the file exte

  • Call Stack Navigation

    Hi, I want to go navigate trough my call stack starting from the very top level like this: Runstate.Root.Runstate -> going down to where my execution is actually running ... How can I do this? Thanks,