<?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"
	>
<channel>
	<title>Comments on: Prototyping for Designers</title>
	<atom:link href="http://www.adaptivepath.com/blog/2007/09/13/prototyping-for-designers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adaptivepath.com/blog/2007/09/13/prototyping-for-designers/</link>
	<description>Adaptive Path Blog</description>
	<pubDate>Thu, 04 Dec 2008 23:55:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Al Abut</title>
		<link>http://www.adaptivepath.com/blog/2007/09/13/prototyping-for-designers/#comment-126230</link>
		<dc:creator>Al Abut</dc:creator>
		<pubDate>Sat, 15 Sep 2007 05:30:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2007/09/13/prototyping-for-designers/#comment-126230</guid>
		<description>What's great about this is that it's such a pain to prototype anything with state changes compared to static content-centric layouts, whether the change is because of Ajax or Flash or whatever. Storyboarding can work for something with a linear and unchanging sequence, like animation or video, but breaks down with interactive content with multiple flows or outcomes. This is great!</description>
		<content:encoded><![CDATA[<p>What&#8217;s great about this is that it&#8217;s such a pain to prototype anything with state changes compared to static content-centric layouts, whether the change is because of Ajax or Flash or whatever. Storyboarding can work for something with a linear and unchanging sequence, like animation or video, but breaks down with interactive content with multiple flows or outcomes. This is great!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Internet Brain &#187; Prototyping for Designers</title>
		<link>http://www.adaptivepath.com/blog/2007/09/13/prototyping-for-designers/#comment-125952</link>
		<dc:creator>Internet Brain &#187; Prototyping for Designers</dc:creator>
		<pubDate>Fri, 14 Sep 2007 18:13:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2007/09/13/prototyping-for-designers/#comment-125952</guid>
		<description>[...] adaptive path » blog » david verba » Prototyping for Designers   I was at Rich Web Experience last week and Yahoo’s Bill Scott presented a session on his recently unveiled prototyping library. It’s called Protoscript and he’s written a blog post as well. Both of these sources get technical fairly quickly so the implications may not be immediately obvious to non-programmers. Even though Protoscript is still very much a work in progress and there’s some distance between it’s current state and Bill’s vision for it’s future, the opportunities it opens up are are exciting. [...]</description>
		<content:encoded><![CDATA[<p>[...] adaptive path » blog » david verba » Prototyping for Designers   I was at Rich Web Experience last week and Yahoo’s Bill Scott presented a session on his recently unveiled prototyping library. It’s called Protoscript and he’s written a blog post as well. Both of these sources get technical fairly quickly so the implications may not be immediately obvious to non-programmers. Even though Protoscript is still very much a work in progress and there’s some distance between it’s current state and Bill’s vision for it’s future, the opportunities it opens up are are exciting. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Barr</title>
		<link>http://www.adaptivepath.com/blog/2007/09/13/prototyping-for-designers/#comment-125926</link>
		<dc:creator>Tom Barr</dc:creator>
		<pubDate>Fri, 14 Sep 2007 16:56:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2007/09/13/prototyping-for-designers/#comment-125926</guid>
		<description>Clients and designers very often don't know what they want until they see it. Tools like this will get them closer to asking for what they really want. I have found that it is often a good excercise to have them develop forms, copy, and layout in a static mode (say Photoshop image or Dreamweaver HTML) and then have them get estimates based on this near net condition. They can be Dr. Frankenstein and the project managers and developers can be the Igor that makes it come alive. It would be nice if this took off and it became a verb: "hey, photoscript and we will get you a quote..."</description>
		<content:encoded><![CDATA[<p>Clients and designers very often don&#8217;t know what they want until they see it. Tools like this will get them closer to asking for what they really want. I have found that it is often a good excercise to have them develop forms, copy, and layout in a static mode (say Photoshop image or Dreamweaver HTML) and then have them get estimates based on this near net condition. They can be Dr. Frankenstein and the project managers and developers can be the Igor that makes it come alive. It would be nice if this took off and it became a verb: &#8220;hey, photoscript and we will get you a quote&#8230;&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas</title>
		<link>http://www.adaptivepath.com/blog/2007/09/13/prototyping-for-designers/#comment-125508</link>
		<dc:creator>Thomas</dc:creator>
		<pubDate>Thu, 13 Sep 2007 23:27:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/2007/09/13/prototyping-for-designers/#comment-125508</guid>
		<description>There's a germ of a great idea in Protoscript: that you can describe most interaction on a page with a combination of Element+Event+Response, but the syntax for it is too fiddly right now. It's just as easy to learn some basic jQuery or Prototype to get this level of interaction. Hopefully a GUI would simplify things, but there is a long (long) history of this kind of product where a designer just drags and drops a behavior onto an object and presto! They usually don't really work all that well, either they're way too simple or way too complex. 

Also: GRR! "distance between it’s current state and Bill’s vision for it’s future," That should be "its" in both cases, not "it's."</description>
		<content:encoded><![CDATA[<p>There&#8217;s a germ of a great idea in Protoscript: that you can describe most interaction on a page with a combination of Element+Event+Response, but the syntax for it is too fiddly right now. It&#8217;s just as easy to learn some basic jQuery or Prototype to get this level of interaction. Hopefully a GUI would simplify things, but there is a long (long) history of this kind of product where a designer just drags and drops a behavior onto an object and presto! They usually don&#8217;t really work all that well, either they&#8217;re way too simple or way too complex. </p>
<p>Also: GRR! &#8220;distance between it’s current state and Bill’s vision for it’s future,&#8221; That should be &#8220;its&#8221; in both cases, not &#8220;it&#8217;s.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
