<?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: Storyboarding Rich Internet Applications with Visio</title>
	<atom:link href="http://boxesandarrows.com/storyboarding-rich-internet-applications-with-visio/feed/" rel="self" type="application/rss+xml" />
	<link>http://boxesandarrows.com/storyboarding-rich-internet-applications-with-visio/</link>
	<description>Boxes and Arrows is devoted to the practice, innovation, and discussion of design; including graphic design, interaction design, information architecture and the design of business.</description>
	<lastBuildDate>Wed, 15 May 2013 11:41:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: vanderwal</title>
		<link>http://boxesandarrows.com/storyboarding-rich-internet-applications-with-visio/#comment-5725</link>
		<dc:creator>vanderwal</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/storyboarding-rich-internet-applications-with-visio/#comment-5725</guid>
		<description><![CDATA[Hopefully this is the tip of the iceberg for rich internet documentation pieces in Boxes and Arrows.  We have been dealing with Flash for six years as a major rich interface component (that was Flash 3 or 4 in 1999 that really tipped things).  We now have AJAX and very little has changed on the documentation front.  Nearly every IA or UX designer conversation the past 12 to 18 months has included a question about documenting rich interfaces.  

Now there is one article to point that I feel is worth reading and sharing.  It is long past time.]]></description>
		<content:encoded><![CDATA[<p>Hopefully this is the tip of the iceberg for rich internet documentation pieces in Boxes and Arrows.  We have been dealing with Flash for six years as a major rich interface component (that was Flash 3 or 4 in 1999 that really tipped things).  We now have AJAX and very little has changed on the documentation front.  Nearly every IA or UX designer conversation the past 12 to 18 months has included a question about documenting rich interfaces.  </p>
<p>Now there is one article to point that I feel is worth reading and sharing.  It is long past time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: billwscott</title>
		<link>http://boxesandarrows.com/storyboarding-rich-internet-applications-with-visio/#comment-5726</link>
		<dc:creator>billwscott</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/storyboarding-rich-internet-applications-with-visio/#comment-5726</guid>
		<description><![CDATA[Looks like a couple of the original comments got lost since the posting of this article. In those comments some good points were made about other tools like Fireworks, etc. In those comments, I mention some background information.

I discuss the full Visio toolkit on my blog at:
http://looksgoodworkswell.blogspot.com/2005/11/visio-wireframe-toolkit-for-download.html

I also discuss briefly using Photoshop CS2 with animation &amp; layered comps at:
http://looksgoodworkswell.blogspot.com/2005/11/animating-interactions-with-photoshop.html

The time is ripe for a tool to be created that allows us to take our design artifacts and essentially animate them into life. Being able to express designs as storyboards that can be animated or shown as storyboard &quot;walls&quot; would be awesome in a design tool. Being able to reverse engineer sites &amp; interactions into storyboards would be a great way to share ideas.]]></description>
		<content:encoded><![CDATA[<p>Looks like a couple of the original comments got lost since the posting of this article. In those comments some good points were made about other tools like Fireworks, etc. In those comments, I mention some background information.</p>
<p>I discuss the full Visio toolkit on my blog at:<br />
<a href="http://looksgoodworkswell.blogspot.com/2005/11/visio-wireframe-toolkit-for-download.html" rel="nofollow">http://looksgoodworkswell.blogspot.com/2005/11/visio-wireframe-toolkit-for-download.html</a></p>
<p>I also discuss briefly using Photoshop CS2 with animation &amp; layered comps at:<br />
<a href="http://looksgoodworkswell.blogspot.com/2005/11/animating-interactions-with-photoshop.html" rel="nofollow">http://looksgoodworkswell.blogspot.com/2005/11/animating-interactions-with-photoshop.html</a></p>
<p>The time is ripe for a tool to be created that allows us to take our design artifacts and essentially animate them into life. Being able to express designs as storyboards that can be animated or shown as storyboard &#8220;walls&#8221; would be awesome in a design tool. Being able to reverse engineer sites &amp; interactions into storyboards would be a great way to share ideas.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lars</title>
		<link>http://boxesandarrows.com/storyboarding-rich-internet-applications-with-visio/#comment-5727</link>
		<dc:creator>lars</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/storyboarding-rich-internet-applications-with-visio/#comment-5727</guid>
		<description><![CDATA[Hi Bill

I&#039;m Lars Pind, the guy responsible for the code behind this site.

Yes, there were indeed 4 comments that were lost in the transition. They&#039;ve been brought back now, and they appear at the top, like they should&#039;ve from the start.

Sorry about that, and thanks for letting us know :)]]></description>
		<content:encoded><![CDATA[<p>Hi Bill</p>
<p>I&#8217;m Lars Pind, the guy responsible for the code behind this site.</p>
<p>Yes, there were indeed 4 comments that were lost in the transition. They&#8217;ve been brought back now, and they appear at the top, like they should&#8217;ve from the start.</p>
<p>Sorry about that, and thanks for letting us know <img src='http://www-boxesandarrows-com.zippykid.netdna-cdn.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alok</title>
		<link>http://boxesandarrows.com/storyboarding-rich-internet-applications-with-visio/#comment-5728</link>
		<dc:creator>alok</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/storyboarding-rich-internet-applications-with-visio/#comment-5728</guid>
		<description><![CDATA[Great Article and very relevant to practical use. 

I would like to add that the change from PIA to RIA doesn&#039;t just mean direct manipulation of page elements but a change in what is destination for the user. 

Previous destination was like navigating through listing pages to reach a product detail page and then configure the product, go to shopping cart and so on. With RIA the sense of destination is changed and then users manipulate that destination space. So they do not &quot;move across spaces&quot; but they manipulate objects in same space. 

I belive the we are in transition phase rightnow and are merging current interaction mechanism with what RIA offfers, as we move forward we&#039;ll see fundamental interaction and navigation mechanisms changing.

I am writing an article (hopefuly soon) about this on my blog (http://www.iprincipia.com) in more detail.

Cheers
Alok Jain]]></description>
		<content:encoded><![CDATA[<p>Great Article and very relevant to practical use. </p>
<p>I would like to add that the change from PIA to RIA doesn&#8217;t just mean direct manipulation of page elements but a change in what is destination for the user. </p>
<p>Previous destination was like navigating through listing pages to reach a product detail page and then configure the product, go to shopping cart and so on. With RIA the sense of destination is changed and then users manipulate that destination space. So they do not &#8220;move across spaces&#8221; but they manipulate objects in same space. </p>
<p>I belive the we are in transition phase rightnow and are merging current interaction mechanism with what RIA offfers, as we move forward we&#8217;ll see fundamental interaction and navigation mechanisms changing.</p>
<p>I am writing an article (hopefuly soon) about this on my blog (<a href="http://www.iprincipia.com" rel="nofollow">http://www.iprincipia.com</a>) in more detail.</p>
<p>Cheers<br />
Alok Jain</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tansht</title>
		<link>http://boxesandarrows.com/storyboarding-rich-internet-applications-with-visio/#comment-5729</link>
		<dc:creator>tansht</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/storyboarding-rich-internet-applications-with-visio/#comment-5729</guid>
		<description><![CDATA[Very interesting article and usefull tool. But I&#039;m wondering how to run the slide show according to there layers. Double click the name of layer? 
Cheers, David]]></description>
		<content:encoded><![CDATA[<p>Very interesting article and usefull tool. But I&#8217;m wondering how to run the slide show according to there layers. Double click the name of layer?<br />
Cheers, David</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gclaes</title>
		<link>http://boxesandarrows.com/storyboarding-rich-internet-applications-with-visio/#comment-5730</link>
		<dc:creator>gclaes</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/storyboarding-rich-internet-applications-with-visio/#comment-5730</guid>
		<description><![CDATA[Hi Bill, I like the idea, but I prefer to show a client the wireframes in Full Screen view. Is there a way to go through the storyboard by just clicking (single) on the storyboard steps (like hyperlinks) in Full Screen view mode?

Cheers, Geert]]></description>
		<content:encoded><![CDATA[<p>Hi Bill, I like the idea, but I prefer to show a client the wireframes in Full Screen view. Is there a way to go through the storyboard by just clicking (single) on the storyboard steps (like hyperlinks) in Full Screen view mode?</p>
<p>Cheers, Geert</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: billwscott</title>
		<link>http://boxesandarrows.com/storyboarding-rich-internet-applications-with-visio/#comment-5731</link>
		<dc:creator>billwscott</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/storyboarding-rich-internet-applications-with-visio/#comment-5731</guid>
		<description><![CDATA[David

Yes, you need to double-click on each of the storyboard steps (name or scenario step). The reason for this is Visio allows you to associate a macro with a double-click event. A hyperlink links to a page, anchor, etc.

I wired the storyboard stencils to use the double-click event.]]></description>
		<content:encoded><![CDATA[<p>David</p>
<p>Yes, you need to double-click on each of the storyboard steps (name or scenario step). The reason for this is Visio allows you to associate a macro with a double-click event. A hyperlink links to a page, anchor, etc.</p>
<p>I wired the storyboard stencils to use the double-click event.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cmodien</title>
		<link>http://boxesandarrows.com/storyboarding-rich-internet-applications-with-visio/#comment-5732</link>
		<dc:creator>cmodien</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/storyboarding-rich-internet-applications-with-visio/#comment-5732</guid>
		<description><![CDATA[While this example is fairly trivial, more complex interactions can be built. In addition multiple storyboards can be used to represent different use cases. This is important for showing error conditions as well as different edge-cases.

Why not just a visio uml diagram to illustrate the different use cases?  What&#039;s the advantage?]]></description>
		<content:encoded><![CDATA[<p>While this example is fairly trivial, more complex interactions can be built. In addition multiple storyboards can be used to represent different use cases. This is important for showing error conditions as well as different edge-cases.</p>
<p>Why not just a visio uml diagram to illustrate the different use cases?  What&#8217;s the advantage?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cmodien</title>
		<link>http://boxesandarrows.com/storyboarding-rich-internet-applications-with-visio/#comment-5733</link>
		<dc:creator>cmodien</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/storyboarding-rich-internet-applications-with-visio/#comment-5733</guid>
		<description><![CDATA[&gt;&gt;&quot;While this example is fairly trivial, more complex interactions can be built. In addition multiple storyboards can be used to represent different use cases. This is important for showing error conditions as well as different edge-cases.&quot; &gt;&gt;

Why not just a visio uml diagram to illustrate the different use cases? What&#039;s the advantage?]]></description>
		<content:encoded><![CDATA[<p>&gt;&gt;&#8221;While this example is fairly trivial, more complex interactions can be built. In addition multiple storyboards can be used to represent different use cases. This is important for showing error conditions as well as different edge-cases.&#8221; &gt;&gt;</p>
<p>Why not just a visio uml diagram to illustrate the different use cases? What&#8217;s the advantage?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tonant</title>
		<link>http://boxesandarrows.com/storyboarding-rich-internet-applications-with-visio/#comment-5734</link>
		<dc:creator>tonant</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/storyboarding-rich-internet-applications-with-visio/#comment-5734</guid>
		<description><![CDATA[I really enjoyed the opening explination of PIAs and RIAs - very useful stuff. I am also a great believer in wireframes and for that matter any kind of visually orientated process. However coming from years of in the trenches services time I think I would think twice at even suggesting this process due to the work load increase it would demand.

Really I believe the future of elaboration is in specifically designed specification and simulation tools rather than technical drawing tools such as Viso, Illustrator and the like. These new tools hold the promise of natively supporting good design patterns and automations to reduce workload.

The big issue really is - what are good design patterns for RIAs? An article on this i&#039;m sure would garner great interest :)]]></description>
		<content:encoded><![CDATA[<p>I really enjoyed the opening explination of PIAs and RIAs &#8211; very useful stuff. I am also a great believer in wireframes and for that matter any kind of visually orientated process. However coming from years of in the trenches services time I think I would think twice at even suggesting this process due to the work load increase it would demand.</p>
<p>Really I believe the future of elaboration is in specifically designed specification and simulation tools rather than technical drawing tools such as Viso, Illustrator and the like. These new tools hold the promise of natively supporting good design patterns and automations to reduce workload.</p>
<p>The big issue really is &#8211; what are good design patterns for RIAs? An article on this i&#8217;m sure would garner great interest <img src='http://www-boxesandarrows-com.zippykid.netdna-cdn.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
