Design View Collapse - How do you un-do?

Hello! I hope you can help! Some how my Design view only shows my header image and footer image, and all else is invisible. I know the page HTML is there as I can see all the code in the Code view, but does not show in Design view.
I have not had this happen before, and figure I accidently hit a wrong button... Any ideas???
Thank you :-)
~ Stephen

Hey there Nancy,
I appreciate your help! That didn't seem to do it, and I don't want to take your time for free.
Do you think we could do a screen share, and I could pay you for your time in advance? I use http://www.crossloop.com/ and that works really well. I've got to make some (non urgent) edits on that page, and it might be best just to get good help right off the bat than for me to tinker with it...
Let me know...
Stephen H. Jones
Atlanta: 770.601.0949
Seattle: 206.601.2821
Date: Mon, 1 Nov 2010 16:10:29 -0600
From: [email protected]
To: [email protected]
Subject: Design View Collapse - How do you un-do?
Hi Stephen,
You have some code validation errors on your page that need attention.
http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.growthstrategies.us%2Fsocial_ media_marketing_programs.html
Most notably, you're missing a valid document type (DTD) on the top your HTML pages. This omission puts your pages into Quirks Mode which can produce unwelcome surprises.
To fix this in DW, go to Modify > Page Properties > Title/Encoding. Select a document type that fits your coding skills. I recommend HTML transitional.
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
http://alt-web.com/
http://twitter.com/altweb
>

Similar Messages

Why hasn't the tutorial been updated to reflect 4.7's lack of a Design View?

This series uses version 4.5 which is no longer available. It frequently mentions the DESIGN VIEW and how easy it is to use, yet there is NO design view (nor is there a Components tab on the lower left box) in current version 4.7. Not only that, but the code used in several of the first day examples is not valid in Flash Builder 4.7 / Flash Player 11 and the browser refuses to show those examples (btw: most of the examples still work in 4.7). There are now ActionScript related errors in the examples that demonstrated Design View. You've had 2 years to fix this...
It seems that you might be shooting yourself in the foot here by:
1. Not giving new users who want to learn how to work in this environment current information (or at least linbking to new information). This is NOT a way to encourage new customers!
2. Not showing any work around options - such as linking to Dreamweaver, Illustrator or Flash Pro in some way? or updating the tutorial and showing how to create the components in the code view?
3. Marketing? Standards? groups within the company need to anticipate and develop fixes BEFORE making such drastic changes - this has NOT been done and it reflects poorly on the product (which is actually pretty cool)!
What is the alternative?
Aren't there other tools in CC that can be integrated in some already well defined way? i.e. I can edit a menu in Encore by selecting "edit in Photoshop". Why can't something like this be available?
I realize that this is one of Adobe's evolutionary mashup products (ie. Flash uses the timeline that originated in Director, Premiere & AfterEffects use tools acquired from CultEffects and AutoMasker, etc.) so there are many behind the scenes licensing issues that have determined the product evolution (and the products occasionally evolve in unexpected ways) - but it seems a bit contrarian to remove useful features without providing workarounds that users will think are BETTER than the old way!

Why complicate yourself? Adobe has almost pulled itself off from enterprise level flex delevopment to create new HTML5 tooling.
They will not pay to upgrade a training that is on the verge of getting unsupported. Just satisfy your training needs with other resources, such as lynda.com, pluralsight, etc.
Always remember, we are talking about capitalist companies here, if its not done for profit, then its not possible.

Design View

Hello.
In Dreamweaver CS 4 "Design" View have some errors.
In screenshots
orange squere - Firefox;
green squere - Dreamweaver
First screenshoot:
Backround color: none
Backround image repeat-x
Problem: Below backround image there is light braun. In Firefox everything is normal.
CLICK ON IMAGE TO ZOOM
Second problem:
I have on the table top one row that is 5px hight. O both sides I have rounded corner images. When there is &.n.b.s.p; in the cell my top row is 20px hight, but when there is no text in cells, top row disappears from Dreamweaver but it is in Firefox.
HOW TO FIX THIS? IS THERE ANY PATCH?

The only patch is not to use design view...or at least don't rely on it if that is what you use to design with. I never use design view...I gave up on it years ago as they never did perfect it 100%. If I was you, get into the habit of viewing your work right from the browser...F12 and the browser is launched. (all shortcut keys can be changed in Preferences)
If you strickly work in the design view then make sure you test it in the browser often to see how your work renders.
It is just how Dreamweaver rolls sometimes.

What is the replacement for design view in in flex builder 4.7 for cs extension builder?

Because design view is not available in flash builder than what is the use of extension builder in UI designing now we have to do design UI with xml which is very time consuming and boring if there is any replacemnt for it than please help me .1 more thing i want to know is that when i make new default project in extension builder(flash builder 4.6) than it also not able to load design mode errror is
C:\Program Files\Adobe\Adobe Flash Builder 4.6\eclipse\plugins\com.adobe.cside.libsinstaller_2.0.0.4-33034\archive\cslibs\2.0\4.5\re lease\apedelta.swc- not respondingSWC file failed to load. Any component dependent on this SWC file will not be displayed in the Design Mode.The SWC may have failed to load because of:
* Incompatible definitions caused by usage of a different SDK version
* Missing referred class definitions

I have researched this quite considerably and my understanding is that Adobe have no intention of supporting Design View any more for Extension Builder. In my opinion a very disappointing decision and one that is hard to comprehend.
The best workaround I can find is to create the majority of your design in a parallel, non Extension Builder, project and then convert/import your design into your Extension. This is by no means as satisfactory as having Design View for the Extension you are writing but it is better than simply creating your layout by guess work/trial and error.
Although this has not been announced by Adobe, I have a suspicion that the reason they have decided not to put any further resources into fixing Design View is that Extension Builder as we know it is going to be abandoned soon, probably replaced with an HTML5/JavaScript method of building extensions. My concern with this is that, other than wanting reassurances that there will be backward compatibility support for old extensions, There will not be a way of compiling an extension in a way that prevents people from seeing your code.
This is all speculation and I guess we will have to wait and see what happens. Hope this has helped.

Flashplayer10 afcs.swc, components not shown in Design view

Hi,
When I use the FlashPlayer10 swc nothing is shown in the Design View.
Is that bug ? isn't it just not working here ?

Hi, could you please try the followijg code and tell me if you can see the visual components in design view.
Make sure you try it with afcs.swc for Player 10 and Compiler set to 10.0.0
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" xmlns:rtc="AfcsNameSpace">
     <mx:RemoteObject showBusyCursor="true"
          id = "afcsService"
          destination = "afcsChat">
          <mx:method name="afcsAuth" result="afcsAuthResult(event)"/>
     </mx:RemoteObject>
     <mx:Script>
          <![CDATA[
            import mx.rpc.events.ResultEvent;
            private function getToken():void{
                 afcsService.afcsAuth();
            private function afcsAuthResult(e:ResultEvent):void{
                 auth.authenticationKey = String(e.result);
                  session.login();
          ]]>
     </mx:Script>
     <mx:Button x="10" y="10" label="Login" click="getToken()"/>
     <rtc:AdobeHSAuthenticator id="auth" />
     <rtc:ConnectSessionContainer autoLogin="false" id="session" width="100%" height="100%"
          authenticator="{auth}"
          roomURL="http://connectnow.acrobat.com/whomzour/videochat">
          <rtc:SimpleChat width="363" height="151" x="10" y="291"/>
          <rtc:WebCamera width="361.5" height="235" y="48" x="10"/>
          <rtc:AudioPublisher />
          <mx:List dataProvider="{session.userManager.userCollection}"
                  labelField="displayName" x="379.5" y="48" height="394" width="155"/>
     </rtc:ConnectSessionContainer>
</mx:Application>

I have created numerous forms in Designer and for some reason, "Edit in Designer" from PDF, I cannot edit any of the fields in Design View.

I have created numerous forms in Designer and for some reason, "Edit in Designer" from PDF, I cannot edit any of the fields in Design View.

Is it possible you accidentally put the fields on the master page?

Floated element breaks Design view in Dreamweaver CS3

I've tried searching for this issue but haven't found a fix yet and could use some help.
I am redesigning a site and am adding a fluid box to the page. This floated element breaks Design View in Dreamweaver CS3 but appears correctly in the Firefox, Chrome, and IE. I can get the element to appear correctly in Design View after I make minor changes to the page's HTML or CSS, however it always breaks when I save the file.
I've tried many work-arounds including adding an absoutely defined container div, altering the various div sizes, adding <div class="clear"> before and after the element, to no avail.
Ideally, I would like to have page appear correctly in Design View so that others in my lab can easily update the page (and not come to me with repeated questions!).
I've included screen prints of how it looks in Design View and how it look in Chrome.
THANKS! J
Design Time error:
Web Browser - correct view:

I'll try CS4; however my main reason for finding a fix is so that others updating the page (w/ CS3) will be able to do so w/ the WYSIWYG editor that we purchased. We will not be upgrading to CS4 anytime soon either.
Thanks

Page body not displaying in Design view

Using CS3, I am trying to edit a page in Design view, however the page does not appear.
http://www.angeleyesgps.com/index2.html
The page can be found here, showing the body content appearing, showing it is not commented out.
As you scroll down the page, you will see a Design view screenshot in CS3 (attached to this posting), showing what I am seeing.
Cannot find anything in the code causing this to happen. All other pages appear fine, with body content appearing.
Sure appreciate your help on this!
Mark

Your table structure is completely messed up. You have tables nested inside of cells and inside of tables... it's a real mess I'm afraid. Because you don't have matching pairs of tags for either tables or cells that correspond, the page isn't showing up in Design view.
I think you need to start again with the table structure -and make sure you nest them correctly.
Also, not sure why you have the content within a form tag... (just under the body - and then the corresponding closing form tag at the end of the document.
<body leftmargin="0" topmargin="0" marginwidth="0" marginheight="0" onLoad="start();" style="background-color:#1b140e">
<form name="form1" method="post" action="">
This is what the validator says:
http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.angeleyesgps.com%2Findex2.htm l
It' really a matter of starting again (sorry !).

Corrupt design view in Dreamweaver 2014

Is there a solution for the corrupt design view in Dreamweaver 2014. Adobe continues to fix this and it has not changed. My pages are all distorted and the elements/divs are all over the place. It is perfect in live view.
PLEASE...does anyone have a solution,
Thanks,
Kathy

Kathy,
Design view in Dreamweaver has always been very problematic, it amazes me that it has been OK for you in the past.
With DWCC14, live view has greatly improved and it will not surprise me if Adobe decide to drop Design view in future releases.
To answer your question, in DWCC14, I would not use design view at all. You can now use Live view where you could not use it in previous versions of DW.

CS3 will not show CSS3 and HTML5 in WYSIWYG "design view"?

So, just got a mobile site template that is CSS3 and HTML5. When I open it to work on it in Dreamweaver CS3, the CSS is not displayed in the "design view" but yet, when you preview in browser, all is perfect. In the WYSIWYG design view, I see the content, but styling is missing. Preview in browser, it is all there.
Is this just a limitation in the CS3 WYSIWYG design view function and I am out of luck? Is there a "fix" - other than a costly upgrade - for it in CS3?

yuytjtdh wrote:
So, just got a mobile site template that is CSS3 and HTML5. When I open it to work on it in Dreamweaver CS3, the CSS is not displayed in the "design view" but yet, when you preview in browser, all is perfect. In the WYSIWYG design view, I see the content, but styling is missing. Preview in browser, it is all there.
Is this just a limitation in the CS3 WYSIWYG design view function and I am out of luck? Is there a "fix" - other than a costly upgrade - for it in CS3?
Dreamweaver's design view isn't perfect WYSIWYG even for CSS2.1. Also, I believe you are using a very old DW (CS3) so you are definitely out of luck. Have you tried using the trial version of CS 5.5? It is worth a try but I am not recommending you to buy it now because CS6 is expected to be released in the second half of this year if not before.
Please note DW isn't a WYSIWYG editor so I won't rely on it at all. Always view your page in the two main browsers - FF and IE8/IE9
Good luck.

How do you set slide size in inches (8 1/2 by 11)

When I try to print, it doesn't print how I see it on the screen. I think it is because the slide sizes are wider than an 8 1/2 by 11 sheet (for widescreen viewing). How do you set up the page size so things print correctly. I tried to do this but it looks like you have to set the size in pixels and they don't give you an option for inches. I think this also affects when I export to PowerPoint and text boxes and other things are more squished in or not alligned. How do I configure Keynote slides to be 8 1/2 by 11?

Get yourself a copy of a program called PhotoScape. (Link)
Please mark the post that solves your issue as "Accept as Solution".
If my answer was helpful click the “Thumbs Up" on the left to say “Thanks”!
I am not a HP employee.

No CSS Design View?

I'm a guy that usually likes to style apps using an external CSS and selecting a component to style, and having a way to add that component's properties/styles to edit.
Flash Builder 4 has done away with this, but to me it feels like it's going BACKWARDS.. but it's probably something I'm missing, so I'd appreciate the way people are using it...
So right now it seems like I can set styles ON a component, and then MOVE it to the existing CSS file I have, but I want to make sure that this doesn't leave ANYTHING within the code view that is styled? I tested it and it seemed to leave backgroundColor in the mxml declaration.
On top of that, there's no autocomplete for any CSS in the CSS view?
Just seems for CSS view you're somewhat stuck to doing it all by hand again...

What SDK version are you using?
Let me start with the easy questions.
Autocomplete in CSS
Code hinting is supported in the CSS editor. If you're in a Flex 4 project, make sure you're using namespace qualified type selectors http://opensource.adobe.com/wiki/display/flexsdk/CSS+Namespaces+Support. That's the typical problem people have during the transition.
CSS Design View
There are a few reasons why CSS Design View isn't supported for Flex 4. Flex 4 skinning, in many cases, replaces CSS styles. For example, backgroundColor isn't supported for every component. For more information, see http://opensource.adobe.com/wiki/display/flexsdk/More+Styles+for+Spark+Skins or the Flex 4 reference http://help.adobe.com/en_US/flex/using/index.html. CSS Design View is supported for SDK 3 projects, but not for SDK 4.
Can you explain in more detail what you mean about setting styles on a component and moving them to a CSS file? Sounds like you're using Design view to set styles in MXML then convert them to CSS declarations. This should be fine since Design view should only let you set valid style properties.
Jason San Jose
Software Engineer, Flash Builder

How do you fit a 40 minute movie on a cd?

question: i have a 40-minute movie (.mov) that i can fit on to a dvd, but the client wants it on a cd rom since a lot of the employees are unable to view dvds. how do you reduce the file so that the quality is still acceptable and is small enough to fit on a cd?
any advice would be appreciated.
merci

We do this every week for our church, and the sermon is usually about 43 minutes long. Once exported, just burn it to a CD. Your users will need to have QuickTime to watch it.
Here's what we do to export from FCE, and the resulting file is about 70 MB for 484 x 272. If you want a larger video, you can make it twice the size, and increase the data rate to 816 kbps.
Export using QuickTime conversion:
Video settings: H.264, 29.97 fps, Key Frames Automatic, Restrict to 204 kbps (for 484 x 272), optimized for download, Frame reordering checked, Encoding Best Quality, size 484 x 272.
Sound settings: AAC, Mono (if stereo, double the data rate), 44.100 kHz, Render Quality Best, VBR Constrained, 48-54, kbps.
That will get you started. Depending on what sort of material you have in the video, you may want to raise the data rate (a CD will hold 700 MB, so you have plenty of space to play with). Try a one minute clip first to see how it comes out before you export the whole thing.
And yes, three hours (depending on your machine) may be what it takes. Our videos usually take less than two hours on a Core 2 Duo 2.33 GHz.
Hope this is helpful.

Design View showing collapsed components.

Ever since I add tomahawk Menu component in my project, all other components are not shown properly in the design view of jdeveloper. I added the menu component to one file and all the files in the project are now showing collapsed view (Only parent component is shown that too in a box). I tried restarting jdeveloper but the problem still remains. I cannot add/edit any components in design view now because of the above reason. How do I go about now?

Hi,
it appears that there is a problem with the WYSIWYG editor and 3rd party components not rendering properly. The outline view is a fallback that JDeveloper uses when it can't show the WYSIWYG (its the outline view). Not sure if you have a support contract inwhich case you could file this as a bug? If not, I'll put that down on my list of issues to track and follow up on.
thanks
Frank

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>
<head>

<title>Revelant Iron-Ons Home</title>

<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">

</script>

<script type="text/javascript">

</script>

</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">
<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></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">
        <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’s Cool Creation!          </p>
          <p>This is sure to become popular very quickly. God’s Cool Creation displays a wonderful arrangement of images and illustrations glorifying God in His handiwork of Earth’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, “Who despises the day of small things?” 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’s premium DURABrite<span class="Superscript">®</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’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>
      </div></div>
</div>
<div class="clearfloat"></div>
<div id="footer"><p class="foottype">© 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></div>
</div>
</body>
</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!

Design View Collapse - How do you un-do?

Similar Messages

Maybe you are looking for