<?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>Asgeir Hoem</title>
	<atom:link href="http://blog.asgeirhoem.no/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.asgeirhoem.no</link>
	<description>Visual communicator / logbook &#38; brain bin</description>
	<lastBuildDate>Thu, 28 Jul 2011 06:32:33 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
		<item>
		<title>CSS3 ribbon effect</title>
		<link>http://blog.asgeirhoem.no/css3-ribbon-effect/</link>
		<comments>http://blog.asgeirhoem.no/css3-ribbon-effect/#comments</comments>
		<pubDate>Thu, 28 Jul 2011 06:32:33 +0000</pubDate>
		<dc:creator>Asgeir</dc:creator>
				<category><![CDATA[CSS]]></category>

		<guid isPermaLink="false">http://blog.asgeirhoem.no/?p=977</guid>
		<description><![CDATA[This wrap-around banner effect contains no unneccessary markup, and uses padding + negative margins to align the content with its parent element. The illusion of depth is achieved by using the :before and :after selectors. The triangles are created with border corners, where an opaque border meets a transparent border. As far as I know, [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://asgeirhoem.no/ex/css-wraparound-ribbon/" ><img class="alignnone size-full wp-image-978" title="CSS3 ribbon, no additional markup" src="http://blog.asgeirhoem.no/wp-content/uploads/2011/07/css3-ribbon.jpg" alt="" width="818" height="409" /></a></p>
<p>This <a title="CSS wrap-around ribbon" href="http://asgeirhoem.no/ex/css-wraparound-ribbon/" >wrap-around banner effect</a> contains no unneccessary markup, and  uses padding + negative margins to align the content with its parent  element. The illusion of depth is achieved by using the :before and  :after selectors. The triangles are created with border corners, where  an opaque border meets a transparent border.</p>
<p>As far as I know, there is no simpler way to achieve this effect. Hope you can use it!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.asgeirhoem.no/css3-ribbon-effect/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Stop hiding behind products</title>
		<link>http://blog.asgeirhoem.no/stop-hiding-behind-products/</link>
		<comments>http://blog.asgeirhoem.no/stop-hiding-behind-products/#comments</comments>
		<pubDate>Mon, 14 Mar 2011 07:49:27 +0000</pubDate>
		<dc:creator>Asgeir</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://blog.asgeirhoem.no/?p=971</guid>
		<description><![CDATA[Years back, we at User Interface Engineering did a little experiment. We asked folks to search for information and items on sites they’d never been to. In advance of showing them the site, we asked them what terms they thought described what they were seeking, then we asked them to go to the site and [...]]]></description>
			<content:encoded><![CDATA[<blockquote><p>Years back, we at User Interface Engineering did a little  experiment. We asked folks to search for information and items on sites  they’d never been to. In advance of showing them the site, we asked them  what terms they thought described what they were seeking, then we asked  them to go to the site and find what the items. After they either  completed the task or gave up, we went back to the site’s home page and  counted the number of times the users terms were on that page.</p>
<p>On  the sites where the users’ terms were present in the navigation, those  users succeeded about 72% of the time at finding what they were seeking.  Yet, on the sites that didn’t mention the users’ terms at all, those  users only succeeded 6% of the time.</p></blockquote>
<p><a href="http://webstandardssherpa.com/reviews/stop-hiding-behind-products/" onclick="javascript:pageTracker._trackPageview('/outbound/article/webstandardssherpa.com');">http://webstandardssherpa.com/reviews/stop-hiding-behind-products/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.asgeirhoem.no/stop-hiding-behind-products/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Single input login</title>
		<link>http://blog.asgeirhoem.no/single-input-login/</link>
		<comments>http://blog.asgeirhoem.no/single-input-login/#comments</comments>
		<pubDate>Mon, 25 Oct 2010 12:43:07 +0000</pubDate>
		<dc:creator>Asgeir</dc:creator>
				<category><![CDATA[User Interface]]></category>
		<category><![CDATA[UX]]></category>

		<guid isPermaLink="false">http://www.asgeirhoem.no/?p=963</guid>
		<description><![CDATA[Amrinder Sandhu over at A Way Back has attracted a lot of attention with his single input login form. I don&#8217;t really see the huge benefit (and the gained space is really a non-issue, like several commenters have mentioned,) but it&#8217;s still refreshing to see somebody try a different take on things. This guy, Jef [...]]]></description>
			<content:encoded><![CDATA[<p>Amrinder Sandhu over at A Way Back has attracted a lot of attention with his <a title="Single input login form" href="http://www.awayback.com/single-input-login-form-2/" onclick="javascript:pageTracker._trackPageview('/outbound/article/www.awayback.com');">single input login form</a>. I don&#8217;t really see the huge benefit (and the gained space is really a non-issue, like several commenters have mentioned,) but it&#8217;s still refreshing to see somebody try a different take on things.</p>
<p><img class="alignnone size-full wp-image-965" title="single-input_r5_c1_s11" src="http://www.asgeirhoem.no/wp-content/uploads/2010/10/single-input_r5_c1_s11.png" alt="" width="460" height="220" /><br />
<img class="alignnone size-full wp-image-965" title="single-input_r7_c1_s11" src="http://www.asgeirhoem.no/wp-content/uploads/2010/10/single-input_r7_c1_s11.png" alt="" width="460" height="220" /></p>
<p>This guy, Jef Raskin, believes you should <a href="http://books.google.com/books?id=D39vjmLfO3kC&amp;pg=PA183&amp;lpg=PA183&amp;dq=6-4-3+Simplified+Sign-Ons&amp;source=bl&amp;ots=COuG7YaUV3&amp;sig=oCWKzHth-1yRY6kgxGQ1HHwVoCo&amp;hl=en&amp;ei=dHbFTK3FLsboOaTpxZUM&amp;sa=X&amp;oi=book_result&amp;ct=result&amp;resnum=1&amp;ved=0CBIQ6AEwAA#v=onepage&amp;q&amp;f=false" onclick="javascript:pageTracker._trackPageview('/outbound/article/books.google.com');">cut the username altogether</a>:</p>
<p><a href="http://www.asgeirhoem.no/wp-content/uploads/2010/10/simplified-signons.jpg" ><img class="alignnone size-full wp-image-966" title="simplified-signons" src="http://www.asgeirhoem.no/wp-content/uploads/2010/10/simplified-signons.jpg" alt="" width="678" height="938" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.asgeirhoem.no/single-input-login/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Target the iPad with CSS media queries</title>
		<link>http://blog.asgeirhoem.no/target-the-ipad-with-css-media-queries/</link>
		<comments>http://blog.asgeirhoem.no/target-the-ipad-with-css-media-queries/#comments</comments>
		<pubDate>Wed, 15 Sep 2010 08:27:26 +0000</pubDate>
		<dc:creator>Asgeir</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[CSS3]]></category>
		<category><![CDATA[media queries]]></category>

		<guid isPermaLink="false">http://www.asgeirhoem.no/?p=955</guid>
		<description><![CDATA[How to create iPad specific CSS with media queries.]]></description>
			<content:encoded><![CDATA[<p><img class="alignnone size-full wp-image-956" title="Target the iPad with media queries" src="http://www.asgeirhoem.no/wp-content/uploads/2010/09/apple_ipad.jpg" alt="iPad" /></p>
<p>Media queries can still be confusing for a lot of us, and people are using them differently. When looking for a way to target the iPad specifically, I found a number of different solutions. This is the one I prefer.</p>
<p>Using the <em>max-device-width</em> lets you know that this is a device with a maximum of 1024 pixels. Then use the <em>width </em>property to limit the query to match the size of the iPad, which is 1024 pixels on the long side, and 768 on the short side. Obviously, if there is another tablet with the exact same specifications–and if not, there surely will be–it will display the same styles.</p>
<pre>@media screen and (max-device-width:1024px) and (width:1024px) { /* iPad landscape styles*/ }
@media screen and (max-device-width:1024px) and (width:768px) { /* iPad portrait*/ }</pre>
<p>I believe this is as iPad specific as it gets.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.asgeirhoem.no/target-the-ipad-with-css-media-queries/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Google &#8216;Streaming&#8217; search</title>
		<link>http://blog.asgeirhoem.no/google-streaming-search/</link>
		<comments>http://blog.asgeirhoem.no/google-streaming-search/#comments</comments>
		<pubDate>Tue, 24 Aug 2010 08:38:28 +0000</pubDate>
		<dc:creator>Asgeir</dc:creator>
				<category><![CDATA[Web development]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[search]]></category>

		<guid isPermaLink="false">http://www.asgeirhoem.no/?p=952</guid>
		<description><![CDATA[Search results updated by the key stroke. (via The Register)]]></description>
			<content:encoded><![CDATA[<p><object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="511" height="308" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true" /><param name="allowScriptAccess" value="always" /><param name="src" value="http://www.youtube.com/v/Ty71OxyQKKc&amp;color1=0xb1b1b1&amp;color2=0xd0d0d0&amp;hl=en_US&amp;feature=player_embedded&amp;fs=1" /><param name="allowfullscreen" value="true" /><embed type="application/x-shockwave-flash" width="511" height="308" src="http://www.youtube.com/v/Ty71OxyQKKc&amp;color1=0xb1b1b1&amp;color2=0xd0d0d0&amp;hl=en_US&amp;feature=player_embedded&amp;fs=1" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>
<p>Search results updated by the key stroke. (<a title="Google streaming search test" href="http://www.theregister.co.uk/2010/08/23/google_streaming_search_test/" onclick="javascript:pageTracker._trackPageview('/outbound/article/www.theregister.co.uk');">via The Register</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.asgeirhoem.no/google-streaming-search/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>New type attributes in HTML5 forms</title>
		<link>http://blog.asgeirhoem.no/new-type-attributes-in-html5-forms/</link>
		<comments>http://blog.asgeirhoem.no/new-type-attributes-in-html5-forms/#comments</comments>
		<pubDate>Fri, 20 Aug 2010 09:32:18 +0000</pubDate>
		<dc:creator>Asgeir</dc:creator>
				<category><![CDATA[HTML5]]></category>
		<category><![CDATA[forms]]></category>
		<category><![CDATA[input types]]></category>

		<guid isPermaLink="false">http://www.asgeirhoem.no/?p=943</guid>
		<description><![CDATA[Another extremely handy feature introduced in HTML5, is the ability to more specifically define what kind of information is expected in an input, so that in turn, your handheld device can display the appropriate keyboard. In previous versions of HTML, you were restricted to the text input type for written information. However, you were not [...]]]></description>
			<content:encoded><![CDATA[<p>Another extremely handy feature introduced in HTML5, is the ability to more specifically define what kind of information is expected in an input, so that in turn, your handheld device can display the appropriate keyboard.</p>
<p>In previous versions of HTML, you were restricted to the text input type for written information. However, you were not able to define <em>what kind</em> of information a text field was expecting.</p>
<h2>HTML5 introduces 13-ish new input types</h2>
<p>With <a title="HTML5 input types" href="http://dev.w3.org/html5/markup/input.html#input" onclick="javascript:pageTracker._trackPageview('/outbound/article/dev.w3.org');">the new input types</a>, you can define that aparticular input is expecting a phone number, or an email address, or a URL, or a date, et cetera. The most practical use of the new values, beside the fact that it <em>makes more sense</em>, is that user agents can display the most useful keyboard for the input.</p>
<p><img class="alignnone size-full wp-image-944" title="iphone-keypads" src="http://www.asgeirhoem.no/wp-content/uploads/2010/08/iphone-keypads.png" alt="" width="465" height="328" /></p>
<h2>Full list of HTML5 input types (as of 20. August 2010)</h2>
<p>*   input type=text<br />
*  input type=password<br />
*  input type=checkbox<br />
*  input type=radio<br />
*  input type=button<br />
*  input type=submit<br />
*  input type=reset<br />
*  input type=file<br />
*  input type=hidden<br />
*  input type=image<br />
*  input type=datetime <strong>NEW</strong><br />
*  input type=datetime-local <strong>NEW</strong><br />
*  input type=date <strong>NEW</strong><br />
*  input type=month <strong>NEW</strong><br />
*  input type=time <strong>NEW</strong><br />
*  input type=week <strong>NEW</strong><br />
*  input type=number <strong>NEW</strong><br />
*  input type=range <strong>NEW</strong><br />
*  input type=email <strong>NEW</strong><br />
*  input type=url <strong>NEW</strong><br />
*  input type=search <strong>NEW</strong><br />
*  input type=tel <strong>NEW</strong><br />
*  input type=color <strong>NEW</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.asgeirhoem.no/new-type-attributes-in-html5-forms/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Placeholder text in HTML5 forms</title>
		<link>http://blog.asgeirhoem.no/placeholder-text-in-html5-forms/</link>
		<comments>http://blog.asgeirhoem.no/placeholder-text-in-html5-forms/#comments</comments>
		<pubDate>Thu, 19 Aug 2010 12:13:59 +0000</pubDate>
		<dc:creator>Asgeir</dc:creator>
				<category><![CDATA[HTML5]]></category>
		<category><![CDATA[forms]]></category>
		<category><![CDATA[placeholder]]></category>

		<guid isPermaLink="false">http://www.asgeirhoem.no/?p=937</guid>
		<description><![CDATA[One of the many improvements in HTML5, is the input placeholder attribute. Instead of using javascript to achieve this functionality, you can now specify the placeholder directly in the input tag. Whenever the input is empty and not in focus, the placeholder text will be displayed.]]></description>
			<content:encoded><![CDATA[<p>One of the many improvements in HTML5, is the input <a title="The Placeholder attribute" href="http://www.whatwg.org/specs/web-apps/current-work/multipage/common-input-element-attributes.html#the-placeholder-attribute" onclick="javascript:pageTracker._trackPageview('/outbound/article/www.whatwg.org');">placeholder attribute</a>. Instead of using javascript to achieve this functionality, you can now specify the placeholder directly in the input tag. Whenever the input is empty and not in focus, the placeholder text will be displayed.</p>
<form style="text-align:center; background:#ccc; padding:2em;">
<input type="text" placeholder="Placeholder text" /></form>
<p><img class="alignnone size-full wp-image-938" title="placeholder-html5" src="http://www.asgeirhoem.no/wp-content/uploads/2010/08/placeholder-html5.jpg" alt="" width="572" height="600" /></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.asgeirhoem.no/placeholder-text-in-html5-forms/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Comic Sans, scooch over, we have Rosewood!</title>
		<link>http://blog.asgeirhoem.no/comic-sans-scooch-over-we-have-rosewood/</link>
		<comments>http://blog.asgeirhoem.no/comic-sans-scooch-over-we-have-rosewood/#comments</comments>
		<pubDate>Tue, 17 Aug 2010 09:01:23 +0000</pubDate>
		<dc:creator>Asgeir</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[typography]]></category>
		<category><![CDATA[webfonts]]></category>

		<guid isPermaLink="false">http://www.asgeirhoem.no/?p=930</guid>
		<description><![CDATA[Adobe and Typekit are teaming up to bring some of the world’s most popular, recognizable, and respected fonts to the web. Starting today, you’ll be able to use classics like Adobe Garamond, News Gothic, Myriad, and Minion plus many more on your website — all of them newly optimized and hinted for the screen. I [...]]]></description>
			<content:encoded><![CDATA[<p><a title="Typekit and Adobe" href="http://blog.typekit.com/2010/08/16/typekit-and-adobe/" onclick="javascript:pageTracker._trackPageview('/outbound/article/blog.typekit.com');"><img class="alignnone size-full wp-image-931" title="Adobe + Typekit = Coolio" src="http://www.asgeirhoem.no/wp-content/uploads/2010/08/adobe-preview-blog1.gif" alt="" width="550" height="418" /></a></p>
<blockquote><p><a title="Typekit and Adobe teaming up" href="http://blog.typekit.com/2010/08/16/typekit-and-adobe/" onclick="javascript:pageTracker._trackPageview('/outbound/article/blog.typekit.com');">Adobe and Typekit are teaming up</a> to bring some of the world’s most popular, recognizable, and respected fonts to the web. Starting today, you’ll be able to use classics like Adobe Garamond, News Gothic, Myriad, and Minion plus many more on your website — all of them newly optimized and hinted for the screen.</p></blockquote>
<p>I can not wait to see the personal weblogs about food and babies, with body copy set in Bickham Script with negative leading.</p>
<p>(But seriously, we get Myriad!)</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.asgeirhoem.no/comic-sans-scooch-over-we-have-rosewood/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>CSS3 media queries in older browsers</title>
		<link>http://blog.asgeirhoem.no/css3-media-queries-in-older-browsers/</link>
		<comments>http://blog.asgeirhoem.no/css3-media-queries-in-older-browsers/#comments</comments>
		<pubDate>Wed, 04 Aug 2010 18:36:31 +0000</pubDate>
		<dc:creator>Asgeir</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[CSS3]]></category>
		<category><![CDATA[media queries]]></category>

		<guid isPermaLink="false">http://www.asgeirhoem.no/?p=922</guid>
		<description><![CDATA[css3-mediaqueries-js is a small javascript library that gives you support for CSS3 media queries in older browsers, including IE5+, Firefox 1+ and Safari. Newer versions of Firefox, Opera, Safari and Chrome already offer native support. If you are unfamiliar with media queries, I suggest reading Ethan Marcotte&#8217;s article in a recent issue of A List [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignnone size-full wp-image-924" style="border: 10px solid #eee;" title="CSS3 media queries" src="http://www.asgeirhoem.no/wp-content/uploads/2010/08/mediaqueries.jpg" alt="" width="500" height="200" /></p>
<p><a title="CSS3 media queries javascript library" href="http://code.google.com/p/css3-mediaqueries-js/" onclick="javascript:pageTracker._trackPageview('/outbound/article/code.google.com');">css3-mediaqueries-js</a> is a small javascript library that gives you support for CSS3 media queries in older browsers, including IE5+, Firefox 1+ and Safari. Newer versions of Firefox, Opera, Safari and Chrome already offer native support.</p>
<p>If you are unfamiliar with media queries, I suggest reading <a title="Responsive Web Design" href="http://www.alistapart.com/articles/responsive-web-design/" onclick="javascript:pageTracker._trackPageview('/outbound/article/www.alistapart.com');">Ethan Marcotte&#8217;s article in a recent issue of A List Apart</a>. Speaking of which, I just finished the first A Book Apart by Jeremy Keith. It is a short read, clearly explaining the most important aspects of HTML5.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.asgeirhoem.no/css3-media-queries-in-older-browsers/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Slug as string in WordPress &#8211; the_slug();</title>
		<link>http://blog.asgeirhoem.no/slug-as-string-in-wordpress-the_slug/</link>
		<comments>http://blog.asgeirhoem.no/slug-as-string-in-wordpress-the_slug/#comments</comments>
		<pubDate>Thu, 15 Jul 2010 13:47:11 +0000</pubDate>
		<dc:creator>Asgeir</dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[page slug]]></category>
		<category><![CDATA[the_slug]]></category>

		<guid isPermaLink="false">http://www.asgeirhoem.no/?p=917</guid>
		<description><![CDATA[A quick function for Wordpress that lets you call 'the_slug()' in your template files.]]></description>
			<content:encoded><![CDATA[<p>I needed a way to replace the default page ID in WordPress with the page slug, and discovered <a href="http://wordpress.org/support/topic/128046?replies=9" onclick="javascript:pageTracker._trackPageview('/outbound/article/wordpress.org');">this two year old post</a> in the support forums.</p>
<p>Put this function in your functions.php:</p>
<pre>function the_slug() {
	$post_data = get_post($post-&gt;ID, ARRAY_A);
	$slug = $post_data['post_name'];
	return $slug;
}</pre>
<p>And call it in your template file like this:</p>
<pre>&lt;article id="&lt;?php echo the_slug(); ?&gt;"&gt;</pre>
<p>Simple as that; saves you from writing CSS for randomly numbered IDs.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.asgeirhoem.no/slug-as-string-in-wordpress-the_slug/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

