<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Screwlewse.com</title>
	<atom:link href="http://screwlewse.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://screwlewse.com</link>
	<description>Front End Engineering notes</description>
	<lastBuildDate>Thu, 26 Aug 2010 05:31:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>CSS3 columns, height, and / or backgrounds</title>
		<link>http://screwlewse.com/2010/08/css3-columns-height-and-or-backgrounds/</link>
		<comments>http://screwlewse.com/2010/08/css3-columns-height-and-or-backgrounds/#comments</comments>
		<pubDate>Thu, 26 Aug 2010 05:23:11 +0000</pubDate>
		<dc:creator>Dave Gregory</dc:creator>
				<category><![CDATA[webdev]]></category>

		<guid isPermaLink="false">http://screwlewse.com/?p=373</guid>
		<description><![CDATA[In some replies today today in Twitter, faux columns came up, then the idea that having to never use faux columns would be a great idea. And then CSS3 Columns were brought up. At the time of this article, CSS3 &#8230; <a href="http://screwlewse.com/2010/08/css3-columns-height-and-or-backgrounds/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://screwlewse.com/2010/08/css3-columns-height-and-or-backgrounds/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Reply to &#8220;Best Clearfix Ever&#8221; post.</title>
		<link>http://screwlewse.com/2010/08/reply-to-best-clearfix-ever-post/</link>
		<comments>http://screwlewse.com/2010/08/reply-to-best-clearfix-ever-post/#comments</comments>
		<pubDate>Mon, 23 Aug 2010 17:50:48 +0000</pubDate>
		<dc:creator>Dave Gregory</dc:creator>
				<category><![CDATA[browser-issues]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[webdev]]></category>

		<guid isPermaLink="false">http://screwlewse.com/?p=348</guid>
		<description><![CDATA[I just had to reply to the clearfix post found on Marc Watts website.  I felt that some aspects of his clearfix solution needed to be cleaned up, as well as explaining a bit more about past solutions. In the &#8230; <a href="http://screwlewse.com/2010/08/reply-to-best-clearfix-ever-post/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://screwlewse.com/2010/08/reply-to-best-clearfix-ever-post/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Different CSS techniques and their performance</title>
		<link>http://screwlewse.com/2010/08/different-css-techniques-and-their-performance/</link>
		<comments>http://screwlewse.com/2010/08/different-css-techniques-and-their-performance/#comments</comments>
		<pubDate>Wed, 04 Aug 2010 06:56:55 +0000</pubDate>
		<dc:creator>Dave Gregory</dc:creator>
				<category><![CDATA[webdev]]></category>

		<guid isPermaLink="false">http://screwlewse.com/?p=321</guid>
		<description><![CDATA[Why would I want to test performance of CSS techniques? Here&#8217;s the background: I am a big fan of OOCSS, (the library and the concept) but I have been using Compass, SASS lately at work. I was feeling that sometimes &#8230; <a href="http://screwlewse.com/2010/08/different-css-techniques-and-their-performance/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://screwlewse.com/2010/08/different-css-techniques-and-their-performance/feed/</wfw:commentRss>
		<slash:comments>44</slash:comments>
		</item>
		<item>
		<title>Don&#8217;t use ID selectors in CSS</title>
		<link>http://screwlewse.com/2010/07/dont-use-id-selectors-in-css/</link>
		<comments>http://screwlewse.com/2010/07/dont-use-id-selectors-in-css/#comments</comments>
		<pubDate>Wed, 28 Jul 2010 04:29:07 +0000</pubDate>
		<dc:creator>Dave Gregory</dc:creator>
				<category><![CDATA[css]]></category>
		<category><![CDATA[webdev]]></category>

		<guid isPermaLink="false">http://screwlewse.com/?p=306</guid>
		<description><![CDATA[Lately I have been testing out performance among css styles and I found that some of my very smart friends, started asking,&#8221;why aren&#8217;t you testing using ID&#8217;s for the unique sections of the page?&#8221;. This wasn&#8217;t a hard answer: The &#8230; <a href="http://screwlewse.com/2010/07/dont-use-id-selectors-in-css/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://screwlewse.com/2010/07/dont-use-id-selectors-in-css/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using the window.location property in Javascript</title>
		<link>http://screwlewse.com/2010/07/using-the-window-location-property-in-javascript/</link>
		<comments>http://screwlewse.com/2010/07/using-the-window-location-property-in-javascript/#comments</comments>
		<pubDate>Thu, 22 Jul 2010 05:34:30 +0000</pubDate>
		<dc:creator>Dave Gregory</dc:creator>
				<category><![CDATA[javascript / jQuery]]></category>
		<category><![CDATA[webdev]]></category>

		<guid isPermaLink="false">http://screwlewse.com/?p=245</guid>
		<description><![CDATA[I often forget how this works, so here is the different properties of window.location. Thanks to DevGuru for the data. To see how these work, pop open your firebug and add them to your console box and run them. The &#8230; <a href="http://screwlewse.com/2010/07/using-the-window-location-property-in-javascript/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://screwlewse.com/2010/07/using-the-window-location-property-in-javascript/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Loading your javascript files asynchronously</title>
		<link>http://screwlewse.com/2010/06/loading-your-javascript-files-asynchronously/</link>
		<comments>http://screwlewse.com/2010/06/loading-your-javascript-files-asynchronously/#comments</comments>
		<pubDate>Sat, 26 Jun 2010 07:38:31 +0000</pubDate>
		<dc:creator>Dave Gregory</dc:creator>
				<category><![CDATA[javascript / jQuery]]></category>
		<category><![CDATA[webdev]]></category>
		<category><![CDATA[yahoo]]></category>

		<guid isPermaLink="false">http://screwlewse.com/?p=287</guid>
		<description><![CDATA[So it&#8217;s widely understood now, that performance has a direct effect on the traffic of our site.   This puts performance at a much higher priority than before.. especially if your site traffic is what pays the bills.  Steve Souders began &#8230; <a href="http://screwlewse.com/2010/06/loading-your-javascript-files-asynchronously/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://screwlewse.com/2010/06/loading-your-javascript-files-asynchronously/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>The joys of Vertical-Align using inline-block</title>
		<link>http://screwlewse.com/2010/02/the-joys-of-vertical-align-using-inline-block/</link>
		<comments>http://screwlewse.com/2010/02/the-joys-of-vertical-align-using-inline-block/#comments</comments>
		<pubDate>Fri, 26 Feb 2010 22:38:27 +0000</pubDate>
		<dc:creator>Dave Gregory</dc:creator>
				<category><![CDATA[browser-issues]]></category>
		<category><![CDATA[css]]></category>

		<guid isPermaLink="false">http://screwlewse.com/?p=250</guid>
		<description><![CDATA[I am being sarcastic.   As designs are getting more complex and more and more developers are ditching IE6&#8230; we are finding new problems using these new styles. Specifically, we need a way to make different elements (all with different margins &#8230; <a href="http://screwlewse.com/2010/02/the-joys-of-vertical-align-using-inline-block/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://screwlewse.com/2010/02/the-joys-of-vertical-align-using-inline-block/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using Regex in Textmate to convert HTML comments to Ruby comments</title>
		<link>http://screwlewse.com/2009/12/using-regex-in-textmate-to-convert-html-comments-to-ruby-comments/</link>
		<comments>http://screwlewse.com/2009/12/using-regex-in-textmate-to-convert-html-comments-to-ruby-comments/#comments</comments>
		<pubDate>Thu, 17 Dec 2009 00:37:23 +0000</pubDate>
		<dc:creator>Dave Gregory</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[rails]]></category>
		<category><![CDATA[webdev]]></category>

		<guid isPermaLink="false">http://screwlewse.com/?p=221</guid>
		<description><![CDATA[To cut down on space, I felt it would be easy enough to convert HTML comments to Ruby comments, so I looked for a way to do this site-wide. Using the Regex option in textmate&#8217;s &#8220;find in project&#8221; utility will &#8230; <a href="http://screwlewse.com/2009/12/using-regex-in-textmate-to-convert-html-comments-to-ruby-comments/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://screwlewse.com/2009/12/using-regex-in-textmate-to-convert-html-comments-to-ruby-comments/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IE8 rendering modes&#8230; useful when things go wrong in IE8.</title>
		<link>http://screwlewse.com/2009/12/ie8-rendering-modes-useful-when-things-go-wrong-in-ie8/</link>
		<comments>http://screwlewse.com/2009/12/ie8-rendering-modes-useful-when-things-go-wrong-in-ie8/#comments</comments>
		<pubDate>Fri, 11 Dec 2009 17:59:44 +0000</pubDate>
		<dc:creator>Dave Gregory</dc:creator>
				<category><![CDATA[Internet Explorer]]></category>
		<category><![CDATA[browser-issues]]></category>
		<category><![CDATA[css]]></category>

		<guid isPermaLink="false">http://screwlewse.com/?p=212</guid>
		<description><![CDATA[There are two different modes for IE8 rendering of a page.. They now have a X-UA compatibility meta tag that allows you to change the mode on a per-page basis. NOTE: it&#8217;s also important to note that this tag only &#8230; <a href="http://screwlewse.com/2009/12/ie8-rendering-modes-useful-when-things-go-wrong-in-ie8/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://screwlewse.com/2009/12/ie8-rendering-modes-useful-when-things-go-wrong-in-ie8/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Testing for elements is good, but watch out for prototype.</title>
		<link>http://screwlewse.com/2009/11/testing-for-elements-is-good-but-watch-out-for-prototype/</link>
		<comments>http://screwlewse.com/2009/11/testing-for-elements-is-good-but-watch-out-for-prototype/#comments</comments>
		<pubDate>Tue, 03 Nov 2009 05:31:01 +0000</pubDate>
		<dc:creator>Dave Gregory</dc:creator>
				<category><![CDATA[javascript / jQuery]]></category>

		<guid isPermaLink="false">http://screwlewse.com/?p=201</guid>
		<description><![CDATA[So using css selectors is fairly easy in Prototype: finding and element with ID: $('name_of_id') finding an element(s) with other selectors: (I am only using one example) $$('.className') Now before looking for an element, it&#8217;s always good to test whether &#8230; <a href="http://screwlewse.com/2009/11/testing-for-elements-is-good-but-watch-out-for-prototype/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://screwlewse.com/2009/11/testing-for-elements-is-good-but-watch-out-for-prototype/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
