Design View - Can't believe it's gone!

I have been using Flash Builder since it was Flex Builder. Actually, since flex was introduced. Once of the best features of Flash Builder over other IDE's was the ability to use a GUI to layout elements on the page. I just downloaded the trial version on Flash Builder 4.7 to see all of the new features and start playing with it, and that's when I noticed that there was NO Source/Design tabs. At first, I thought there must be a check mark somewhere to turn them on. After I could not find any settings that enabled the Design Veiw, I did a search on Google, and found out that it has been removed.
REALLY! OK. I have read peoples comments saying that if you are a Real programmer, you don't need it. Well, if I am a real driver, I really don't need leather seats and Air Conditioning either. The Design View was what set Flash Builder apart from other IDE's! And you got rid of it!?
Well, this is one developer who will not be upgrading to 4.7, when I could just use a free IDE to get the same results. Adobe, if you really care about your END USERS - The people that actually use your products, don;t change things that made your products what they are! When something works, don't fix it!
I can not imaging Flash Builder ever seeing a Version 5 if the Design View is not brought back.
So, hey... Adobe management - it's your lively hood because it's us developers that use your products that pay for your new releases that keep you in business. You have to show me why I should spend the $250 to upgrade when there are many FREE products out there that will now do everything that 4.7 will do. I just don't get it.
Thanks for listening, and I hope this comment is not just lost, forgotten or locked and displaced.
Ronnie
Online Innovations

I guess that when they set at the round table, and discussed what it would mean if they removed the Design View, they must have though... nevermind, I have no idea what they were thinking. All I know is, I love Adobe Products, I have purchased the CS suites since CS2, and I have been using Flex since it was introduced. Design View, however such a "small" part of the overall Flex concept, is a very important part. The concept was to have an environment that allowed you to write code (actionscript) and bundle that with a user interface (Flash) and build these applications quickly (RAD). Sure, Flash Builder will still allow you to develop the coding part quickly, but the Design View was the key that tied it all together, allowing you to create the backend (code) and the front end (user interface) quickly. I do not care that you are a fabulous coder that feels they are so good that they do not need a design view. I want it, and I am the one who is buying it.
So, I guess Adobe must have felt there where enough people that will still buy the 4.7 and beyond concept to keep it alive. I feel... it will not be me.
Adobe, I really like your products, But this is something that really needs to be re-thought. Who ever the person was that made the decision to get rid of this, you need to now make the decision to let them all go. Because they effectivaly killed Flex for many many people.
I hope you figure all of this out soon, because we will continue to use 4.6 for a little while. Then, we will start to change our development practices. Are you wanting to push people back to Flash Pro? Well, this may be the way we have to go and forget about Flex. I hope this will not be the case, but we will see.
Adobe can make the decision to not listen, and I can make the decision to not spend. Last I understood, they were in business to make products they can sell. So, I know I will still be here with my money, even if Flex falls to the side.

Similar Messages

  • Flash Builder - Design View - can't resize/move objects anymore.

      So, I've downloaded the 60 day trial of Flash Builder 4.  I've been working with it for about 2 days and everything has been going fine.  However, for some unknown reason, my design view panel just suddenly stopped working properly.  I see the components (and the gray outlines of my containers) I'm working with, but when I try to click on them, I do not get that blue resizing outline with the handles.  I see the properties panel change when I click different components, but I get no outline.  So, I can no longer resize in this view.  I also can't move components/containers around.  I can only click on them and watch the properties panel change.  I do not believe I've hit any sort of option in the menus.  I closed the application and started it up again with the same result.  I even rebooted my machine and tried again.  As of right now, this problem seems to be permanent.  Any ideas?  Thanks for your time.

    I would recommend you post on the Flash Builder forum: http://forums.adobe.com/community/flash_builder

  • Design View - Can't Select Text, Only Divs

    This is a page I did not build, and I hope I can describe this properly. Here's the published page -
    www.wheeltime.com
    I'm in CS4 and there are two things going on when trying to edit in design view. The first is I can't select text of content. Clicking to select said content, say a line of text or a word, selects and highlights the entire div container and all the content within in one big chunk. Why is DW not letting me select the actual content? This is the first time I've enver encountered this issue. 
    This is the same for all the div ontainers on the page. But another, perhaps related problem, has to do with this content area. In design view, there's a fixed height, so not only can I not select the content, but I can't see it all. It's OK in the browser, expands as it should. I've looked at all the properties anywhere and don't see any height attribute anywhere, especially those that enclose this area of content.
    One this that has be wondering - this content area is warpped in a "main-content" div, with a class applied. But this div has no corresponding entry or properties in the style sheet. I can see where a div can be used that has no specific properies of it's own, but is it OK to not be mentioned at all in the style sheet? And can this affect what's going on in design view editing?
    So, I guess the question is - what is governing this inability to edit in Design view?  Thank you in advance!!

    Have you tried double clicking the content?
    I'm not sure what causes this exactly, but I downloaded your page and ran it in my DWCS4. It did the same thing until I double clicked the content of the divs. That allowed me to select it without issue from that point on.
    It may have something to do with the content being wrapped in <span> tags within each <div>.
    Onto your other question, your <div id="main-container"class="container"> is being affected by the .container class in your style.css file rather than a #main-container id.
    EDIT: HTML id's like <div id="main-content"> serve to identify elements for many purposes, not just css. There is no problem with giving an element an id simply for organizational purposes, though usually they are used as targets for javascripts, css or php scripting purposes.

  • Can't believe it is gone

    It started with an iPhone..... then I saw Frontrow on an iMac...and I was convinced.
    I changed all PC's, network equipment in the house to Apple. Today we pretty much have everything from Apple - including software etc.
    I am a total IT gadget freak....so I write about this stuff and help hundreds of people to get better IT/media use in their homes.
    There is not one individual - who is not simply blown away - by the simplicity, ease of use and cool interface of AppleTV and Frontrow.
    Frontrow enables ordinary people to finally make use of all their media in an easy to use way.
    This is what makes a computer different from just a computer. It comes to life ... it brings life into your living room/kitchen or where you have it.
    MacMini/Frontrow/55" TV was what changed our family.... to finally having an easy way to enjoy recent photos, home videos, TV, movies etc.
    It made all my many years in the IT industry pay off....meaning I no longer needed to spend hours setting up, copying the specific film/photos to a specific place for us to enjoy together.
    Now it was as easy - as a click on a button.
    So the computer was no longer a computer.... it was something for people... it enriched our family's lives.... it came to life with pictures, private footage and all kinds of stuff.
    So this whole solution with iTunes containing all the media, iPhoto with the photos etc., MacMini, FrontRow and a TV is absolutely brilliant.
    Its no longer tech stuff, it no longer requires an IT guy (like me) to make it work.
    Its for ordinary people.....
    So why on earth did you remove it? and made Apple the same as any other PC supplier?
    Now - a mac no longer comes to life? Its just a pc with programs...
    No pictures, no footage, no audio - at a click of a button....
    I am so sad, frustrated and confused that Apple could remove their incredible advantage and key point of differentiation....
    What will the future bring ... ?

    To all of You who would like to get Front Row back... please send feedback to
    http://www.apple.com/feedback/
    or support me on my page
    http://www.facebook.com/pages/iWantFrontRowBack/115169858583709
    Regards,
    Martin

  • CSS style not rendering in design view

    I have style="max-width:600px" in a image but it wont show in design view on Dreamweaver CS4

    The parent file MUST be named with .shtml or .shtm as an extension.  It's that extension that tips the server off that the file contains server directives and that it should be parsed to find them (normally, fetched files are not parsed by the server).  Using these filename extensions will not affect the XHTML strict validation of the file (by the way, is there a reason for sticking with XHTML?).
    It is not necessary to have a testing server defined to see proper HTML includes rendered in Design view.  I believe that by renaming your file with the correct extension you will see this include expressed in Design view. It is a little unclear to me whether the correct syntax for a virtual include is to use the root slash or to omit it.  For example, Wikipedia says -
    The file parameter defines the included file as relative to the document path; the virtual parameter defines the included file as relative to the document root.
    Then later it says -
    The file parameter defines the included file as relative to the document path; the virtual parameter defines the included file as relative to the document root.
    There is, in fact, a big difference between these two statements!  From a personal point of view, I don't use HTML includes at all (always use PHP includes which are written differently).  But I think you can use the file include as I have shown safely - that's assuming that the two files are at the same level.

  • Design View Inaccuracy

    I have created a page in DW-CC which is completely disjointed in design view. It presents fine in live view and when previewed in the browser. It is more difficult to review and revise in this scattered form. I have to go to live view to see how the changes look on the page. Any thoughts?
    jaywwem

    Check you code for errors.  Design View can't tolerate them.  
    http://validator.w3.org/
    http://jigsaw.w3.org/css-validator/
    If the problem is not caused by code errors, just turn of your CSS. 
    Go to View > Style Rendering > Disable Styles. 
    This will not effect either LiveView or Preview in browsers. But it makes editing unstyled pages easier.
    Another option is to use a Design-Time style sheet.
    http://help.adobe.com/en_US/dreamweaver/cs/using/WScbb6b82af5544594822510a94ae8d65-7e17a.h tml
    Nancy O.

  • Getting user input in design view

    I need to get the user inputs in the design view. NOT in the runtime...
    (Say in the design view of NetBeans)
    how to do this?
    Say;
    I have UserControl with 2 textboxes.
    textbox1 for Name and textbox2 for Age.
    when i drag this usercontrol to the form(in form design view) i need to get the 2 inputs(Name and Age) and write them to a file...Is this possible

    User input in design view can only be entered via the properties of the input interface. Else it is impossible.

  • JSP Design View is gone

    I created a project and made some JSP pages successfully. Everything is working.
    When I started the Creator the second time, the design view of some of my JSP pages are gone. Theere's a grey panel for the design view.
    I checked the source view and it looks like the source is good and untouched.
    What's going on here? How can I recover the design view?
    thanks

    The dead designer is usually caused by problems (bugs) in the underlying subsystem that parses and models the source code. Take a look at the log file and if you have any interesting exceptions there, you can provide them here and we can take a look.
    One of the problems that was recently fixed for an EA update had to do with parsing arrays and array initializers. I am not sure when that update will be available, but, in the mean time, if you have arrays in your source, try commenting them out.
    Another problem that exists has to do with referencing types defined in your other sources. Try using fully-qualified classnames for those.
    I hope this helps.

  • How can I get back to editing in Design view?

    I can't edit my web pages in Design view. When I DON'T have Live View on, nor Live Code, I only get a cursor shaped like a NO circle and I cannot click on anything to edit it. I can only make changes in the code window.
    What can I do to restore editablilty in Design view?

    Sorry this has taken so long. I have been trying a few things. One is the fact my template my pages are all based on has an editable region, which is where the uneditable are is within.. Other editable areas in the template are available for me to click into and edit, but not the main area.
    I tried moving the main div inside the editable region, but then, although it is now editable, the main div gets wiped away when the site pages get updated. So then I am forced to go back to the previous situation.
    Link: http://www.revelantiron-ons.com/MainPage.html
    Code:
    <html><!-- InstanceBegin template="/Templates/PageLayout_Idea_Template.dwt" codeOutsideHTMLIsLocked="false" -->
    <head>
    <!-- InstanceBeginEditable name="doctitle" -->
    <title>Revelant Iron-Ons Home</title>
    <!-- InstanceEndEditable -->
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" > <meta name="keywords" content="christian t shirts, christian apparel, iron on transfer, iron-on transfer, transfers iron on, creation, creator, relevant, Christian, t-shirt, tshirt, iron on, iron-on, inspirational, political, conservative, pro-life, prolife, religious, religion, christian, bible, Jesus, Holy Spirit, spiritual, design, revelation">
    <meta name="description" content="A site for custom-designed Christian, religious, inspiriational, politically conservative iron-on designs. Unique Christian and inspirational iron-on transfer designs for you.">
    <link href="rio-styles.css" rel="stylesheet" type="text/css">
    <script type="text/javascript">
    <!--
    function MM_preloadImages() { //v3.0
      var d=document; if(d.images){ if(!d.MM_p) d.MM_p=new Array();
        var i,j=d.MM_p.length,a=MM_preloadImages.arguments; for(i=0; i<a.length; i++)
        if (a[i].indexOf("#")!=0){ d.MM_p[j]=new Image; d.MM_p[j++].src=a[i];}}
    function MM_findObj(n, d) { //v4.01
      var p,i,x;  if(!d) d=document; if((p=n.indexOf("?"))>0&&parent.frames.length) {
        d=parent.frames[n.substring(p+1)].document; n=n.substring(0,p);}
      if(!(x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms[i][n];
      for(i=0;!x&&d.layers&&i<d.layers.length;i++) x=MM_findObj(n,d.layers[i].document);
      if(!x && d.getElementById) x=d.getElementById(n); return x;
    function MM_nbGroup(event, grpName) { //v6.0
      var i,img,nbArr,args=MM_nbGroup.arguments;
      if (event == "init" && args.length > 2) {
        if ((img = MM_findObj(args[2])) != null && !img.MM_init) {
          img.MM_init = true; img.MM_up = args[3]; img.MM_dn = img.src;
          if ((nbArr = document[grpName]) == null) nbArr = document[grpName] = new Array();
          nbArr[nbArr.length] = img;
          for (i=4; i < args.length-1; i+=2) if ((img = MM_findObj(args[i])) != null) {
            if (!img.MM_up) img.MM_up = img.src;
            img.src = img.MM_dn = args[i+1];
            nbArr[nbArr.length] = img;
      } else if (event == "over") {
        document.MM_nbOver = nbArr = new Array();
        for (i=1; i < args.length-1; i+=3) if ((img = MM_findObj(args[i])) != null) {
          if (!img.MM_up) img.MM_up = img.src;
          img.src = (img.MM_dn && args[i+2]) ? args[i+2] : ((args[i+1])? args[i+1] : img.MM_up);
          nbArr[nbArr.length] = img;
      } else if (event == "out" ) {
        for (i=0; i < document.MM_nbOver.length; i++) {
          img = document.MM_nbOver[i]; img.src = (img.MM_dn) ? img.MM_dn : img.MM_up; }
      } else if (event == "down") {
        nbArr = document[grpName];
        if (nbArr)
          for (i=0; i < nbArr.length; i++) { img=nbArr[i]; img.src = img.MM_up; img.MM_dn = 0; }
        document[grpName] = nbArr = new Array();
        for (i=2; i < args.length-1; i+=2) if ((img = MM_findObj(args[i])) != null) {
          if (!img.MM_up) img.MM_up = img.src;
          img.src = img.MM_dn = (args[i+1])? args[i+1] : img.MM_up;
          nbArr[nbArr.length] = img;
    //-->
    </script>
    <!-- InstanceBeginEditable name="head" -->
    <script type="text/javascript">
    <!--
    function MM_swapImgRestore() { //v3.0
      var i,x,a=document.MM_sr; for(i=0;a&&i<a.length&&(x=a[i])&&x.oSrc;i++) x.src=x.oSrc;
    function MM_swapImage() { //v3.0
      var i,j=0,x,a=MM_swapImage.arguments; document.MM_sr=new Array; for(i=0;i<(a.length-2);i+=3)
       if ((x=MM_findObj(a[i]))!=null){document.MM_sr[j++]=x; if(!x.oSrc) x.oSrc=x.src; x.src=a[i+2];}
    //-->
    </script>
    <!-- InstanceEndEditable -->
    </head>
    <body   class="body" onLoad="MM_preloadImages('images/NavRllvr1.jpg','images/NavRllvr2.jpg','images/NavRllvr3. jpg','images/NavRllvr4.jpg','images/NavRllvr5.jpg','images/NavRllvr6.jpg','images/RIO_NavU p1.jpg','images/RIO_NavUp2.jpg','images/RIO_NavUp3.jpg','images/RIO_NavUp4.jpg','images/RI O_NavUp5.jpg','images/RIO_NavUp6.jpg','images/BuyBttn_sml_ovr.jpg')">
    <div id="container">
    <div id="adspace">
      <!-- InstanceBeginEditable name="AdSpaceRegion" --><img src="../images/AlsoFollowbar.jpg" id="followbox"  alt="Also follow Revelant Iron-Ons at these locations" width="857" height="43" hspace="59" vspace="0" border="0" usemap="#Map">
      <map name="Map">
        <area shape="rect" coords="640,2,712,48" href="http://www.cafepress.com/RevelantIronOnsCP" target="_blank" alt="Revelant Iron-Ons at CafePress">
        <area shape="rect" coords="487,4,616,40" href="http://www.zazzle.com/revelant" target="_blank" alt="Revelant Iron-Ons at Zazzle.com">
    <area shape="rect" coords="792,1,848,42" href="http://twitter.com/RevelantIronOns" target="_blank" alt="Revelant Iron-Ons Twitter page">
        <area shape="rect" coords="727,2,787,45" href="http://www.facebook.com/profile.php?id=100002412534139&sk=wall" target="_blank" alt="Revelant Iron-ons Facebook page">
      </map><!-- InstanceEndEditable --></div>
    <div id="leftside"></div><div id="rightside"></div><div id="centercore">
        <div id="header"><img src="images/RIO_Masthead-left.jpg" width="448" height="109" alt="Revelant Iron-Ons logo"><img src="images/RIO_Masthead-Right.jpg" width="448" height="109" alt="Inspirational Iron-On Designs"></div>
        <div id="navbar">
          <div id="navbuttonlineup"><a href="MainPage.html" target="_top" onClick="MM_nbGroup('down','group1','Home_bttn','../images/NavRllvr1.jpg',1)" onMouseOver="MM_nbGroup('over','Home_bttn','../images/NavRllvr1.jpg','../images/RIO_NavUp 1.jpg',1)" onMouseOut="MM_nbGroup('out')"><img src="images/RIO_NavUp1.jpg" alt="Home" name="Home_bttn" width="150" height="28" border="0" onload=""></a><a href="designs.html" target="_top" onClick="MM_nbGroup('down','group1','Designs_bttn','../images/NavRllvr2.jpg',1)" onMouseOver="MM_nbGroup('over','Designs_bttn','../images/NavRllvr2.jpg','../images/RIO_Na vUp2.jpg',1)" onMouseOut="MM_nbGroup('out')"><img src="images/RIO_NavUp2.jpg" alt="Designs" name="Designs_bttn" width="150" height="28" border="0" onload=""></a><a href="news.html" target="_top" onClick="MM_nbGroup('down','group1','News_bttn','../images/NavRllvr3.jpg',1)" onMouseOver="MM_nbGroup('over','News_bttn','../images/NavRllvr3.jpg','../images/RIO_NavUp 3.jpg',1)" onMouseOut="MM_nbGroup('out')"><img src="images/RIO_NavUp3.jpg" alt="News" name="News_bttn" width="150" height="28" border="0" onload=""></a><a href="articles.html" target="_top" onClick="MM_nbGroup('down','group1','Articles_bttn','../images/NavRllvr4.jpg',1)" onMouseOver="MM_nbGroup('over','Articles_bttn','../images/NavRllvr4.jpg','../images/RIO_N avUp4.jpg',1)" onMouseOut="MM_nbGroup('out')"><img src="images/RIO_NavUp4.jpg" alt="Articles" name="Articles_bttn" width="150" height="28" border="0" onload=""></a><a href="instructions.html" target="_top" onClick="MM_nbGroup('down','group1','instruct_bttn','../images/NavRllvr5.jpg',1)" onMouseOver="MM_nbGroup('over','instruct_bttn','../images/NavRllvr5.jpg','../images/RIO_N avUp5.jpg',1)" onMouseOut="MM_nbGroup('out')"><img src="images/RIO_NavUp5.jpg" alt="Instructions" name="instruct_bttn" width="150" height="28" border="0" onload=""></a><a href="contactform.html" target="_top" onClick="MM_nbGroup('down','group1','About_bttn','../images/NavRllvr6.jpg',1)" onMouseOver="MM_nbGroup('over','About_bttn','../images/NavRllvr6.jpg','../images/RIO_NavU p6.jpg',1)" onMouseOut="MM_nbGroup('out')"><img src="images/RIO_NavUp6.jpg" alt="Contact Us" name="About_bttn" width="146" height="28" border="0" onload=""></a></div>
          <div id="mainContent"><!-- InstanceBeginEditable name="ContentRegion" -->
            <div id="mainblurb" class="RIO_basic">
            <div id="quickquip" ><p class="RIO_smaller">Keep on top of new designs and other important information. <a href="http://revelantiron-ons.com/letsshop/index.php?main_page=login">Click here</a> to sign up for our newsletter.<a href="http://revelantiron-ons.com/letsshop/index.php?main_page=login"><img src="/images/nwslttr_choose_shot.jpg" alt="choose our newsletter section of registration form" width="190" height="67" vspace="6" border="0"></a> </p>
          </div>
          <div id="quickquip" ><p class="RIO_smaller">Have  questions about Revelant Iron-Ons iron-on transfers? <a href="FAQ.html">Look up our FAQ page</a>.</p>
          </div>
          <div class="clearfloat"></div>
                        <p class="RIO_HeadlineK">God&rsquo;s Cool Creation!          </p>
              <p>This is sure to become popular very quickly. God&rsquo;s Cool Creation displays a wonderful arrangement of images and illustrations glorifying God in His handiwork of Earth&rsquo;s creation.</p>
    <p><img src="/images/designs/proxies/CC_proxy_150w.png" width="150" height="126" alt="God's Cool Creation iron-on design"></p>
    <p>Take a look at this design, <a href="http://revelantiron-ons.com/letsshop/index.php?main_page=product_info&cPath=1&products_id= 7&zenid=217315476d30c2abb2e57d53bcbadb97"><span class="linkK">order it today</span></a>, and get ready to hear your friends ooh and aah over it!</p>
              <p class="RIO_HeadlineK"><a href="news.html#SpecialOffer" class="linkK">A Special Introductory Offer<br>
                for first-time orders!</a></p>
              <p class="RIO_HeadlineK">Welcome to Revelant Iron-Ons.</p>
              <p class="RIO_SubK">Iron-On Designs that Say What You Want to Say</p>
              <p>We are happy to present to you some of the most relevant, eye-catching and unique Christian, inspirational iron-on designs available on the web. This is our aim, and as we grow, we believe you will find this to be true.</p>
              <p>As this site is new, we currently have only a few designs. However, many new designs are in the works. The Bible asks, &ldquo;Who despises the day of small things?&rdquo; Well, not us! We thankfully rejoice that we can start offering you specially made iron-ons in a small way now and grow to more designs later.</p>
              <p class="RIO_SubK">A DIY Approach</p>
              <p>Our purpose is to provide you with great iron-on designs, and impactful messages, printed with Epson&rsquo;s premium  DURABrite<span class="Superscript">&reg;</span> Ultra ink, on quality iron-on transfer material. You supply the garment and the iron, follow our special instructions, and end up with a fantastic iron-on you can enjoy wearing for years.</p>
              <p>Please view our designs, order what you like, and also read any important news and articles about each offering. </p>
            <div id="duraBriteBlurb"><img name="durabriteimage" src="images/DURABrite_logo_8bt.png" width="120" height="65" alt="DURABrite Ultra Ink logo"></div>
            </div><p class="RIO_basic"><br>
            Click on any design to see more!<br>
            <br>
            <a href="/letsshop/index.php" onMouseOut="MM_swapImgRestore()" onMouseOver="MM_swapImage('buybttn_sml','','images/BuyBttn_sml_ovr.jpg',1)"><img src="images/BuyBttn_sml_up.jpg" alt="Buy now!" name="buybttn_sml" width="116" height="30" border="0"></a>        </p>
            <div id="pictscolumn">
                      <p class="RIO_caption"><a href="designs.html"><img src="images/designs/T-Shirt_Proxy_CoolC.png" width="162" height="165" alt="Cool Creation T-shirt" border="0" align="top"></a><br>
    God&rsquo;s Cool Creation</p>
              <p class="RIO_caption"><a href="designs.html"><img src="images/designs/T-Shirt_Proxy_ATS.png" width="162" height="165" alt="Able To Save T-shirt" border="0" align="top"></a><br>
    Able to Save</p>
    <p class="RIO_caption"><a href="designs.html"><img src="images/designs/T-Shirt_Proxy_answr.png" width="162" height="165" alt="the answers T-shirt" border="0" align="top"></a><br>
    the answers</p>
               <p class="RIO_caption"><a href="designs.html"><img src="images/designs/proxies/Shirt_Proxy_FOSS.png" alt="Fruit of the Spirit Spots T-shirt" width="162" height="165" border="0"></a><br>
              Fruit of the Spirit Spots</p>
              <p class="RIO_caption"><a href="designs.html"><img src="images/designs/proxies/Shirt_Proxy_Endrs.png" alt="Endorse does not Establish T-shirt" width="162" height="165" border="0"></a><br>
              Endorse does not Establish</p>
              <p class="RIO_caption"><a href="designs.html"><img src="images/designs/T-Shirt_Proxy_WrngChc.png" alt="Fruit of the Spirit Spots T-shirt" width="162" height="165" border="0"></a><br>
              The Wrong Choice</p>
           </div>
          <!-- InstanceEndEditable --></div></div>
      </div>
    <div class="clearfloat"></div>
      <div id="footer"><p class="foottype">&copy; 2011 RightStar Computing<br>
      Revelant Iron-Ons is a brand of RightStar Computing.  123 Hedman Lane, Monticello, Minnesota 55362<br>
      <a href="MainPage.html" class="link">Home</a> | <a href="designs.html"  class="link">Designs</a> | <a href="news.html"  class="link">News</a> | <a href="articles.html"  class="link">Articles</a> | <a href="instructions.html"  class="link">Iron-On Instructions</a> | <a href="contact.html"  class="link">Contact Us | </a><a href="letsshop/index.php" class="link">Buy Now!</a></p><!--footer info will go here, such as copyright, etc. --></div>
    </div><!--end container area -->
    </body>
    <!-- InstanceEnd --></html>
    CSS:
    @charset "UTF-8";
    .body  {
              text-align: center; /* this centers the container in IE 5* browsers. The text is then set to the left aligned default in the #container selector */
              background-color: #514444;
              font-family: Verdana, Arial, Helvetica, sans-serif;
              font-size: 100%;
              margin: 0px;
              padding: 0px;
              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;
    .RIO_basic {
              font-family: Verdana, Arial, Helvetica, sans-serif;
              font-size: 100%;
              font-style: normal;
              line-height: 120%;
              font-weight: normal;
              font-variant: normal;
              color: #000000;
              text-decoration: none;
              white-space: normal;
              margin-left:0 em;
              margin-right:1.5em;
              margin-top:0.5em;
    .RIO_smaller  {
              font-family: Verdana, Arial, Helvetica, sans-serif;
              font-size: 85%;
              font-style: normal;
              line-height: 120%;
              font-weight: normal;
              font-variant: normal;
              color: #000000;
              text-decoration: none;
              white-space: normal;
              margin-left:0 em;
              margin-right:1.5em;
              margin-top:0.5em;
    .RIO_showtitle {
    font-family:  Verdana, Arial, Helvetica, sans-serif;
    color:          #000;
    font-size: 85%;
    font-weight:bold;
    margin-top:0px;
    margin-bottom: 4px;
    text-decoration:none;
    .RIO_caption {
              font-family: Verdana, Arial, Helvetica, sans-serif;
              font-size: 70%;
              --font-style:italic;
              color:#000;
              margin-top:.25em;
              margin-bottom:1em;
              text-decoration:none;
    .RIO_basicK {
              font-family: Verdana, Arial, Helvetica, sans-serif;
              font-size: 100%;
              font-style: normal;
              line-height: 120%;
              font-weight: normal;
              font-variant: normal;
              color: #000000;
              text-decoration: none;
              white-space: normal;
    .RIO_HeadlineK {
              font-family: Verdana, Arial, Helvetica, sans-serif;
              font-size: 120%;
              font-style: normal;
              line-height: 120%;
              font-weight: bold;
              font-variant: normal;
              color: #000000;
              text-decoration: none;
              white-space: normal;
              text-align: center;
              margin-top:1em;
    .RIO_HeadlineK-left {
              font-family: Verdana, Arial, Helvetica, sans-serif;
              font-size: 120%;
              font-style: normal;
              line-height: 120%;
              font-weight: bold;
              font-variant: normal;
              color: #000000;
              text-decoration: none;
              white-space: normal;
              text-align: left;
              margin-top:1em;
    .newsdate {
    color: #cead33;
    font-weight: bold;
    font-size: 85%;
    text-decoration:underline;
    margin-top:0.125em;
    .RIO_SubK {
              font-family: Verdana, Arial, Helvetica, sans-serif;
              font-size: 110%;
              font-style: normal;
              line-height: 120%;
              font-weight: bold;
              font-variant: normal;
              color: #000000;
              text-decoration: none;
              white-space: normal;
              text-align: left;
              margin-left:0em;
              margin-right:0.5em;
              margin-top:0.75em;
    .Superscript {
              font-size: x-small;
    .link {
              font-family: Verdana, Arial, Helvetica, sans-serif;
              color: #FFFFFF;
              text-decoration: none;
              --text-indent: 2em;
              white-space: normal;
              --text-decoration: underline;
    .linkK {
              font-family: Verdana, Arial, Helvetica, sans-serif;
              color: #000000;
              text-decoration: none;
              --text-indent: 2em;
              white-space: normal;
              text-decoration: underline;
    .linkhover {
              color: #ffe050;
              text-decoration: none;
              --text-indent: 2em;
              white-space: normal;
              --text-decoration: underline;
    .foottype {
              font-family: Verdana, Arial, Helvetica, sans-serif;
              font-size: 65%;
              color: #FFF;
              font-weight:lighter;
              text-align:center;
              line-height:160%;
              text-decoration: none;
    .caption {
              font-family: Verdana, Arial, Helvetica, sans-serif;
              font-size: .75em;
              color: #000F;
              font-weight:lighter;
              text-align:center;
              line-height:160%;
              text-decoration: none;
    .background {
              background-attachment: fixed;
              background-image: url(images/RVLT_Bkgrd_2000h.jpg);
              background-repeat: no-repeat;
              background-position: left top;
    #container {
              width:970px;
              text-align: left;
              height: 900px;
              padding: 0px;
              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;
              margin-top: 0;
              margin-right: auto;
              margin-bottom: 0;
              margin-left: auto;
    #buttonspace {
    width:180px;
    height:auto;
    margin-right: 10px;
    margin-bottom: 6px;
    padding-left: 5px;
    padding-bottom: 5px;
    background-color:#f8cf35;
    text-align:left;
    float: left;
    border-radius:6px;
    -moz-box-shadow: 3px 3px 5px rgba(0,0,0, .5);
    box-shadow: 3px 3px 5px rgba(0,0,0, .5);
    .buttontext {
              margin:0px;
              text-decoration:none;
              font-size:80%;
    #centercore {
              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;
              margin-top: 0px;
              margin-right: 0px;
              margin-bottom: 0px;
              margin-left: 0px;
              position: relative;
              padding-top: 0px;
              padding-right: 0px;
              padding-bottom: 0px;
              padding-left: 37px;
    #followbox {
              margin-top:46px;
              margin-bottom:0px;
    #adspace {
              background-image: url(images/RIO_Adspace.jpg);
              background-repeat: no-repeat;
              background-position: 0px 0px;
              margin: 0px;
              height: 100px;
              width: 970px;
              padding:  0px;
              --clip: rect(auto,auto,auto,auto);
              position: relative;
              clear: both;
    #header {
              height: auto;
              width:auto;
              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;
              margin: 0px;
              padding: 0;
    #leftside {
              background-image: url(images/RIO_LeftSide.jpg);
              background-repeat: no-repeat;
              float: left;
              width: 37px;
              background-position: top;
              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;
              margin: 0px;
              padding: 0px;
              height: 700px;
              position: inherit;
              left: 0px;
              top: 100px;
    #rightside {
              background-image: url(images/RIO_RightSide.jpg);
              background-repeat: no-repeat;
              margin: 0px;
              float: right;
              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;
              width: 37px;
              height: 700px;
              background-position: top;
    #mainblurb {
              float: left;
              width: 500px;
              margin-top: 20px;
              margin-right: 10px;
              margin-bottom: 15px;
              margin-left: 20px;
              padding-right:15px;
              overflow: auto;
              height: 485px;
              padding:0px, 0px, 0px, 0px;
    #pictscolumn {
              float: right;
              width: 230px;
              height:380;
              margin-top: 15px;
              margin-right: 50px;
              margin-bottom: 15px;
              margin-left: 0px;
              overflow: auto;
              padding:0px;
    #navbar {
              height: 71px;
              width: 896px;
              background-image: url(images/RIO_NavBarBkgd.jpg);
              background-repeat:no-repeat;
              background-position: top;
              margin: 0px;
              padding: 0;
              position: absolute;
              top: 109px;
    #navbuttonlineup {
              height: 28px;
              padding-top:43px;
              width: 896px;
              margin-right: 0px;
              margin-bottom: 0px;
              margin-left: 0px;
              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;
              position: relative;
              z-index: 80;
              margin-top: 0px;
              padding-right: 0px;
              padding-bottom: 0px;
              padding-left: 0px;
    #mainContent {
              margin: 0; /* the right margin can be given in percentages or pixels. It creates the space down the right side of the page. */
              background-image: url(images/RIO_ContentBkgrd.jpg);
              background-repeat: no-repeat;
              height: 520px;
              width: 896px;
              position: relative;
              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;
              top: 0px;
              background-position: left top;
              padding-top: 10px;
              padding-right: 37px;
              padding-bottom: 0px;
              padding-left: 37px;
                        overflow: auto;
    #quickquip  {
              width: 205px;
              padding-left:6px;
              padding-right:6px;
              margin:6px;
              background-color:rgba(248, 207, 53, .85);
              border-radius:6px;
    float:left;
    #showbox  {
              width: 268px;
              height: 268px;
              background-color:rgba(255, 255, 255, .7);
              border-radius:8px;
              text-align:center;
              float:left;
              padding-top:8px;
              margin:4px;
    #duraBriteBlurb {
              padding: 10px;
              float: right;
              height: 70px;
              width: 125px;
              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;
              z-index: auto;
    table {
    margin-left: 20px;
    margin-right: 20px;
    border: thin solid black;
    caption-side: bottom;
    border-spacing:0px;
    border-collapse: collapse;
    td, th {
    border: thin dotted gray;
    padding: 5px;
    th {
    background-color:#cc6600;
    table table th {
    background-color:white;
    caption {
    font-style: italic;
    padding-top: 8px;
    font-size: 80%;
    .cellshirt {
    width:180px;
    .cellcolor {
    background-color:#fcba7a;
    .centered {
    text-align: center;
    .right  {
    text-align: right;
    #footer {
              padding: 0,0,0,0;
              width:970px;
              background-image: url(images/RIO_Footer.jpg);
              background-repeat: no-repeat;
              height: 100px;
              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;
              position: relative;
              clear: both;
              float:left;
              background-position: 0px 0px;
              margin: 0px;
              top: 0px;
    /* Tips for mainContent:
    1. The space between the mainContent and sidebar1 is created with the left margin on the mainContent div.  No matter how much content the sidebar1 div contains, the column space will remain. You can remove this left margin if you want the #mainContent div's text to fill the #sidebar1 space when the content in #sidebar1 ends.
    2. Be aware it is possible to cause float drop (the dropping of the non-floated mainContent area below the sidebar) if an element wider than it can contain is placed within the mainContent div. WIth a hybrid layout (percentage-based overall width with em-based sidebar), it may not be possible to calculate the exact width available. If the user's text size is larger than average, you will have a wider sidebar div and thus, less room in the mainContent div. You should be aware of this limitation - especially if the client is adding content with Contribute.
    3. In the Internet Explorer Conditional Comment below, the zoom property is used to give the mainContent "hasLayout." This may help avoid several IE-specific bugs.
    /* Miscellaneous classes for reuse */
    .fltrt { /* this class can be used to float an element right in your page. The floated element must precede the element it should be next to on the page. */
              float: right;
              margin-left: 8px;
    .fltlft { /* this class can be used to float an element left in your page */
              float: left;
              margin-right: 8px;
              azimuth:center-left
    .clearfloat { /* this class should be placed on a div or break element and should be the final element before the close of a container that should fully contain a float */
              clear:both;
        height:0;
        font-size: 1px;
        line-height: 0px;
    [if IE]>
    <style type="text/css">
    /* place css fixes for all versions of IE in this conditional comment */
    #navbar, #header, #mainContent, #container, navbuttonlineup, #centercore, #leftside, #rightside, #adspace, #mainblurb, #pictscolumn {zoom: 1;}
    #header {
              top:0px;
              position:absolute;
    /* the above proprietary zoom property gives IE the hasLayout it needs to avoid several bugs */
    </style>
    <![endif]
    If you have any solution, I would greatly appreciate it!

  • Why can't I see my template in Design view as it is?

    Hi Guys
    A couple of days ago I noticed that my template which I use for my website, doesn't show correctly while working in design view. Quite annoying since I now constantly have to save all and view in Chrome or Firefox or...
    Does anyone know how I can make my template show again as it should be?
    See my website here: http://www.bmgraphics.be
    And see the difference of the template layout on this print screen of design view:

    Hi Nancy
    I don't think that this still is a problem. Otherwise I guess, with my few experience, I would have already gone totally mad...
    At the moment it seems as if there is a source code separate from the CSS stylesheet which used to be in only one stylesheet so.
    I downloaded the template together with the stylesheet etc. and it didn't cause any problems until I started combining styles off course
    Btw, Jon, the validator really did it I guess! It seems as if there were some mistakes which are now solved and it looks better now
    Thanks!

  • Can not see two fields in Crystal 2008 Developer explorer/designer view

    I am currently developing crystal 2008 reports against the salesforce.com database using version 12.0.0.683 CR Developer Full version. I am using an updated driver that was provided in July or Aug 08 in order to view self referencing fields. The problem is that when I try and report against one of the tables (lead history) I cannot view two of the fields (New Value and Old Value)? I can see these two field (New Value and Old Value) in the database expert as the last two fields in the actual table, but the two fields are missing when I go into the explorer/designer view. In Salesforce, these two fields can not be filtered on, but I can export all the values in this table using Salesforece Apex data loader.

    Please re-post if this is still an issue to the OnDemand Forum or purchase a case and have a dedicated support engineer work with you directly

  • Can not see the design view nor the java file in CentOS

    Hi all. I've recently installed JSC2 in CentOS. I find this tool really useful. But I have a problem with the design view and the java file view. At the beginning, when I first create a Page1.jsp, I can see the design view and the java view with no problem. I run apps correctly. But after a while, I get a "null pointer exception" error and I am able to see only the jsp view, not the others. I don't even have the option to see the Design and Java views. And the page icon in the project window appears to be darker than a well working page. I'm not really sure what sequence of actions I do to get this error, it just suddenly happens. What I've done so far in JSC2 is to link to pages in the Page Navigation view. It works fine for a while, but after a while I get the error I've described.

    Yes, if I do that It happens the same. I've tried everything. Now I'm using Window$ 2000 and it works properly. Thanks anyway.

  • How come I can see my div in design view but not in live view

    Hi,
    I have a div ID called "portfolio" that I can see in design view but not live view or on a browser. It's a little pink square and I want that square round also.
    I ran it through validator. It picked up some things in the style.css which I changed and the boilerplate.css that I did not. Because I thought DW auto creates code for boilerplate because I don't enter that code myself.
    It's also rejecting a lot of webkit code but this seems like standard webkit code that works elsewhere on the page.
    BTW: at what point does this brutal hand coding pay off in money and less heartache when Wordpress looks cleaner and is so much easier to use? I feel like I barely know HTML or CSS in terms of translating vision to reality and with all-browser functionality after months and months of on-line classes. How long are the pros at it till they reach a watershed point?
    here's my address: http://www.adjacentdimensionsmedia.com/home.html
    Here's my html:
    <body>
      <div class="gridContainer clearfix">
        <div id="div1" class="fluid"><img src="adtitle2.png" width="700" height="80" alt=""/></div>
      <div class="fluid"><div class="box-shad"><a href="index.html"></a></div>
      </div>
        <div id="portfolio">Portfolio</div>
    </body>
    Here's my CSS:
    .box-shad {
      margin-top: 200px;
      margin-left: 100px;
      width: 900px;
      height: 700px;
      display: block;
      background-image: url("images/Big-tree-trans1.png");
      background-size: 900px 700px;
      -webkit-box-shadow: 15px 15px 15px #000000 inset;
      box-shadow: 15px 15px 15px #000000 inset;
      -webkit-border-radius: 50%;
      border-radius: 50%;
      position: fixed;
    .box-shad a {
        display:block;
        width:900px;
        height:700px;
    #portfolio {
      width: 100px;
      height: 100px;
      margin-top: 0px;
      margin-right: 200px;
      margin-left: 200px;
      margin-bottom: 0px;
      border-radius: 75%;
      -webkit-border-radius: 75% 75%;
      background: pink;
      top: -300px;
      position: relative;

    The top:-300 is putting that div above the top of the browser viewport. Fix that and you'll see the div.

  • Can't see design view after changing connections file from localhost to a remote host & back again

    I was using localhost to test files before changing the connections document over to a remote host, since I couldn't get dreamweaver to connect to the remote host, I changed back to localhot. My files are all .php files. This is a dynamic site. After I changed my connection back to my local host my design view no longer works. It's competly grey with 3 small icons at the top on the left. I can view in live view and I can view in the browser. But no longer in design view after being able to for 6 months. The 3 icons are a hard drive case, a document, and a link symbol . When I click in code view the design view turns grey when I click in design view it turns white. I am using wamp for the localhost, Windows XP home, Dreamweaver CS5. Can someone please tell me how to go back to design view. This happens with any & all files including non dynamic .html files. Also having a problem connecting to my remote host. using godaddy, and they have tried with me for 2 hours to connect, I just keep getting password is incorrect. Thank you for any help, Stacey

    I would also recommend clearing the Site cache, which may help with the connection failure. To do so, choose Site > Advanced > Recreate Site Cache.
    After doing so, be sure to go back into your Site Setup, and make sure the FTP address, user name, and password are all correct. (Click the Test button in there to verify.)
    If that doesn't help with getting connected to your server, you might try an alternate FTP client (e.g. FileZilla) to just make sure you are entering the right connection information. It could be that GoDaddy is having some issue, or maybe you just mistyped something (I know I do this often when I type too fast).
    As for the issue with Design View, try clearing the Dreamweaver cache. Instructions are here: http://forums.adobe.com/thread/494811
    You might also try toggling the location of Design View. That is, when in Split View, choose View > Design View On Left. Then, choose that menu option again to reset the location back to the right.
    Resetting the workspace might also be recommended. Window > Worksapce Layout > Reset 'name of current workspace'

  • Can't see my page in design view, usind split screen

    Hi everyone, I am new to these forums and new to dreamweaver,
    I have a problem which I have no idea how to fix.
    I have been using the program (in my limited ability) saved
    my work, then when I opened it today, I have no design view in Code
    and Design view. The top part is fine but all I have is lots of
    lines at the bottom.
    The actual website seems fine, but just means I can't make
    any changes other than in code view, which I a not skilled enough
    to do.
    Please help.
    Regards
    Hypnoman

    There are a lot of problems with this page!!
    You will need to clean up your code! You have invalidly
    nested tags, empty tags, unclosed tags!
    If you would like a quote to clean up this page, send me a
    message!

Maybe you are looking for

  • Has anyone else noticed a slowdown in programs loading since update to 5.1.2??

    Since the last snow leopard update to 5.1.2 I have notice everything loading at a much slower rate. Even on shutdown or sleep things are much slower than prior to this update. Nothing else has been changed, added or deleted other than the update. Any

  • When I retrieve returnpack from customer, stock type should be blocked

    Hello, When I retrieve returnpack from customer, I want stock type should be blocked. When I use standart movement type 622, stock type is unrestricted use. Are there any way for this? I couldn't find any movement type which retrieve returnpack stock

  • How to eliminate status bar icon?

    I used an app named LogMeIn for a short while, then deleted it from my Mac using AppCleaner.  The icon for LogMeIn, however, still appears as a grayed-out icon in the menu bar.  I tried to remove it using Command-Click to drag it off the menu bar, bu

  • LabVIEW for Mac

    My boss has purchase two mini-Macs for my serial interface instruments. I'm a PC-girl and totally new to Mac so I wonder if the same LabVIEW license will do or if we need to get a new (Penn State University)? Since the Macs don't have a serial port I

  • Since I installed Mountain Lion, my i-phone, i-pad and desk top do not sync through i-cloud?

    I need changes to calendars to post to all devices immediately, and this is not happening.  I have everything turned on with i-cloud and plenty of storage space available.