<?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 for Chris Johnston</title>
	<atom:link href="http://www.fuzzylizard.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fuzzylizard.com</link>
	<description>Web development and design with a little VFX thrown in for fun</description>
	<lastBuildDate>Tue, 28 Apr 2009 21:54:54 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on HTML 4.01 or xHTML 1? by Morgan Roderick</title>
		<link>http://www.fuzzylizard.com/archives/2009/04/29/1053/comment-page-1/#comment-34404</link>
		<dc:creator>Morgan Roderick</dc:creator>
		<pubDate>Tue, 28 Apr 2009 21:54:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.fuzzylizard.com/?p=1053#comment-34404</guid>
		<description>The stricter the better!

If it was practical, I&#039;d love to use a proper mimetype when serving XHTML documents.

One thing that comes to mind, which Dave doesn&#039;t mention is the fact that XHTML 1.0 Strict has been cleaned of a lot of the presentational elements that plagued us in the past. I wouldn&#039;t want to go back to presentational markup again.</description>
		<content:encoded><![CDATA[<p>The stricter the better!</p>
<p>If it was practical, I&#8217;d love to use a proper mimetype when serving XHTML documents.</p>
<p>One thing that comes to mind, which Dave doesn&#8217;t mention is the fact that XHTML 1.0 Strict has been cleaned of a lot of the presentational elements that plagued us in the past. I wouldn&#8217;t want to go back to presentational markup again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Keep CSS clean by Bernd Eckenfels</title>
		<link>http://www.fuzzylizard.com/archives/2009/04/14/1038/comment-page-1/#comment-34402</link>
		<dc:creator>Bernd Eckenfels</dc:creator>
		<pubDate>Thu, 16 Apr 2009 05:00:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.fuzzylizard.com/?p=1038#comment-34402</guid>
		<description>Yes agreed. Consistent elements across multiple plages is a good thing, and CSS is the first place you can see if you violate that.</description>
		<content:encoded><![CDATA[<p>Yes agreed. Consistent elements across multiple plages is a good thing, and CSS is the first place you can see if you violate that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Keep CSS clean by Chris Johnston</title>
		<link>http://www.fuzzylizard.com/archives/2009/04/14/1038/comment-page-1/#comment-34401</link>
		<dc:creator>Chris Johnston</dc:creator>
		<pubDate>Thu, 16 Apr 2009 00:49:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.fuzzylizard.com/?p=1038#comment-34401</guid>
		<description>I definitely agree with reserving the use of h1-h6 tags solely for describing elements of content.

As for using different renderings based on content, I would have to say that the more consistent you can have things across your site, the better things are going to look. The more I can style an h3 tag once and keep it the same, the easier it is for my users to recognize what they are looking at. This applies to all the different elements on the page.

There may be exceptions to this rule, but I would suggest thinking real hard before you add custom renderings for something and ask yourself why need it.

The more consistent your site is, the easier it is for your users to, well, use.</description>
		<content:encoded><![CDATA[<p>I definitely agree with reserving the use of h1-h6 tags solely for describing elements of content.</p>
<p>As for using different renderings based on content, I would have to say that the more consistent you can have things across your site, the better things are going to look. The more I can style an h3 tag once and keep it the same, the easier it is for my users to recognize what they are looking at. This applies to all the different elements on the page.</p>
<p>There may be exceptions to this rule, but I would suggest thinking real hard before you add custom renderings for something and ask yourself why need it.</p>
<p>The more consistent your site is, the easier it is for your users to, well, use.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Programatically adding tags to contacts in Highrise by Chris Johnston</title>
		<link>http://www.fuzzylizard.com/archives/2009/04/03/1028/comment-page-1/#comment-34400</link>
		<dc:creator>Chris Johnston</dc:creator>
		<pubDate>Thu, 16 Apr 2009 00:46:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.fuzzylizard.com/?p=1028#comment-34400</guid>
		<description>I have not gotten that far. I have been side tracked a little lately working on a Rails site. Anyway, I will give it a shot in the next little while and see if I can figure it out.</description>
		<content:encoded><![CDATA[<p>I have not gotten that far. I have been side tracked a little lately working on a Rails site. Anyway, I will give it a shot in the next little while and see if I can figure it out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Programatically adding tags to contacts in Highrise by Pete</title>
		<link>http://www.fuzzylizard.com/archives/2009/04/03/1028/comment-page-1/#comment-34399</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Wed, 15 Apr 2009 21:04:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.fuzzylizard.com/?p=1028#comment-34399</guid>
		<description>Interesting post. I&#039;ve been finding holes in the Highrise API to - for example, have you managed to remove an email address or phone number from a person? Reading the API documentation, you would assume you&#039;d just omit the details you want to remove from an update post but that doesn&#039;t seem to work.

I&#039;m stumped

Cheers,
Pete</description>
		<content:encoded><![CDATA[<p>Interesting post. I&#8217;ve been finding holes in the Highrise API to &#8211; for example, have you managed to remove an email address or phone number from a person? Reading the API documentation, you would assume you&#8217;d just omit the details you want to remove from an update post but that doesn&#8217;t seem to work.</p>
<p>I&#8217;m stumped</p>
<p>Cheers,<br />
Pete</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Keep CSS clean by Bernd Eckenfels</title>
		<link>http://www.fuzzylizard.com/archives/2009/04/14/1038/comment-page-1/#comment-34398</link>
		<dc:creator>Bernd Eckenfels</dc:creator>
		<pubDate>Wed, 15 Apr 2009 04:10:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.fuzzylizard.com/?p=1038#comment-34398</guid>
		<description>I somewhat disagree. If you do semantic markup with heading levels you do have to use different renderings based on the context.

However it might also be wrong to use headings for things like navigation. Reserve the h1-h6 for the body/content.

Greetings
Bernd</description>
		<content:encoded><![CDATA[<p>I somewhat disagree. If you do semantic markup with heading levels you do have to use different renderings based on the context.</p>
<p>However it might also be wrong to use headings for things like navigation. Reserve the h1-h6 for the body/content.</p>
<p>Greetings<br />
Bernd</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Quickstart JSP/Servlets Demo using NetBeans by geekmaster</title>
		<link>http://www.fuzzylizard.com/archives/2005/09/18/628/comment-page-1/#comment-34365</link>
		<dc:creator>geekmaster</dc:creator>
		<pubDate>Wed, 25 Mar 2009 23:38:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.fuzzylizard.com/archives/2005/09/18/628/#comment-34365</guid>
		<description>really awesome tutorial.. waiting for more of those.....</description>
		<content:encoded><![CDATA[<p>really awesome tutorial.. waiting for more of those&#8230;..</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Weird behaviour from Nokogiri on Solaris by Chris Johnston</title>
		<link>http://www.fuzzylizard.com/archives/2009/02/17/1014/comment-page-1/#comment-33241</link>
		<dc:creator>Chris Johnston</dc:creator>
		<pubDate>Tue, 17 Feb 2009 21:37:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.fuzzylizard.com/?p=1014#comment-33241</guid>
		<description>Hi Aaron,

&lt;a href=&quot;http://nokogiri.lighthouseapp.com/projects/19607/tickets/37-nokogirihtml-returning-just-doctype-comments-on-solaris#ticket-37-2&quot; rel=&quot;nofollow&quot;&gt;It is ticket #37.&lt;/a&gt; The ticket contains the version of libxml2, ruby, and nokogiri that we are using. The version on Solaris are:

Nokogiri: 1.1.1 
Libxml2: 2.6.31 
Mechanize: 0.9.0 
Ruby: 1.8.6 p0</description>
		<content:encoded><![CDATA[<p>Hi Aaron,</p>
<p><a href="http://nokogiri.lighthouseapp.com/projects/19607/tickets/37-nokogirihtml-returning-just-doctype-comments-on-solaris#ticket-37-2" rel="nofollow">It is ticket #37.</a> The ticket contains the version of libxml2, ruby, and nokogiri that we are using. The version on Solaris are:</p>
<p>Nokogiri: 1.1.1<br />
Libxml2: 2.6.31<br />
Mechanize: 0.9.0<br />
Ruby: 1.8.6 p0</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Weird behaviour from Nokogiri on Solaris by Aaron Patterson</title>
		<link>http://www.fuzzylizard.com/archives/2009/02/17/1014/comment-page-1/#comment-33231</link>
		<dc:creator>Aaron Patterson</dc:creator>
		<pubDate>Tue, 17 Feb 2009 18:19:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.fuzzylizard.com/?p=1014#comment-33231</guid>
		<description>Hi Chris,

Where did you file the ticket? I don&#039;t see it in our lighthouse tracker.

What version of libxml2 are you using on the systems?  What version of solaris?

Also, I&#039;m not sure how I&#039;ll fix this.  I don&#039;t have access to a solaris machine.  I&#039;ll see if I can get a parallels instance working.</description>
		<content:encoded><![CDATA[<p>Hi Chris,</p>
<p>Where did you file the ticket? I don&#8217;t see it in our lighthouse tracker.</p>
<p>What version of libxml2 are you using on the systems?  What version of solaris?</p>
<p>Also, I&#8217;m not sure how I&#8217;ll fix this.  I don&#8217;t have access to a solaris machine.  I&#8217;ll see if I can get a parallels instance working.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How to get Phusion Passenger and ImageMagick to work together? by Mat</title>
		<link>http://www.fuzzylizard.com/archives/2008/07/05/954/comment-page-1/#comment-33140</link>
		<dc:creator>Mat</dc:creator>
		<pubDate>Sun, 15 Feb 2009 00:45:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.fuzzylizard.com/?p=954#comment-33140</guid>
		<description>I didn&#039;t want to install ports or hack Ruby, here&#039;s a patch we submitted to paperclip that allows you to use Paperclip   Phusion   ImageMagick nicely: http://thoughtbot.lighthouseapp.com/projects/8794-paperclip/tickets/109-phusion-passenger-mod_rails-issue-on-osx</description>
		<content:encoded><![CDATA[<p>I didn&#8217;t want to install ports or hack Ruby, here&#8217;s a patch we submitted to paperclip that allows you to use Paperclip   Phusion   ImageMagick nicely: <a href="http://thoughtbot.lighthouseapp.com/projects/8794-paperclip/tickets/109-phusion-passenger-mod_rails-issue-on-osx" rel="nofollow">http://thoughtbot.lighthouseapp.com/projects/8794-paperclip/tickets/109-phusion-passenger-mod_rails-issue-on-osx</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
