<?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: Theme Building Challenge</title>
	<atom:link href="http://bradtheblogboy.com/traffic-building/blog-contests/theme-building-challenge/feed/" rel="self" type="application/rss+xml" />
	<link>http://bradtheblogboy.com/traffic-building/blog-contests/theme-building-challenge/?source=rss</link>
	<description>blogging 102</description>
	<lastBuildDate>Fri, 10 Apr 2009 13:35:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: blogboy</title>
		<link>http://bradtheblogboy.com/traffic-building/blog-contests/theme-building-challenge/comment-page-1/#comment-201</link>
		<dc:creator>blogboy</dc:creator>
		<pubDate>Tue, 15 Jul 2008 07:34:30 +0000</pubDate>
		<guid isPermaLink="false">http://bradtheblogboy.com/?p=80#comment-201</guid>
		<description>The problem with liquid layouts is you can only go so small with them and have them still be useful.  That threshold is almost always a 1000px width or close there too if you are going to use a sidebar with any sort of meaningful information in it.  The biggest problem with liquid formatting is you still have to decide at what width you want it to look its best.  A blog with a liquid layout best on a 1024px  width monitor will look almost as bad on a 1600px wide as it does on a 640px wide display.

As someone who uses a widescreen monitor having liquid formatting often times makes for bad formatting when it spills across a 22&quot; monitor having your sidebar ungodly far from the content or worse having entire posts stretch out into two or three lines of text running across the monitor.

Liquid layouts worked really well when the majority of people were using widths between 800px and 1024px.  While some of the new monitors still have native resolution at 1024x768 most of them are getting a lot bigger.  Theme designers need to start accounting for these bigger sizes with something better than just letting it stretch.  Theme switcher will let the end user decide what looks best for them without forcing the blogger to compromise on content vs navigation vs advertising.  Less than 200 characters of code will please a lot more people.

BTW You have no idea how bad some sites looked in IE 5.  The libraries are up for a levy soon and want to invest in new computers  and I am going to be pushing that they drop their silly notion of windows and the even sillier idea of affording Mac&#039;s and go with locally built linux machines with firefox.  Twice the machine at half the price.</description>
		<content:encoded><![CDATA[<p>The problem with liquid layouts is you can only go so small with them and have them still be useful.  That threshold is almost always a 1000px width or close there too if you are going to use a sidebar with any sort of meaningful information in it.  The biggest problem with liquid formatting is you still have to decide at what width you want it to look its best.  A blog with a liquid layout best on a 1024px  width monitor will look almost as bad on a 1600px wide as it does on a 640px wide display.</p>
<p>As someone who uses a widescreen monitor having liquid formatting often times makes for bad formatting when it spills across a 22&#8243; monitor having your sidebar ungodly far from the content or worse having entire posts stretch out into two or three lines of text running across the monitor.</p>
<p>Liquid layouts worked really well when the majority of people were using widths between 800px and 1024px.  While some of the new monitors still have native resolution at 1024&#215;768 most of them are getting a lot bigger.  Theme designers need to start accounting for these bigger sizes with something better than just letting it stretch.  Theme switcher will let the end user decide what looks best for them without forcing the blogger to compromise on content vs navigation vs advertising.  Less than 200 characters of code will please a lot more people.</p>
<p>BTW You have no idea how bad some sites looked in IE 5.  The libraries are up for a levy soon and want to invest in new computers  and I am going to be pushing that they drop their silly notion of windows and the even sillier idea of affording Mac&#8217;s and go with locally built linux machines with firefox.  Twice the machine at half the price.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://bradtheblogboy.com/traffic-building/blog-contests/theme-building-challenge/comment-page-1/#comment-200</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Tue, 15 Jul 2008 07:07:40 +0000</pubDate>
		<guid isPermaLink="false">http://bradtheblogboy.com/?p=80#comment-200</guid>
		<description>Well, actually there is no need for various types of themes for different resolution. Just get the designers to create a liquid layout (using proper XHTML and CSS) so that the layout will adjust to whatever resolution users are using.

IE5??? I think that most of the existing website of today will break when viewing with IE5.</description>
		<content:encoded><![CDATA[<p>Well, actually there is no need for various types of themes for different resolution. Just get the designers to create a liquid layout (using proper XHTML and CSS) so that the layout will adjust to whatever resolution users are using.</p>
<p>IE5??? I think that most of the existing website of today will break when viewing with IE5.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Theme Building Challenge - WebProWorld</title>
		<link>http://bradtheblogboy.com/traffic-building/blog-contests/theme-building-challenge/comment-page-1/#comment-199</link>
		<dc:creator>Theme Building Challenge - WebProWorld</dc:creator>
		<pubDate>Sun, 13 Jul 2008 01:45:37 +0000</pubDate>
		<guid isPermaLink="false">http://bradtheblogboy.com/?p=80#comment-199</guid>
		<description>[...] Building Challenge     Theme Building Challenge  There isn&#039;t a lot I can say that I haven&#039;t already said int he post except I am closer to finding [...]</description>
		<content:encoded><![CDATA[<p>[...] Building Challenge     Theme Building Challenge  There isn&#8217;t a lot I can say that I haven&#8217;t already said int he post except I am closer to finding [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

