<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Random Web Development and Web Designer Tips</title>
	<atom:link href="http://www.webredesignpro.com/2010/02/05/web-design-development-tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webredesignpro.com/2010/02/05/web-design-development-tips/</link>
	<description>Web design, whether starting from scratch or redesigning, is all about planning and organization. Think long-term but focus on short-term -- and never lose sight of your customer.</description>
	<lastBuildDate>Sat, 10 Jul 2010 02:48:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: George</title>
		<link>http://www.webredesignpro.com/2010/02/05/web-design-development-tips/comment-page-1/#comment-202</link>
		<dc:creator>George</dc:creator>
		<pubDate>Sat, 10 Jul 2010 02:48:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.webredesignpro.com/2010/02/05/random-web-development-and-web-designner-tips/#comment-202</guid>
		<description>normal block element, like a  can be set to a certain height and width. What happens when the content of the DIV exceeds the size given to it?

Enter the CSS property &#039;overflow&#039;.

    * overflow: auto - This will create a scrollbar - horizontal, vertical or both only if the content in the block requires it. For practical web development, this is probably the most useful approach to creating a scrollbar.
    * overflow: scroll - This will will insert horizontal and vertical scrollbars. They will become active only if the content requires it.
    * overflow: visible - This will cause the content of the block to expand outside of it and be visible at the same time.
    * overflow: hidden - This forces the block to only show content that fits in the block. Other content will be clipped and not visible. There will be no scrollbars.

CSS code:


 

in the  add DIV layer with overflow contents 
This is a scrolling are created with the CSS property overflow.
</description>
		<content:encoded><![CDATA[<p>normal block element, like a  can be set to a certain height and width. What happens when the content of the DIV exceeds the size given to it?</p>
<p>Enter the CSS property &#8216;overflow&#8217;.</p>
<p>    * overflow: auto &#8211; This will create a scrollbar &#8211; horizontal, vertical or both only if the content in the block requires it. For practical web development, this is probably the most useful approach to creating a scrollbar.<br />
    * overflow: scroll &#8211; This will will insert horizontal and vertical scrollbars. They will become active only if the content requires it.<br />
    * overflow: visible &#8211; This will cause the content of the block to expand outside of it and be visible at the same time.<br />
    * overflow: hidden &#8211; This forces the block to only show content that fits in the block. Other content will be clipped and not visible. There will be no scrollbars.</p>
<p>CSS code:</p>
<p>in the  add DIV layer with overflow contents<br />
This is a scrolling are created with the CSS property overflow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Syracuse Designer</title>
		<link>http://www.webredesignpro.com/2010/02/05/web-design-development-tips/comment-page-1/#comment-44</link>
		<dc:creator>Syracuse Designer</dc:creator>
		<pubDate>Sun, 23 May 2010 13:28:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.webredesignpro.com/2010/02/05/random-web-development-and-web-designner-tips/#comment-44</guid>
		<description>Thank you for useful tips.
More might be added to &quot;Random Web Development and Web Designer Tips&quot; 

Best Practices for Speeding Up Your Web Site

    * Minimize HTTP Requests
    * Use a Content Delivery Network
    * Add an Expires or a Cache-Control Header
    * Gzip Components
    * Put Stylesheets at the Top
    * Put Scripts at the Bottom
    * Avoid CSS Expressions
    * Make JavaScript and CSS External
    * Reduce DNS Lookups
    * Minify JavaScript and CSS
    * Avoid Redirects
    * Remove Duplicate Scripts
    * Configure ETags
    * Make Ajax Cacheable
    * Flush the Buffer Early
    * Use GET for AJAX Requests
    * Post-load Components
    * Preload Components
    * Reduce the Number of DOM Elements
    * Split Components Across Domains
    * Minimize the Number of iframes
    * No 404s
    * Reduce Cookie Size
    * Use Cookie-free Domains for Components
    * Minimize DOM Access
    * Develop Smart Event Handlers
    * Choose  over @import
    * Avoid Filters
    * Optimize Images
    * Optimize CSS Sprites
    * Don&#039;t Scale Images in HTML
    * Make favicon.ico Small and Cacheable
    * Keep Components under 25K
    * Pack Components into a Multipart Document</description>
		<content:encoded><![CDATA[<p>Thank you for useful tips.<br />
More might be added to &#8220;Random Web Development and Web Designer Tips&#8221; </p>
<p>Best Practices for Speeding Up Your Web Site</p>
<p>    * Minimize HTTP Requests<br />
    * Use a Content Delivery Network<br />
    * Add an Expires or a Cache-Control Header<br />
    * Gzip Components<br />
    * Put Stylesheets at the Top<br />
    * Put Scripts at the Bottom<br />
    * Avoid CSS Expressions<br />
    * Make JavaScript and CSS External<br />
    * Reduce DNS Lookups<br />
    * Minify JavaScript and CSS<br />
    * Avoid Redirects<br />
    * Remove Duplicate Scripts<br />
    * Configure ETags<br />
    * Make Ajax Cacheable<br />
    * Flush the Buffer Early<br />
    * Use GET for AJAX Requests<br />
    * Post-load Components<br />
    * Preload Components<br />
    * Reduce the Number of DOM Elements<br />
    * Split Components Across Domains<br />
    * Minimize the Number of iframes<br />
    * No 404s<br />
    * Reduce Cookie Size<br />
    * Use Cookie-free Domains for Components<br />
    * Minimize DOM Access<br />
    * Develop Smart Event Handlers<br />
    * Choose  over @import<br />
    * Avoid Filters<br />
    * Optimize Images<br />
    * Optimize CSS Sprites<br />
    * Don&#8217;t Scale Images in HTML<br />
    * Make favicon.ico Small and Cacheable<br />
    * Keep Components under 25K<br />
    * Pack Components into a Multipart Document</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kela</title>
		<link>http://www.webredesignpro.com/2010/02/05/web-design-development-tips/comment-page-1/#comment-42</link>
		<dc:creator>kela</dc:creator>
		<pubDate>Fri, 05 Feb 2010 17:07:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.webredesignpro.com/2010/02/05/random-web-development-and-web-designner-tips/#comment-42</guid>
		<description>thank you this is good</description>
		<content:encoded><![CDATA[<p>thank you this is good</p>
]]></content:encoded>
	</item>
</channel>
</rss>
