<?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>Frontend Force Blog</title>
	<atom:link href="http://blog.frontendforce.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.frontendforce.com</link>
	<description>We write about javascript</description>
	<lastBuildDate>Tue, 15 Jun 2010 16:05:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Continuous Code Validation using JSLint</title>
		<link>http://blog.frontendforce.com/2010/06/continuous-code-validation-using-jslint/</link>
		<comments>http://blog.frontendforce.com/2010/06/continuous-code-validation-using-jslint/#comments</comments>
		<pubDate>Tue, 15 Jun 2010 16:04:34 +0000</pubDate>
		<dc:creator>Adam Stankiewicz</dc:creator>
				<category><![CDATA[Guides]]></category>
		<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Server Side]]></category>
		<category><![CDATA[jslint]]></category>
		<category><![CDATA[nodejs]]></category>
		<category><![CDATA[validation]]></category>

		<guid isPermaLink="false">http://blog.frontendforce.com/?p=245</guid>
		<description><![CDATA[
Callbacks are often found in JavaScript code. Some say &#8216;They are inconvenient and make code harder to understand&#8217;. Actually, it is a matter of habit and JS code may be as readable and easy to understand as any other. Additionally, this approach of coding allow us to &#8216;release&#8217; program flow. No function is waiting for [...]]]></description>
		<wfw:commentRss>http://blog.frontendforce.com/2010/06/continuous-code-validation-using-jslint/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>jQuery vs MooTools Nightly Benchmark</title>
		<link>http://blog.frontendforce.com/2010/05/jquery-vs-mootools-nightly-benchmark/</link>
		<comments>http://blog.frontendforce.com/2010/05/jquery-vs-mootools-nightly-benchmark/#comments</comments>
		<pubDate>Mon, 31 May 2010 19:15:23 +0000</pubDate>
		<dc:creator>Adam Stankiewicz</dc:creator>
				<category><![CDATA[Benchmarks]]></category>
		<category><![CDATA[Good to know]]></category>
		<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[MooTools]]></category>
		<category><![CDATA[Web Development]]></category>
		<category><![CDATA[jQuery]]></category>
		<category><![CDATA[benchmark]]></category>
		<category><![CDATA[slick]]></category>

		<guid isPermaLink="false">http://blog.frontendforce.com/?p=234</guid>
		<description><![CDATA[
MooTools team suprised us by releasing 1.3 beta. One of the most notable features was Slick &#8211; very fast selector engine. It does not use MooTools code, so finally we can use it without attaching whole MooTools Core. On other side, as everybody knows, jQuery seems to have fastest selector engine among JavaScript libraries &#8211; [...]]]></description>
		<wfw:commentRss>http://blog.frontendforce.com/2010/05/jquery-vs-mootools-nightly-benchmark/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Unit Testing in JavaScript: Selenium</title>
		<link>http://blog.frontendforce.com/2010/05/unit-testing-in-javascript-selenium/</link>
		<comments>http://blog.frontendforce.com/2010/05/unit-testing-in-javascript-selenium/#comments</comments>
		<pubDate>Sun, 30 May 2010 17:20:49 +0000</pubDate>
		<dc:creator>Adam Stankiewicz</dc:creator>
				<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Unit Testing]]></category>
		<category><![CDATA[Web Development]]></category>
		<category><![CDATA[selenium]]></category>
		<category><![CDATA[tutorial]]></category>
		<category><![CDATA[webdriver]]></category>

		<guid isPermaLink="false">http://blog.frontendforce.com/?p=223</guid>
		<description><![CDATA[
I&#8217;ve described tools like QUnit or JSSpec. They allow us to test JavaScript functions, classes, generally things that works without refreshing the page. But what if we need to check existance of &#8220;Log in&#8221; page, whether navigation works properly or user is able to modify settings of his account. These actions require loading several pages on [...]]]></description>
		<wfw:commentRss>http://blog.frontendforce.com/2010/05/unit-testing-in-javascript-selenium/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>JavaScript oddities explained. Comparing.</title>
		<link>http://blog.frontendforce.com/2010/05/javascript-oddities-explained-comparing/</link>
		<comments>http://blog.frontendforce.com/2010/05/javascript-oddities-explained-comparing/#comments</comments>
		<pubDate>Wed, 19 May 2010 18:53:40 +0000</pubDate>
		<dc:creator>Adam Stankiewicz</dc:creator>
				<category><![CDATA[Good to know]]></category>
		<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[comparing]]></category>
		<category><![CDATA[oddities]]></category>
		<category><![CDATA[wtfjs]]></category>

		<guid isPermaLink="false">http://blog.frontendforce.com/?p=195</guid>
		<description><![CDATA[
This post is inspired by Brian Leroux and his wtfjs tumblr blog. JavaScript is full of unexplained oddities. I&#8217;m going to prove you that every each of them can be explained. There are several causes of such interpreter behavior: inaccurate specification, hyper-correct interpreting, understatements, waywardness of browsers creators. The first type of such &#8216;features&#8217; are [...]]]></description>
		<wfw:commentRss>http://blog.frontendforce.com/2010/05/javascript-oddities-explained-comparing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mobile Application Development using JavaScript</title>
		<link>http://blog.frontendforce.com/2010/05/mobile-application-development-using-javascript/</link>
		<comments>http://blog.frontendforce.com/2010/05/mobile-application-development-using-javascript/#comments</comments>
		<pubDate>Sun, 16 May 2010 18:04:05 +0000</pubDate>
		<dc:creator>Adam Stankiewicz</dc:creator>
				<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[Mobile Development]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Web Development]]></category>
		<category><![CDATA[android]]></category>
		<category><![CDATA[blackberry]]></category>
		<category><![CDATA[frameworks]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[titanium]]></category>
		<category><![CDATA[webos]]></category>

		<guid isPermaLink="false">http://blog.frontendforce.com/?p=165</guid>
		<description><![CDATA[
JavaScript is not only for webpages and web applications. Among other things, You can create realtime applications, serverside solutions, desktop and mobile applications. There are two types of moble applications: running in browser and native ones. These latter are often faster and more powerful. That&#8217;s because they have access to filesystem, accelometer, camera and et [...]]]></description>
		<wfw:commentRss>http://blog.frontendforce.com/2010/05/mobile-application-development-using-javascript/feed/</wfw:commentRss>
		<slash:comments>52</slash:comments>
		</item>
		<item>
		<title>HTML5 JavaScript API. What&#8217;s new?</title>
		<link>http://blog.frontendforce.com/2010/04/html5-javascript-api-whats-new/</link>
		<comments>http://blog.frontendforce.com/2010/04/html5-javascript-api-whats-new/#comments</comments>
		<pubDate>Thu, 22 Apr 2010 19:22:22 +0000</pubDate>
		<dc:creator>Adam Stankiewicz</dc:creator>
				<category><![CDATA[HTML5]]></category>
		<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Web Development]]></category>
		<category><![CDATA[canvas]]></category>
		<category><![CDATA[features]]></category>
		<category><![CDATA[modern browsers]]></category>

		<guid isPermaLink="false">http://blog.frontendforce.com/?p=128</guid>
		<description><![CDATA[
HTML5 has a lot of new features. There&#8217;s new HTML, CSS and, of course, JavaScript. Officially HTML5 specification and implementation won&#8217;t be ready until 2022. Personally I don&#8217;t believe in this. Majority of JavaScript features described further are already implemented in modern browsers (e.g. Sarafi, Chrome, Firefox, Opera). Even Internet Explorer gained capability to render canvas [...]]]></description>
		<wfw:commentRss>http://blog.frontendforce.com/2010/04/html5-javascript-api-whats-new/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Event Delegation with JavaScript</title>
		<link>http://blog.frontendforce.com/2010/04/event-delegation-with-javascript/</link>
		<comments>http://blog.frontendforce.com/2010/04/event-delegation-with-javascript/#comments</comments>
		<pubDate>Mon, 19 Apr 2010 12:00:20 +0000</pubDate>
		<dc:creator>Adam Stankiewicz</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[Web Development]]></category>
		<category><![CDATA[delegating]]></category>
		<category><![CDATA[event]]></category>
		<category><![CDATA[jQuery]]></category>
		<category><![CDATA[MooTools]]></category>

		<guid isPermaLink="false">http://blog.frontendforce.com/?p=107</guid>
		<description><![CDATA[
Event delegation involves attaching event handler to parent DOM element. Reason is simple: when an event is triggered on an element, the same event is also triggered on all of that element&#8217;s ancescors. Event bubbles up from the most nested element (e.g. button) to the root of the DOM (e.g. window); this process is known [...]]]></description>
		<wfw:commentRss>http://blog.frontendforce.com/2010/04/event-delegation-with-javascript/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>10 steps to make your site cacheable</title>
		<link>http://blog.frontendforce.com/2010/04/10-steps-to-make-your-site-cacheable/</link>
		<comments>http://blog.frontendforce.com/2010/04/10-steps-to-make-your-site-cacheable/#comments</comments>
		<pubDate>Fri, 02 Apr 2010 16:27:42 +0000</pubDate>
		<dc:creator>Adam Stankiewicz</dc:creator>
				<category><![CDATA[Guides]]></category>
		<category><![CDATA[Web Development]]></category>
		<category><![CDATA[backend]]></category>
		<category><![CDATA[caching]]></category>
		<category><![CDATA[performance]]></category>

		<guid isPermaLink="false">http://blog.frontendforce.com/?p=90</guid>
		<description><![CDATA[
If your startup is relatively new and doesn&#8217;t take much network traffic, there&#8217;s probably no reason to be interested in caching. The problem arises when users begin to complain about the time to load several pages. Well, users hate waiting. If you care about their convenience or you are curious about caching this article is [...]]]></description>
		<wfw:commentRss>http://blog.frontendforce.com/2010/04/10-steps-to-make-your-site-cacheable/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Games development in JavaScript: Canvas vs DOM benchmark</title>
		<link>http://blog.frontendforce.com/2010/03/games-development-in-javascript-canvas-vs-dom-benchmark/</link>
		<comments>http://blog.frontendforce.com/2010/03/games-development-in-javascript-canvas-vs-dom-benchmark/#comments</comments>
		<pubDate>Tue, 30 Mar 2010 08:39:55 +0000</pubDate>
		<dc:creator>Piotrek Koszuliński</dc:creator>
				<category><![CDATA[Games]]></category>
		<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[benchmark]]></category>
		<category><![CDATA[canvas]]></category>
		<category><![CDATA[dom]]></category>
		<category><![CDATA[performance]]></category>

		<guid isPermaLink="false">http://blog.frontendforce.com/?p=77</guid>
		<description><![CDATA[﻿

In my last article I described four frameworks used in games&#8217; developing. What differentiate frameworks is the way in which they render graphic. Each framework I mentioned used DOM and CSS, only one enabled the use of Canvas too. But it&#8217;s obvious that in time more and more frameworks will work with it &#8211; it&#8217;s [...]]]></description>
		<wfw:commentRss>http://blog.frontendforce.com/2010/03/games-development-in-javascript-canvas-vs-dom-benchmark/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Unit Testing in JavaScript: JSSpec</title>
		<link>http://blog.frontendforce.com/2010/03/unit-testing-in-javascript-jsspec/</link>
		<comments>http://blog.frontendforce.com/2010/03/unit-testing-in-javascript-jsspec/#comments</comments>
		<pubDate>Sat, 27 Mar 2010 14:42:39 +0000</pubDate>
		<dc:creator>Adam Stankiewicz</dc:creator>
				<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[Programming]]></category>
		<category><![CDATA[Unit Testing]]></category>
		<category><![CDATA[bdd]]></category>
		<category><![CDATA[jsspec]]></category>
		<category><![CDATA[test]]></category>

		<guid isPermaLink="false">http://blog.frontendforce.com/?p=63</guid>
		<description><![CDATA[
If you are not familiar with definition of Unit Testing or you are wondering about solutions in JavaScript go to one of my previous articles.
If you want to see real example of Unit Testing or Test Driven Development, go to article Unit Testing in JavaScript: QUnit.
Today&#8217;s Unit Testing Framework is JSSpec. It is used by MooTools, [...]]]></description>
		<wfw:commentRss>http://blog.frontendforce.com/2010/03/unit-testing-in-javascript-jsspec/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

