<?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>Anders Ramsay.com &#187; Adobe</title>
	<atom:link href="http://www.andersramsay.com/category/adobe/feed" rel="self" type="application/rss+xml" />
	<link>http://www.andersramsay.com</link>
	<description>designing user experiences</description>
	<lastBuildDate>Wed, 18 Jan 2012 21:48:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Converting Photoshop files into MXML with Adobe Thermo</title>
		<link>http://www.andersramsay.com/2007/10/06/converting-photoshop-files-into-mxml-with-adobe-thermo</link>
		<comments>http://www.andersramsay.com/2007/10/06/converting-photoshop-files-into-mxml-with-adobe-thermo#comments</comments>
		<pubDate>Sat, 06 Oct 2007 17:07:48 +0000</pubDate>
		<dc:creator>Anders</dc:creator>
				<category><![CDATA[Adobe]]></category>
		<category><![CDATA[Photoshop]]></category>
		<category><![CDATA[Prototyping]]></category>

		<guid isPermaLink="false">http://www.andersramsay.com/2007/10/06/converting-photoshop-files-into-mxml-with-adobe-thermo/</guid>
		<description><![CDATA[Tweet Victor sent me this unofficial sneak peak presentation of Adobe Thermo presented at the MAX 2007 conference in Chicago: Be sure to also check out parts II and III of the video. What&#8217;s truly ground-breaking about this new app is how it allows for transforming what were just layers and objects in Photoshop (and [...]]]></description>
			<content:encoded><![CDATA[<div id="bottomcontainerBox" style="">
			<div style="float:left; width:75px;padding-right:10px; margin:4px 4px 4px 4px;height:30px;">
			<iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.andersramsay.com%2F2007%2F10%2F06%2Fconverting-photoshop-files-into-mxml-with-adobe-thermo&amp;layout=button_count&amp;show_faces=false&amp;width=75&amp;action=like&amp;font=verdana&amp;colorscheme=light&amp;height=21" scrolling="no" frameborder="0" style="border:none; overflow:hidden; width=75px; height:21px;" allowTransparency="true"></iframe></div>
			<div style="float:left; width:60px;padding-right:10px; margin:4px 4px 4px 4px;height:30px;">
			<g:plusone size="medium" href="http://www.andersramsay.com/2007/10/06/converting-photoshop-files-into-mxml-with-adobe-thermo"></g:plusone>
			</div>
			<div style="float:left; width:85px;padding-right:10px; margin:4px 4px 4px 4px;height:30px;">
			<a href="http://twitter.com/share" class="twitter-share-button" data-url="http://www.andersramsay.com/2007/10/06/converting-photoshop-files-into-mxml-with-adobe-thermo"  data-text="Converting Photoshop files into MXML with Adobe Thermo" data-count="horizontal" data-via="andersramsay">Tweet</a>
			</div>			
			</div><div style="clear:both"></div><div style="padding-bottom:4px;"></div><p><a href="http://noisebetweenstations.com">Victor</a> sent me this unofficial sneak peak presentation of <a href="http://labs.adobe.com/wiki/index.php/Thermo">Adobe Thermo</a> presented at the MAX 2007 conference in Chicago:<br />
<object width="425" height="350"><param name="movie" value="http://www.youtube.com/v/lGdr3dCmxe4"></param><param name="wmode" value="transparent"></param><embed src="http://www.youtube.com/v/lGdr3dCmxe4" type="application/x-shockwave-flash" wmode="transparent" width="425" height="350"></embed></object></p>
<p>Be sure to also check out <a href="http://www.youtube.com/watch?v=d9IjZJ0D_bo&#038;mode=related&#038;search=">parts II</a> and <a href="http://www.youtube.com/watch?v=lsfOe_MCEbg&#038;mode=related&#038;search=">III</a> of the video.  What&#8217;s truly ground-breaking about this new app is how it allows for transforming what were just layers and objects in Photoshop (and possibly other apps &#8211; they only used Photoshop in the demo) into actual functioning interface elements on a web page.  In other words, rather than being stuck with whatever ui theme that the framework you are using supports, you can just draw the components and then tell Thermo what part of your drawing should have what functionality. In other words, I can turn a text layer in Photoshop into a text field, or two rectangles into a scroll bar.  All of this is functioning within Flex, meaning that Photoshop files effectively are being converted into MXML. Rather than requiring developers to recreate all the designer&#8217;s efforts, they can now instead allow the designer to bring their work into their framework, and even continue their design work, prototyping behaviors (Thermo has a bunch of cool prototyping features built in, such as easily being able to add sample content) and exploring interactive versions of the formerly static Photoshop files. </p>
<p>In some ways, I am incredibly excited about Thermo, and can&#8217;t wait for the public release.  But the devil will, as they say, be in the details, and that couldn&#8217;t be more true for an application as complex and powerful as this.  The demo looks fantastic,  but so did a demo of iRise, which I saw years ago, only to discover that the real application fell far short of its promises.  Of course, Thermo goes far beyond iRise (after all, iRise is an application simulator, while Thermo in fact is intended to allow for creating real apps), and is many ways a much smarter model, particularly the use of MXML, which allows for much more control and portability.</p>
<p>So, for now, I&#8217;m definitely excited about this tool, but only cautiously so.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.andersramsay.com/2007/10/06/converting-photoshop-files-into-mxml-with-adobe-thermo/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Adobe Fireworks CS3, my new favorite prototyping tool</title>
		<link>http://www.andersramsay.com/2007/04/18/adobe-fireworks-cs3-my-new-favorite-prototyping-tool</link>
		<comments>http://www.andersramsay.com/2007/04/18/adobe-fireworks-cs3-my-new-favorite-prototyping-tool#comments</comments>
		<pubDate>Wed, 18 Apr 2007 19:03:35 +0000</pubDate>
		<dc:creator>Anders</dc:creator>
				<category><![CDATA[Adobe]]></category>
		<category><![CDATA[Fireworks]]></category>

		<guid isPermaLink="false">http://www.andersramsay.com/2007/04/18/adobe-fireworks-cs3-my-new-favorite-prototyping-tool/</guid>
		<description><![CDATA[Tweet I think the actual release of Adobe CS3 is still a couple weeks away [actually, just received an email from Adobe that it's shipping now], but I&#8217;m already reading up on every last tidbit about this great new application framework. As a UX designer, one of my main focuses has been on Fireworks CS3, [...]]]></description>
			<content:encoded><![CDATA[<div id="bottomcontainerBox" style="">
			<div style="float:left; width:75px;padding-right:10px; margin:4px 4px 4px 4px;height:30px;">
			<iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.andersramsay.com%2F2007%2F04%2F18%2Fadobe-fireworks-cs3-my-new-favorite-prototyping-tool&amp;layout=button_count&amp;show_faces=false&amp;width=75&amp;action=like&amp;font=verdana&amp;colorscheme=light&amp;height=21" scrolling="no" frameborder="0" style="border:none; overflow:hidden; width=75px; height:21px;" allowTransparency="true"></iframe></div>
			<div style="float:left; width:60px;padding-right:10px; margin:4px 4px 4px 4px;height:30px;">
			<g:plusone size="medium" href="http://www.andersramsay.com/2007/04/18/adobe-fireworks-cs3-my-new-favorite-prototyping-tool"></g:plusone>
			</div>
			<div style="float:left; width:85px;padding-right:10px; margin:4px 4px 4px 4px;height:30px;">
			<a href="http://twitter.com/share" class="twitter-share-button" data-url="http://www.andersramsay.com/2007/04/18/adobe-fireworks-cs3-my-new-favorite-prototyping-tool"  data-text="Adobe Fireworks CS3, my new favorite prototyping tool" data-count="horizontal" data-via="andersramsay">Tweet</a>
			</div>			
			</div><div style="clear:both"></div><div style="padding-bottom:4px;"></div><p>I think the actual release of Adobe CS3 is still a couple weeks away [actually, just received an email from Adobe that it's shipping <em>now</em>], but I&#8217;m already reading up on every last tidbit about this great new application framework. As a UX designer, one of my main focuses has been on Fireworks CS3, which has added at least two features that I think will make it a very popular rapid prototyping tool.</p>
<p>First, they&#8217;ve added multiple pages and master pages.  That was one the biggest let-downs with previous versions &#8211; even if you did a quick design mockup of a single page, propagating that across multiple pages was a pain in the #@*$! (and one of many reasons I chose to not use FW for prototyping.)  Now you can quickly create a mini-site with common elements on one page.</p>
<p>The other great new feature is smart symbols, which use something called 9-piece slices (?), which basically means that you can resize them without distorting them.  This is a critical feature when working with UI widgets, since you often want to, say, make a text field wider.  And better yet, the app allows for creating your own custom symbols with these properties.  This really sets FW CS3 apart from a lot of other prototyping tools, who often have a fixed library of UI widgets.  I think there was a time when UI widgets were reasonably stable &#8211; as in, you basically had Windows, Mac, and *nix widgets, but all that has changed with the Web itself becoming a platform.  Take for example the reply feature in Gmail&#8230;</p>
<p><img class="alignnone size-full wp-image-586" title="Gmail reply feature" src="http://www.andersramsay.com/wp-content/uploads/2007/04/gmail-reply-feature.gif" alt="Gmail reply feature" width="235" height="249" /></p>
<p>This isn&#8217;t exactly a standard widget.  Sure, you could probably re-create the functionality represented here with a vanilla drop-down, but it would just not have the same elegant feel. With FW CS3, you could basically draw whatever kind of element you want and then turn it into a Smart Symbol, i.e. a widget in the UXD world.</p>
<p>Btw, I think it&#8217;s starting to sound like a traveling salesman for Adobe (but wait, there&#8217;s more!) &#8211; I&#8217;m not &#8211; it&#8217;s just that I&#8217;ve been waiting so long for something like this and all the other tools that seem to do what FW CS3 claims to do have turned out to be duds.  Of course, this app could be a dud as well, but I have a good feeling that it won&#8217;t be &#8211; keeping my fingers crossed&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.andersramsay.com/2007/04/18/adobe-fireworks-cs3-my-new-favorite-prototyping-tool/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Adobe CS3 and UXD workflow</title>
		<link>http://www.andersramsay.com/2007/03/27/adobe-cs3-and-uxd-workflow</link>
		<comments>http://www.andersramsay.com/2007/03/27/adobe-cs3-and-uxd-workflow#comments</comments>
		<pubDate>Tue, 27 Mar 2007 20:41:00 +0000</pubDate>
		<dc:creator>Anders</dc:creator>
				<category><![CDATA[Adobe]]></category>

		<guid isPermaLink="false">http://www.andersramsay.com/2007/03/27/adobe-cs3-and-uxd-workflow/</guid>
		<description><![CDATA[Tweet So I&#8217;m currently watching the live webcast of the Adobe CS3 launch &#8211; the most exciting part so far, from the perspective of a User Experience is about the focus on prototyping &#8211; in other words, integrating features into the tool that are specifically intended for presenting unfinished work to clients. Until now, major [...]]]></description>
			<content:encoded><![CDATA[<div id="bottomcontainerBox" style="">
			<div style="float:left; width:75px;padding-right:10px; margin:4px 4px 4px 4px;height:30px;">
			<iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.andersramsay.com%2F2007%2F03%2F27%2Fadobe-cs3-and-uxd-workflow&amp;layout=button_count&amp;show_faces=false&amp;width=75&amp;action=like&amp;font=verdana&amp;colorscheme=light&amp;height=21" scrolling="no" frameborder="0" style="border:none; overflow:hidden; width=75px; height:21px;" allowTransparency="true"></iframe></div>
			<div style="float:left; width:60px;padding-right:10px; margin:4px 4px 4px 4px;height:30px;">
			<g:plusone size="medium" href="http://www.andersramsay.com/2007/03/27/adobe-cs3-and-uxd-workflow"></g:plusone>
			</div>
			<div style="float:left; width:85px;padding-right:10px; margin:4px 4px 4px 4px;height:30px;">
			<a href="http://twitter.com/share" class="twitter-share-button" data-url="http://www.andersramsay.com/2007/03/27/adobe-cs3-and-uxd-workflow"  data-text="Adobe CS3 and UXD workflow" data-count="horizontal" data-via="andersramsay">Tweet</a>
			</div>			
			</div><div style="clear:both"></div><div style="padding-bottom:4px;"></div><p>So I&#8217;m currently watching the <a href="http://www.adobe.com/products/creativesuite/launchevent/webcast/">live webcast of the Adobe CS3 launch </a> &#8211; the most exciting part so far, from the perspective of a User Experience is about the focus on prototyping &#8211; in other words, integrating features into the tool that are specifically intended for presenting unfinished work to clients.  Until now, major apps like Photoshop and Dreamweaver are all about creating the finished product.  While that&#8217;s all good and well, the reality is of course that to get to that final deliverable, you need to iterate through a series of increasingly refined concepts.  For me, this is potentially super-exciting, since I&#8217;ve already been hacking ways of presenting work in progress for clients with these tools, and will now have tools that were actually designed for this(!)  For example, you&#8217;ll be able to insert sketches of designs and then add hotspots to them to be able to click through the various sketched pages with a user or a client. That&#8217;s of course not too amazing (and there are agile tools out there that already support it), but apparently, from what I could glean, this is all integrated into a workflow in which you iterate into your final design.  In other words, Adobe is recognizing UXD as part of the production process and integrating it into their tools &#8211; but I&#8217;m going to want to play around with an actual tool until I uncork the champagne&#8230;.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.andersramsay.com/2007/03/27/adobe-cs3-and-uxd-workflow/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

