<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: State Level Wireflows and Transitions</title>
	<atom:link href="http://wireframes.linowski.ca/2009/02/state-level-wireflows-and-transitions/feed/" rel="self" type="application/rss+xml" />
	<link>http://wireframes.linowski.ca/2009/02/state-level-wireflows-and-transitions/</link>
	<description>Because every IA has something funky up their sleeve</description>
	<lastBuildDate>Wed, 28 Jul 2010 06:45:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Multiple Element Changes Using Miniframe References &#8250; Wireframes Magazine</title>
		<link>http://wireframes.linowski.ca/2009/02/state-level-wireflows-and-transitions/comment-page-1/#comment-229</link>
		<dc:creator>Multiple Element Changes Using Miniframe References &#8250; Wireframes Magazine</dc:creator>
		<pubDate>Thu, 19 Feb 2009 16:07:30 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=248#comment-229</guid>
		<description>[...] full page and thus decreases effort and increases document flexibility. Fabian has achieved this by combining state based wireflows with miniframes which act as references for the elements which do change. Overall, this document [...]</description>
		<content:encoded><![CDATA[<p>[...] full page and thus decreases effort and increases document flexibility. Fabian has achieved this by combining state based wireflows with miniframes which act as references for the elements which do change. Overall, this document [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: juarezpaf</title>
		<link>http://wireframes.linowski.ca/2009/02/state-level-wireflows-and-transitions/comment-page-1/#comment-154</link>
		<dc:creator>juarezpaf</dc:creator>
		<pubDate>Mon, 09 Feb 2009 11:52:16 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=248#comment-154</guid>
		<description>Hummm... This way to prototype transitions is great. I don&#039;t see frequently this kind of thing here inf my jobs, but I&#039;ll send this article for my partners and show to them the importance to make it. 
I agreed with Tyeshasnow about conversation between devs and interaction designers. 
Keep movin guys! 
 </description>
		<content:encoded><![CDATA[<p>Hummm&#8230; This way to prototype transitions is great. I don&#039;t see frequently this kind of thing here inf my jobs, but I&#039;ll send this article for my partners and show to them the importance to make it.<br />
I agreed with Tyeshasnow about conversation between devs and interaction designers.<br />
Keep movin guys!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tyeshasnow</title>
		<link>http://wireframes.linowski.ca/2009/02/state-level-wireflows-and-transitions/comment-page-1/#comment-146</link>
		<dc:creator>Tyeshasnow</dc:creator>
		<pubDate>Fri, 06 Feb 2009 20:55:41 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=248#comment-146</guid>
		<description>We were just talking with a client today about how scope creep can happen so quickly because something is represented in a layout but not fully explained/approved by the devs. Using techniques like this allows the devs to go &quot;oh, wait a minute, if we display like &lt;blank&gt; it will mean &lt;blank&gt;, so you might want to reconsider that design/interaction choice&quot;.  I often find doing something like this is a good test for me too.  Is what I am thinking really going to work? </description>
		<content:encoded><![CDATA[<p>We were just talking with a client today about how scope creep can happen so quickly because something is represented in a layout but not fully explained/approved by the devs. Using techniques like this allows the devs to go &quot;oh, wait a minute, if we display like &lt;blank&gt; it will mean &lt;blank&gt;, so you might want to reconsider that design/interaction choice&quot;.  I often find doing something like this is a good test for me too.  Is what I am thinking really going to work?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcus</title>
		<link>http://wireframes.linowski.ca/2009/02/state-level-wireflows-and-transitions/comment-page-1/#comment-137</link>
		<dc:creator>Marcus</dc:creator>
		<pubDate>Thu, 05 Feb 2009 03:17:51 +0000</pubDate>
		<guid isPermaLink="false">http://wireframes.linowski.ca/?p=248#comment-137</guid>
		<description>I think this is an excellent way to prototype transitions/behaviours without needing to go to code (of course, it does kind of imply an understanding of the medium your design for - what events are available, etc.).  
And your last paragraph, in my experience, is right on the money.  
 
Thanks for sharing. Marcus </description>
		<content:encoded><![CDATA[<p>I think this is an excellent way to prototype transitions/behaviours without needing to go to code (of course, it does kind of imply an understanding of the medium your design for &#8211; what events are available, etc.).<br />
And your last paragraph, in my experience, is right on the money.  </p>
<p>Thanks for sharing. Marcus</p>
]]></content:encoded>
	</item>
</channel>
</rss>
