<?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>mir.aculo.us &#187; Hints</title>
	<atom:link href="http://mir.aculo.us/tag/hints/feed/" rel="self" type="application/rss+xml" />
	<link>http://mir.aculo.us</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Wed, 01 Sep 2010 15:36:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Little JavaScript hints, episode 3: force redraw</title>
		<link>http://mir.aculo.us/2009/01/11/little-javascript-hints-episode-3-force-redraw/</link>
		<comments>http://mir.aculo.us/2009/01/11/little-javascript-hints-episode-3-force-redraw/#comments</comments>
		<pubDate>Sun, 11 Jan 2009 09:52:00 +0000</pubDate>
		<dc:creator>Thomas Fuchs</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Hints]]></category>
		<category><![CDATA[JavaScript]]></category>

		<guid isPermaLink="false">http://mir.aculo.us//2009/01/11/little-javascript-hints-episode-3-force-redraw</guid>
		<description><![CDATA[If you ever did some advanced DOM manipulation stuff, especially CSS-based animations, you might have run into situations where the browser just wouldn&#8217;t redraw an element correctly. Here&#8217;s a little snippet for Prototype I use to force redraw in such situations: Element.addMethods({ redraw: function(element){ element = $(element); var n = document.createTextNode(' '); element.appendChild(n); (function(){n.parentNode.removeChild(n)}).defer(); return [...]]]></description>
		<wfw:commentRss>http://mir.aculo.us/2009/01/11/little-javascript-hints-episode-3-force-redraw/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Using input values as hints, the easy way</title>
		<link>http://mir.aculo.us/2009/01/07/using-input-values-as-hints-the-easy-way/</link>
		<comments>http://mir.aculo.us/2009/01/07/using-input-values-as-hints-the-easy-way/#comments</comments>
		<pubDate>Wed, 07 Jan 2009 12:17:00 +0000</pubDate>
		<dc:creator>Thomas Fuchs</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Hints]]></category>
		<category><![CDATA[JavaScript]]></category>

		<guid isPermaLink="false">http://mir.aculo.us//2009/01/07/using-input-values-as-hints-the-easy-way</guid>
		<description><![CDATA[An often occuring UI pattern is &#8220;use the value of a textfield as hint what to input&#8221;. These fields all auto-clear when the user first focuses it (by clicking or tabbing it), and if nothing it entered, the hint will be shown once again once the user leaves it. Because we decided to go this [...]]]></description>
		<wfw:commentRss>http://mir.aculo.us/2009/01/07/using-input-values-as-hints-the-easy-way/feed/</wfw:commentRss>
		<slash:comments>21</slash:comments>
		</item>
		<item>
		<title>Credit card validation</title>
		<link>http://mir.aculo.us/2008/12/22/credit-card-validation/</link>
		<comments>http://mir.aculo.us/2008/12/22/credit-card-validation/#comments</comments>
		<pubDate>Mon, 22 Dec 2008 11:06:00 +0000</pubDate>
		<dc:creator>Thomas Fuchs</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Hints]]></category>
		<category><![CDATA[JavaScript]]></category>

		<guid isPermaLink="false">http://mir.aculo.us//2008/12/22/credit-card-validation</guid>
		<description><![CDATA[We all know that payment processing can be very painful. At least, everyone who&#8217;s ever tried to do it knows. To help ease the pain, Amy came up with a Jump Start Credit Card Processing cheat sheet for Ruby Advent 2008, based on our experiences when implementing freckle time tracking. The cheat sheet does explaining-in-layman-terms [...]]]></description>
		<wfw:commentRss>http://mir.aculo.us/2008/12/22/credit-card-validation/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Little JavaScript hints, episode 2: stay DRY</title>
		<link>http://mir.aculo.us/2008/12/20/little-javascript-hints-episode-2-stay-dry/</link>
		<comments>http://mir.aculo.us/2008/12/20/little-javascript-hints-episode-2-stay-dry/#comments</comments>
		<pubDate>Sat, 20 Dec 2008 10:42:00 +0000</pubDate>
		<dc:creator>Thomas Fuchs</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Hints]]></category>
		<category><![CDATA[JavaScript]]></category>

		<guid isPermaLink="false">http://mir.aculo.us//2008/12/20/little-javascript-hints-episode-2-stay-dry</guid>
		<description><![CDATA[Here&#8217;s a technique you can use to DRY (Don&#8217;t repeat yourself) up your code, if you have very similiar methods that just do the &#8220;opposite&#8221;. An example of this are controls that do scrolling or paging, and often include a forward/back button. I often see code like this: function nextPage(){ // do something } function [...]]]></description>
		<wfw:commentRss>http://mir.aculo.us/2008/12/20/little-javascript-hints-episode-2-stay-dry/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Little JavaScript hints, episode 1: prevent console.log breakage</title>
		<link>http://mir.aculo.us/2008/12/19/little-javascript-hints-episode-1/</link>
		<comments>http://mir.aculo.us/2008/12/19/little-javascript-hints-episode-1/#comments</comments>
		<pubDate>Fri, 19 Dec 2008 17:38:00 +0000</pubDate>
		<dc:creator>Thomas Fuchs</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Hints]]></category>
		<category><![CDATA[JavaScript]]></category>

		<guid isPermaLink="false">http://mir.aculo.us//2008/12/19/little-javascript-hints-episode-1</guid>
		<description><![CDATA[Here&#8217;s something I&#8217;ve tripped over in the past, and it hit me again while developing some JavaScript for freckle. Firebug&#8217;s console.log is of great value. But don&#8217;t dare you forget it in your code before you deploy&#8230; Here&#8217;s a quick snippet that saves your code from exploding (this is for peeps that use Prototype): 1 [...]]]></description>
		<wfw:commentRss>http://mir.aculo.us/2008/12/19/little-javascript-hints-episode-1/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
	</channel>
</rss>
