<?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>WilcoFiers.com</title>
	<atom:link href="http://wilcofiers.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://wilcofiers.com</link>
	<description>Stuff that matters to people, like me.</description>
	<lastBuildDate>Thu, 31 Mar 2011 16:00:39 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
		<item>
		<title>Using strict mode in javascript today</title>
		<link>http://wilcofiers.com/2011/03/using-strict-mode-today/</link>
		<comments>http://wilcofiers.com/2011/03/using-strict-mode-today/#comments</comments>
		<pubDate>Thu, 31 Mar 2011 16:00:39 +0000</pubDate>
		<dc:creator>Wilco</dc:creator>
				<category><![CDATA[Javascript]]></category>
		<category><![CDATA[ECMAScript 5]]></category>

		<guid isPermaLink="false">http://wilcofiers.com/?p=122</guid>
		<description><![CDATA[For a very long time, javascript has remained the same. Browser venders have given us new things to access from using javascript. But the language it&#8217;s self has remained pretty much the same since it&#8217;s conception in 1995. As of &#8230; <a href="http://wilcofiers.com/2011/03/using-strict-mode-today/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://wilcofiers.com/2011/03/using-strict-mode-today/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>OOP in Javascript, the right way</title>
		<link>http://wilcofiers.com/2011/03/oop-in-javascrip/</link>
		<comments>http://wilcofiers.com/2011/03/oop-in-javascrip/#comments</comments>
		<pubDate>Thu, 24 Mar 2011 17:00:43 +0000</pubDate>
		<dc:creator>Wilco</dc:creator>
				<category><![CDATA[Javascript]]></category>
		<category><![CDATA[CommonJS]]></category>
		<category><![CDATA[design patterns]]></category>
		<category><![CDATA[frameworks]]></category>
		<category><![CDATA[RequireJS]]></category>

		<guid isPermaLink="false">http://wilcofiers.com/?p=44</guid>
		<description><![CDATA[In the past months I&#8217;ve covered a lot of topics involving the basics of javascript, several design patterns, and the power of RequireJS as a tool for better JS applications. Now it&#8217;s time to put the pieces together and let&#8217;s &#8230; <a href="http://wilcofiers.com/2011/03/oop-in-javascrip/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://wilcofiers.com/2011/03/oop-in-javascrip/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HTML Form styling with Formall – part 2</title>
		<link>http://wilcofiers.com/2011/03/form-styling-with-formall-2/</link>
		<comments>http://wilcofiers.com/2011/03/form-styling-with-formall-2/#comments</comments>
		<pubDate>Thu, 17 Mar 2011 17:00:08 +0000</pubDate>
		<dc:creator>Wilco</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[design patterns]]></category>
		<category><![CDATA[Formall]]></category>
		<category><![CDATA[HTML5]]></category>
		<category><![CDATA[WAI:ARIA]]></category>

		<guid isPermaLink="false">http://wilcofiers.com/?p=109</guid>
		<description><![CDATA[As an accessibility researcher, this subject is pretty close to my heart. When I designed Formall, the first priority was given to make sure that the HTML which would create good looking forms would also create accessible and user friendly &#8230; <a href="http://wilcofiers.com/2011/03/form-styling-with-formall-2/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://wilcofiers.com/2011/03/form-styling-with-formall-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HTML Form styling with Formall – part 1</title>
		<link>http://wilcofiers.com/2011/03/form-styling-with-formall-1/</link>
		<comments>http://wilcofiers.com/2011/03/form-styling-with-formall-1/#comments</comments>
		<pubDate>Thu, 10 Mar 2011 17:00:18 +0000</pubDate>
		<dc:creator>Wilco</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[design patterns]]></category>
		<category><![CDATA[Formall]]></category>
		<category><![CDATA[HTML5]]></category>
		<category><![CDATA[WAI:ARIA]]></category>

		<guid isPermaLink="false">http://wilcofiers.com/?p=98</guid>
		<description><![CDATA[One of the most painful jobs of front end development, I always found to be styling forms across different browsers. The CSS rules on how forms should be styled leave much to the imagination of browser vendors. So I&#8217;ve attempted &#8230; <a href="http://wilcofiers.com/2011/03/form-styling-with-formall-1/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://wilcofiers.com/2011/03/form-styling-with-formall-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Javascript modules</title>
		<link>http://wilcofiers.com/2011/03/javascript-modules/</link>
		<comments>http://wilcofiers.com/2011/03/javascript-modules/#comments</comments>
		<pubDate>Thu, 03 Mar 2011 17:00:52 +0000</pubDate>
		<dc:creator>Wilco</dc:creator>
				<category><![CDATA[Javascript]]></category>
		<category><![CDATA[design patterns]]></category>

		<guid isPermaLink="false">http://wilcofiers.com/?p=40</guid>
		<description><![CDATA[The module pattern has taken the javascript world by storm. Almost every library out there uses it these days. It has become the corner stone of server side javascript. There has even been talk of including it in a future &#8230; <a href="http://wilcofiers.com/2011/03/javascript-modules/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://wilcofiers.com/2011/03/javascript-modules/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Variable visibility in javascript</title>
		<link>http://wilcofiers.com/2011/02/variable-visibilit/</link>
		<comments>http://wilcofiers.com/2011/02/variable-visibilit/#comments</comments>
		<pubDate>Mon, 28 Feb 2011 17:00:54 +0000</pubDate>
		<dc:creator>Wilco</dc:creator>
				<category><![CDATA[Javascript]]></category>
		<category><![CDATA[design patterns]]></category>

		<guid isPermaLink="false">http://wilcofiers.com/?p=42</guid>
		<description><![CDATA[Every function has it&#8217;s own scope. A place where we can declare variables that are only available within the function it&#8217;s self. We&#8217;ve already seen how this can create private variables in a constructor. But there is much more to &#8230; <a href="http://wilcofiers.com/2011/02/variable-visibilit/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://wilcofiers.com/2011/02/variable-visibilit/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Constructors vs factories</title>
		<link>http://wilcofiers.com/2011/02/constructors-vs-factories/</link>
		<comments>http://wilcofiers.com/2011/02/constructors-vs-factories/#comments</comments>
		<pubDate>Wed, 23 Feb 2011 17:00:39 +0000</pubDate>
		<dc:creator>Wilco</dc:creator>
				<category><![CDATA[Javascript]]></category>
		<category><![CDATA[design patterns]]></category>

		<guid isPermaLink="false">http://wilcofiers.com/?p=36</guid>
		<description><![CDATA[Often in Javascript, you only want one instance of an object. In classical OOP this is done with a singleton design pattern. In javascript we simply use the object literal (i.e. { property: &#8216;value&#8217;}). But when we need a multitude &#8230; <a href="http://wilcofiers.com/2011/02/constructors-vs-factories/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://wilcofiers.com/2011/02/constructors-vs-factories/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Inheritance using the Caller extension pattern</title>
		<link>http://wilcofiers.com/2011/02/caller-extension-pattern/</link>
		<comments>http://wilcofiers.com/2011/02/caller-extension-pattern/#comments</comments>
		<pubDate>Fri, 18 Feb 2011 17:00:32 +0000</pubDate>
		<dc:creator>Wilco</dc:creator>
				<category><![CDATA[Javascript]]></category>
		<category><![CDATA[design patterns]]></category>

		<guid isPermaLink="false">http://wilcofiers.com/?p=26</guid>
		<description><![CDATA[The caller extension pattern is a design pattern I&#8217;ve discovered, which let&#8217;s you create constructors that can inherit from any other constructor. To do this we get to use some javascript magic: the call and apply methods. So let&#8217;s see &#8230; <a href="http://wilcofiers.com/2011/02/caller-extension-pattern/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://wilcofiers.com/2011/02/caller-extension-pattern/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A critical look at javascript&#8217;s prototype</title>
		<link>http://wilcofiers.com/2011/02/critical-look-at-prototype/</link>
		<comments>http://wilcofiers.com/2011/02/critical-look-at-prototype/#comments</comments>
		<pubDate>Sun, 13 Feb 2011 15:00:01 +0000</pubDate>
		<dc:creator>Wilco</dc:creator>
				<category><![CDATA[Javascript]]></category>

		<guid isPermaLink="false">http://wilcofiers.com/?p=23</guid>
		<description><![CDATA[Javascript&#8217;s prototype is often compared to the inheritance model used by classical OOP languages. In these languages a sub class inherits properties and methods from a super class. In the sub class you can then add and override methods and &#8230; <a href="http://wilcofiers.com/2011/02/critical-look-at-prototype/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://wilcofiers.com/2011/02/critical-look-at-prototype/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The basics of javascript prototype</title>
		<link>http://wilcofiers.com/2011/02/basics-of-prototype/</link>
		<comments>http://wilcofiers.com/2011/02/basics-of-prototype/#comments</comments>
		<pubDate>Tue, 08 Feb 2011 17:00:12 +0000</pubDate>
		<dc:creator>Wilco</dc:creator>
				<category><![CDATA[Javascript]]></category>

		<guid isPermaLink="false">http://wilcofiers.com/?p=20</guid>
		<description><![CDATA[In the next couple of articles I&#8217;ll introduce a number of design patterns that I feel have the potential to be the staple food of any javascript application. But to really understand these, we need to first understand some of &#8230; <a href="http://wilcofiers.com/2011/02/basics-of-prototype/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://wilcofiers.com/2011/02/basics-of-prototype/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
