<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: True or False &#8211; Autotrace</title>
	<atom:link href="http://hoopercharles.wordpress.com/2010/04/08/true-or-false-autotrace/feed/" rel="self" type="application/rss+xml" />
	<link>http://hoopercharles.wordpress.com/2010/04/08/true-or-false-autotrace/</link>
	<description>Miscellaneous Random Oracle Topics: Stop, Think, ... Understand</description>
	<lastBuildDate>Thu, 23 May 2013 04:02:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Roberto</title>
		<link>http://hoopercharles.wordpress.com/2010/04/08/true-or-false-autotrace/#comment-1162</link>
		<dc:creator><![CDATA[Roberto]]></dc:creator>
		<pubDate>Wed, 26 May 2010 07:36:01 +0000</pubDate>
		<guid isPermaLink="false">http://hoopercharles.wordpress.com/?p=1873#comment-1162</guid>
		<description><![CDATA[4:3 now is ok]]></description>
		<content:encoded><![CDATA[<p>4:3 now is ok</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles Hooper</title>
		<link>http://hoopercharles.wordpress.com/2010/04/08/true-or-false-autotrace/#comment-1146</link>
		<dc:creator><![CDATA[Charles Hooper]]></dc:creator>
		<pubDate>Tue, 25 May 2010 14:18:11 +0000</pubDate>
		<guid isPermaLink="false">http://hoopercharles.wordpress.com/?p=1873#comment-1146</guid>
		<description><![CDATA[I did not think about the possibility of specifying percentage widths.  I am only able to make adjustments through changes to the CSS specification - I do not have direct access to the HTML coding of the pages.  That said, CSS offers a lot of flexibility once the names of the styles defined in the HTML coding are determined.

I just made another change - hopefully it will make the blog a bit more viewable on the netbook, and hopefully address the issue that Roberto mentioned with his 4:3 screen.]]></description>
		<content:encoded><![CDATA[<p>I did not think about the possibility of specifying percentage widths.  I am only able to make adjustments through changes to the CSS specification &#8211; I do not have direct access to the HTML coding of the pages.  That said, CSS offers a lot of flexibility once the names of the styles defined in the HTML coding are determined.</p>
<p>I just made another change &#8211; hopefully it will make the blog a bit more viewable on the netbook, and hopefully address the issue that Roberto mentioned with his 4:3 screen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: coskan</title>
		<link>http://hoopercharles.wordpress.com/2010/04/08/true-or-false-autotrace/#comment-1145</link>
		<dc:creator><![CDATA[coskan]]></dc:creator>
		<pubDate>Tue, 25 May 2010 13:50:08 +0000</pubDate>
		<guid isPermaLink="false">http://hoopercharles.wordpress.com/?p=1873#comment-1145</guid>
		<description><![CDATA[Do you give fixed size width  or a percentage ? I am not sure how wordpress works but I believe percentage can sort the issue (If I recall my html knowledge corretly). As a feedback  With 1280 width resolutions scrollbar appears but for only 10pixel diffrence which does not make any problem for blog post. By the way I think you can also change the size of the header table which is still using the same size]]></description>
		<content:encoded><![CDATA[<p>Do you give fixed size width  or a percentage ? I am not sure how wordpress works but I believe percentage can sort the issue (If I recall my html knowledge corretly). As a feedback  With 1280 width resolutions scrollbar appears but for only 10pixel diffrence which does not make any problem for blog post. By the way I think you can also change the size of the header table which is still using the same size</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles Hooper</title>
		<link>http://hoopercharles.wordpress.com/2010/04/08/true-or-false-autotrace/#comment-1144</link>
		<dc:creator><![CDATA[Charles Hooper]]></dc:creator>
		<pubDate>Tue, 25 May 2010 11:13:13 +0000</pubDate>
		<guid isPermaLink="false">http://hoopercharles.wordpress.com/?p=1873#comment-1144</guid>
		<description><![CDATA[Roberto and Coskan,

Thank you for the feedback.  I am not 100% happy with the new layout yet.

I admit that the code sections in the original layout caused me problems in the past.  It was especially difficult to copy the text from a code section if the last line did not quite fit into the small code window - it seems that 50% of the time Internet Explorer would also copy the entire contents of the web page from that point down.  I also did not like that nearly half of an execution plan was hidden in the code sections.  The content portion of the blog (and the code sections) is now almost twice as wide as before.  This change not only fixed the code sections, but also allows me to add larger versions of pictures that are presented on the blog.

After seeing Roberto&#039;s comment this morning I attempted to view the web page using a Toshiba netbook that has a 16:9 screen with 1024 horizontal lines of resolution.  The content portion of the page would just barely fit on the screen if I scrolled the screen slightly to the right.  The latest release of Internet Explorer offers a zoom percent, which I noticed automatically adjusts on some websites that are viewed on the netbook.  The zoom feature may be a work-around.  It would be nice if I did not need to scroll slightly to the right to view a page.

I modified this blog article to include 3 screen capture:
1. Netbook showing the &quot;modified&quot; version of this blog.
2. 4:3 20 inch monitor at 1600 x 1200 resolution (not using the full width of the screen) showing the original version of the blog.
3. 4:3 20 inch monitor at 1600 x 1200 resolution (not using the full width of the screen) showing the modified version of the blog.]]></description>
		<content:encoded><![CDATA[<p>Roberto and Coskan,</p>
<p>Thank you for the feedback.  I am not 100% happy with the new layout yet.</p>
<p>I admit that the code sections in the original layout caused me problems in the past.  It was especially difficult to copy the text from a code section if the last line did not quite fit into the small code window &#8211; it seems that 50% of the time Internet Explorer would also copy the entire contents of the web page from that point down.  I also did not like that nearly half of an execution plan was hidden in the code sections.  The content portion of the blog (and the code sections) is now almost twice as wide as before.  This change not only fixed the code sections, but also allows me to add larger versions of pictures that are presented on the blog.</p>
<p>After seeing Roberto&#8217;s comment this morning I attempted to view the web page using a Toshiba netbook that has a 16:9 screen with 1024 horizontal lines of resolution.  The content portion of the page would just barely fit on the screen if I scrolled the screen slightly to the right.  The latest release of Internet Explorer offers a zoom percent, which I noticed automatically adjusts on some websites that are viewed on the netbook.  The zoom feature may be a work-around.  It would be nice if I did not need to scroll slightly to the right to view a page.</p>
<p>I modified this blog article to include 3 screen capture:<br />
1. Netbook showing the &#8220;modified&#8221; version of this blog.<br />
2. 4:3 20 inch monitor at 1600 x 1200 resolution (not using the full width of the screen) showing the original version of the blog.<br />
3. 4:3 20 inch monitor at 1600 x 1200 resolution (not using the full width of the screen) showing the modified version of the blog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roberto</title>
		<link>http://hoopercharles.wordpress.com/2010/04/08/true-or-false-autotrace/#comment-1142</link>
		<dc:creator><![CDATA[Roberto]]></dc:creator>
		<pubDate>Tue, 25 May 2010 09:27:09 +0000</pubDate>
		<guid isPermaLink="false">http://hoopercharles.wordpress.com/?p=1873#comment-1142</guid>
		<description><![CDATA[For my 4/3 monitor is worse than before :-(]]></description>
		<content:encoded><![CDATA[<p>For my 4/3 monitor is worse than before <img src='http://s0.wp.com/wp-includes/images/smilies/icon_sad.gif' alt=':-(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: coskan</title>
		<link>http://hoopercharles.wordpress.com/2010/04/08/true-or-false-autotrace/#comment-1141</link>
		<dc:creator><![CDATA[coskan]]></dc:creator>
		<pubDate>Tue, 25 May 2010 08:50:47 +0000</pubDate>
		<guid isPermaLink="false">http://hoopercharles.wordpress.com/?p=1873#comment-1141</guid>
		<description><![CDATA[Looks awesome Charles. Thank you very much for this change. It really made reading way easier than it was, I hope others will like it as well.]]></description>
		<content:encoded><![CDATA[<p>Looks awesome Charles. Thank you very much for this change. It really made reading way easier than it was, I hope others will like it as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles Hooper</title>
		<link>http://hoopercharles.wordpress.com/2010/04/08/true-or-false-autotrace/#comment-1107</link>
		<dc:creator><![CDATA[Charles Hooper]]></dc:creator>
		<pubDate>Mon, 24 May 2010 21:15:04 +0000</pubDate>
		<guid isPermaLink="false">http://hoopercharles.wordpress.com/?p=1873#comment-1107</guid>
		<description><![CDATA[Now I need to dig out the book on CSS to fix what I can.  The modified theme is not quite flexible-width, but at least I can see most of the code sections now, and I still have the scrolling windows for those code sections that are too wide.]]></description>
		<content:encoded><![CDATA[<p>Now I need to dig out the book on CSS to fix what I can.  The modified theme is not quite flexible-width, but at least I can see most of the code sections now, and I still have the scrolling windows for those code sections that are too wide.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles Hooper</title>
		<link>http://hoopercharles.wordpress.com/2010/04/08/true-or-false-autotrace/#comment-1099</link>
		<dc:creator><![CDATA[Charles Hooper]]></dc:creator>
		<pubDate>Mon, 24 May 2010 18:05:31 +0000</pubDate>
		<guid isPermaLink="false">http://hoopercharles.wordpress.com/?p=1873#comment-1099</guid>
		<description><![CDATA[Coskan,

Thank you for the suggestion.  The last time that I looked at the various themes was in December 2009.  The theme that I originally selected simply truncated the right side of code sections.  I explored the idea of using a flexible width theme, but found that those themes also caused the right side of some code sections to be truncated.  So, I settled on a theme that permits horizontally scrollable code sections.  When the code section is taller than the web browser window it is difficult to see the entire code section because, of course, the scrollbar does not appear on the screen.

Now that I have a couple of decent articles on the blog (I think that I am up to 5 decent articles now), it might be worth spending $15 USD a year for access to Wordpress&#039; Custom CSS feature so that I can hopefully make the code sections wider and still scrollable.]]></description>
		<content:encoded><![CDATA[<p>Coskan,</p>
<p>Thank you for the suggestion.  The last time that I looked at the various themes was in December 2009.  The theme that I originally selected simply truncated the right side of code sections.  I explored the idea of using a flexible width theme, but found that those themes also caused the right side of some code sections to be truncated.  So, I settled on a theme that permits horizontally scrollable code sections.  When the code section is taller than the web browser window it is difficult to see the entire code section because, of course, the scrollbar does not appear on the screen.</p>
<p>Now that I have a couple of decent articles on the blog (I think that I am up to 5 decent articles now), it might be worth spending $15 USD a year for access to WordPress&#8217; Custom CSS feature so that I can hopefully make the code sections wider and still scrollable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: coskan</title>
		<link>http://hoopercharles.wordpress.com/2010/04/08/true-or-false-autotrace/#comment-1096</link>
		<dc:creator><![CDATA[coskan]]></dc:creator>
		<pubDate>Mon, 24 May 2010 17:25:55 +0000</pubDate>
		<guid isPermaLink="false">http://hoopercharles.wordpress.com/?p=1873#comment-1096</guid>
		<description><![CDATA[Charles,

Great thread but the wordpress template you use makes it really hard to follow.   is there a chance you move to a flexible-width template (like the one I use or Jonathan use there are around 8 templates on wordpress ) instead of fixed-width template like the one you use ?

  Your stuff is really great but the template makes it very hard to follow especially when there is too many code in it.  

Please take this as a regular loyal reader feedback.]]></description>
		<content:encoded><![CDATA[<p>Charles,</p>
<p>Great thread but the wordpress template you use makes it really hard to follow.   is there a chance you move to a flexible-width template (like the one I use or Jonathan use there are around 8 templates on wordpress ) instead of fixed-width template like the one you use ?</p>
<p>  Your stuff is really great but the template makes it very hard to follow especially when there is too many code in it.  </p>
<p>Please take this as a regular loyal reader feedback.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: limewire</title>
		<link>http://hoopercharles.wordpress.com/2010/04/08/true-or-false-autotrace/#comment-737</link>
		<dc:creator><![CDATA[limewire]]></dc:creator>
		<pubDate>Fri, 30 Apr 2010 16:41:02 +0000</pubDate>
		<guid isPermaLink="false">http://hoopercharles.wordpress.com/?p=1873#comment-737</guid>
		<description><![CDATA[dang amazing stuff man.]]></description>
		<content:encoded><![CDATA[<p>dang amazing stuff man.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
