<?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: New Adobe XD pub, thoughts on CS4 UI</title>
	<atom:link href="http://blogs.adobe.com/jnack/2008/10/new_adobe_xd_pub_thoughts_on_cs4_ui.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blogs.adobe.com/jnack/2008/10/new_adobe_xd_pub_thoughts_on_cs4_ui.html</link>
	<description></description>
	<lastBuildDate>Wed, 22 May 2013 19:45:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Rob Moir</title>
		<link>http://blogs.adobe.com/jnack/2008/10/new_adobe_xd_pub_thoughts_on_cs4_ui.html#comment-9740</link>
		<dc:creator>Rob Moir</dc:creator>
		<pubDate>Tue, 27 Jan 2009 14:35:27 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/10/new-adobe-xd-pub-thoughts-on-cs4-ui.html#comment-9740</guid>
		<description><![CDATA[Inspire - how interesting. It&#039;s like a website but broken. This is easily some of the worst webdesign I&#039;ve ever seen, with the possible exception of anything from geocities back in the old days.
Why in God&#039;s name do I need to load flex to view a simple blog? The borked up UI in CS4 is starting to make a lot of sense to me now. *sigh*.
]]></description>
		<content:encoded><![CDATA[<p>Inspire &#8211; how interesting. It&#8217;s like a website but broken. This is easily some of the worst webdesign I&#8217;ve ever seen, with the possible exception of anything from geocities back in the old days.<br />
Why in God&#8217;s name do I need to load flex to view a simple blog? The borked up UI in CS4 is starting to make a lot of sense to me now. *sigh*.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aran</title>
		<link>http://blogs.adobe.com/jnack/2008/10/new_adobe_xd_pub_thoughts_on_cs4_ui.html#comment-9739</link>
		<dc:creator>Aran</dc:creator>
		<pubDate>Wed, 15 Oct 2008 16:08:43 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/10/new-adobe-xd-pub-thoughts-on-cs4-ui.html#comment-9739</guid>
		<description><![CDATA[I tried to email the team through the suggestions link within the Inspire app, but the email address doesn&#039;t work!
Delivery to the following recipient failed permanently:
inspiresuggestions@adobe.com
550 No such user
John, can you pass on to the team that this doesn&#039;t work?
Cheers.
]]></description>
		<content:encoded><![CDATA[<p>I tried to email the team through the suggestions link within the Inspire app, but the email address doesn&#8217;t work!<br />
Delivery to the following recipient failed permanently:<br />
<a href="mailto:inspiresuggestions@adobe.com">inspiresuggestions@adobe.com</a><br />
550 No such user<br />
John, can you pass on to the team that this doesn&#8217;t work?<br />
Cheers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://blogs.adobe.com/jnack/2008/10/new_adobe_xd_pub_thoughts_on_cs4_ui.html#comment-9738</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Wed, 15 Oct 2008 14:47:46 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/10/new-adobe-xd-pub-thoughts-on-cs4-ui.html#comment-9738</guid>
		<description><![CDATA[Wow, what a horrible mess of a UI for a design team site. The site steals the browser context menu, which I depend on for many functions. Not all text is selectable. Mouse scrolling is inverted in Opera (so much for platform independence). I hate to imagine how consistently it handles disabled interfaces like Voice-over. Fine, it is some sort of beta testbed for Flex, but that is not useable and only puts many of us off ever visiting it.
Their reply to the criticism they&#039;ve received is partly reassuring, but trivializes the work they need to e.g. make my goddamn context menu work as it does on *every* other web site. User unfriendly sums it up perfectly...
]]></description>
		<content:encoded><![CDATA[<p>Wow, what a horrible mess of a UI for a design team site. The site steals the browser context menu, which I depend on for many functions. Not all text is selectable. Mouse scrolling is inverted in Opera (so much for platform independence). I hate to imagine how consistently it handles disabled interfaces like Voice-over. Fine, it is some sort of beta testbed for Flex, but that is not useable and only puts many of us off ever visiting it.<br />
Their reply to the criticism they&#8217;ve received is partly reassuring, but trivializes the work they need to e.g. make my goddamn context menu work as it does on *every* other web site. User unfriendly sums it up perfectly&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ann Shelbourne</title>
		<link>http://blogs.adobe.com/jnack/2008/10/new_adobe_xd_pub_thoughts_on_cs4_ui.html#comment-9737</link>
		<dc:creator>Ann Shelbourne</dc:creator>
		<pubDate>Wed, 15 Oct 2008 08:12:13 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/10/new-adobe-xd-pub-thoughts-on-cs4-ui.html#comment-9737</guid>
		<description><![CDATA[Actually, you CAN increase type-size: there is a &quot;+&quot; Button right at the top of their page.
]]></description>
		<content:encoded><![CDATA[<p>Actually, you CAN increase type-size: there is a &#8220;+&#8221; Button right at the top of their page.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NO RSS</title>
		<link>http://blogs.adobe.com/jnack/2008/10/new_adobe_xd_pub_thoughts_on_cs4_ui.html#comment-9736</link>
		<dc:creator>NO RSS</dc:creator>
		<pubDate>Wed, 15 Oct 2008 03:17:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/10/new-adobe-xd-pub-thoughts-on-cs4-ui.html#comment-9736</guid>
		<description><![CDATA[The biggest insult of all perhaps, you can&#039;t even bypass that HORRIBLE site and read via RSS… because they RSS articles are all truncated after about a paragraph.
What complete garbage
]]></description>
		<content:encoded><![CDATA[<p>The biggest insult of all perhaps, you can&#8217;t even bypass that HORRIBLE site and read via RSS… because they RSS articles are all truncated after about a paragraph.<br />
What complete garbage</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Terry</title>
		<link>http://blogs.adobe.com/jnack/2008/10/new_adobe_xd_pub_thoughts_on_cs4_ui.html#comment-9735</link>
		<dc:creator>Terry</dc:creator>
		<pubDate>Wed, 15 Oct 2008 02:26:55 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/10/new-adobe-xd-pub-thoughts-on-cs4-ui.html#comment-9735</guid>
		<description><![CDATA[Why on earth did they make this in flash?
I find that quite worrying from a UI team.
You really should know where flash is wanted and where it should stay well away.
I mean yesterday I was working in fireworks and the palettes reset for some reason and I noticed the &quot;Autoshape Properties&quot; palette… a clunky weird mess made in flash. This made me worry about your new Photoshop flash panels, I mean looking at this the font rendering is significantly worse than my OS font rendering, the combo box and controls are neither standard to my OS or the rest of fireworks, scrollbar is weird clunky and different.
Why on earth would you want weird clunky trash like that in any product? Let alone Photoshop
]]></description>
		<content:encoded><![CDATA[<p>Why on earth did they make this in flash?<br />
I find that quite worrying from a UI team.<br />
You really should know where flash is wanted and where it should stay well away.<br />
I mean yesterday I was working in fireworks and the palettes reset for some reason and I noticed the &#8220;Autoshape Properties&#8221; palette… a clunky weird mess made in flash. This made me worry about your new Photoshop flash panels, I mean looking at this the font rendering is significantly worse than my OS font rendering, the combo box and controls are neither standard to my OS or the rest of fireworks, scrollbar is weird clunky and different.<br />
Why on earth would you want weird clunky trash like that in any product? Let alone Photoshop</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bjoern</title>
		<link>http://blogs.adobe.com/jnack/2008/10/new_adobe_xd_pub_thoughts_on_cs4_ui.html#comment-9734</link>
		<dc:creator>Bjoern</dc:creator>
		<pubDate>Wed, 15 Oct 2008 01:35:03 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/10/new-adobe-xd-pub-thoughts-on-cs4-ui.html#comment-9734</guid>
		<description><![CDATA[As much as I like the fact that you create such a blog - is barely usable for me! I&#039;m using NetNewsWire for reading blogs and when I open an entry for this blog, it takes me to the start page!!! the fact that it&#039;s built in Flex prevents NetNewsWire to create a nice Thumbnail - instead I only see the gray background color. When I open the site it sometimes is not displayed at all and then takes me back to the start page... this is incredibly unusable! I sincerely wouldn&#039;t mind Flex as long as it just works... it doesn&#039;t in this case.
]]></description>
		<content:encoded><![CDATA[<p>As much as I like the fact that you create such a blog &#8211; is barely usable for me! I&#8217;m using NetNewsWire for reading blogs and when I open an entry for this blog, it takes me to the start page!!! the fact that it&#8217;s built in Flex prevents NetNewsWire to create a nice Thumbnail &#8211; instead I only see the gray background color. When I open the site it sometimes is not displayed at all and then takes me back to the start page&#8230; this is incredibly unusable! I sincerely wouldn&#8217;t mind Flex as long as it just works&#8230; it doesn&#8217;t in this case.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jerry</title>
		<link>http://blogs.adobe.com/jnack/2008/10/new_adobe_xd_pub_thoughts_on_cs4_ui.html#comment-9733</link>
		<dc:creator>Jerry</dc:creator>
		<pubDate>Wed, 15 Oct 2008 00:45:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/10/new-adobe-xd-pub-thoughts-on-cs4-ui.html#comment-9733</guid>
		<description><![CDATA[I&#039;m not going to rant off like Hale, but I agree with him on key points. Is there a reason why that blog had to be done with Flash/Flex/whatever-it-is? Could it not be realized with HTML? It&#039;s just some text, a few images and videos, so it seems like using a hammer to swat a fly.
I understand if it is a tech demo, but I certainly hope this is not Adobe&#039;s future vision of the internet. We dropped full-flash sites a few years ago when we realized it was a bad idea.
I&#039;m open to new ideas, however, and if you (or the folks behind the blog) can give me a few reasons why we can&#039;t just stick to web standards, I&#039;m all ears.
]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m not going to rant off like Hale, but I agree with him on key points. Is there a reason why that blog had to be done with Flash/Flex/whatever-it-is? Could it not be realized with HTML? It&#8217;s just some text, a few images and videos, so it seems like using a hammer to swat a fly.<br />
I understand if it is a tech demo, but I certainly hope this is not Adobe&#8217;s future vision of the internet. We dropped full-flash sites a few years ago when we realized it was a bad idea.<br />
I&#8217;m open to new ideas, however, and if you (or the folks behind the blog) can give me a few reasons why we can&#8217;t just stick to web standards, I&#8217;m all ears.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hale</title>
		<link>http://blogs.adobe.com/jnack/2008/10/new_adobe_xd_pub_thoughts_on_cs4_ui.html#comment-9732</link>
		<dc:creator>Hale</dc:creator>
		<pubDate>Tue, 14 Oct 2008 22:12:25 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/10/new-adobe-xd-pub-thoughts-on-cs4-ui.html#comment-9732</guid>
		<description><![CDATA[This is irony at it&#039;s best. I launched the url to the Inspire blog over 15 minutes ago and the big, fat, purple progress bar that displays &quot;Loading Adobe Flex&quot; is just now crawling it&#039;s way past the three quarter mark. This site is the epitomy of forced technology as there is absolutely no reason for it to be so Flash-heavy. The blatancy of this attempt to peddle Adobe&#039;s proprietary technology is embarrassing to witness. Seriously, making the user experience blog so &quot;user unfriendly&quot; has got to warrant a nomination for the Darwin Awards. I&#039;ve finished my post just in time to check and see that Inspire has just finished loading. It&#039;s very annoying to see this site disregard the increased font size reflected in my preferences as I often make my daily reading-rounds from the couch, from which browser magnification capabilities work great with. I also have the feeling that this isn&#039;t the only user-disruption presented by this execution, but I digress. I&#039;m going to fix the problem right now by simply closing leaving this site once and for all. Congratulations Adobe, you&#039;ve done little more than further Inspire me to put the kibosh on recommending and/or using your internet solutions.
]]></description>
		<content:encoded><![CDATA[<p>This is irony at it&#8217;s best. I launched the url to the Inspire blog over 15 minutes ago and the big, fat, purple progress bar that displays &#8220;Loading Adobe Flex&#8221; is just now crawling it&#8217;s way past the three quarter mark. This site is the epitomy of forced technology as there is absolutely no reason for it to be so Flash-heavy. The blatancy of this attempt to peddle Adobe&#8217;s proprietary technology is embarrassing to witness. Seriously, making the user experience blog so &#8220;user unfriendly&#8221; has got to warrant a nomination for the Darwin Awards. I&#8217;ve finished my post just in time to check and see that Inspire has just finished loading. It&#8217;s very annoying to see this site disregard the increased font size reflected in my preferences as I often make my daily reading-rounds from the couch, from which browser magnification capabilities work great with. I also have the feeling that this isn&#8217;t the only user-disruption presented by this execution, but I digress. I&#8217;m going to fix the problem right now by simply closing leaving this site once and for all. Congratulations Adobe, you&#8217;ve done little more than further Inspire me to put the kibosh on recommending and/or using your internet solutions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Thompson</title>
		<link>http://blogs.adobe.com/jnack/2008/10/new_adobe_xd_pub_thoughts_on_cs4_ui.html#comment-9731</link>
		<dc:creator>Tim Thompson</dc:creator>
		<pubDate>Tue, 14 Oct 2008 19:53:15 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/10/new-adobe-xd-pub-thoughts-on-cs4-ui.html#comment-9731</guid>
		<description><![CDATA[This is all good and well but when will I be able to download my preorder copy of CS4?
]]></description>
		<content:encoded><![CDATA[<p>This is all good and well but when will I be able to download my preorder copy of CS4?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: font9a</title>
		<link>http://blogs.adobe.com/jnack/2008/10/new_adobe_xd_pub_thoughts_on_cs4_ui.html#comment-9730</link>
		<dc:creator>font9a</dc:creator>
		<pubDate>Tue, 14 Oct 2008 19:08:55 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/10/new-adobe-xd-pub-thoughts-on-cs4-ui.html#comment-9730</guid>
		<description><![CDATA[Back button on Webkit (OS X 10.5.5) nightly 10/12/08 doesn&#039;t work. Page took over 60 seconds to load. They should just have an HTML site and invite users to download a swf file instead of using all the overhead of crappy Mac support + Flash Player. I can understand the argument of eating your own dogfood and all... but given the usability perils the Flash-dependency presents it seems a really perplexing choice.
]]></description>
		<content:encoded><![CDATA[<p>Back button on Webkit (OS X 10.5.5) nightly 10/12/08 doesn&#8217;t work. Page took over 60 seconds to load. They should just have an HTML site and invite users to download a swf file instead of using all the overhead of crappy Mac support + Flash Player. I can understand the argument of eating your own dogfood and all&#8230; but given the usability perils the Flash-dependency presents it seems a really perplexing choice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aran</title>
		<link>http://blogs.adobe.com/jnack/2008/10/new_adobe_xd_pub_thoughts_on_cs4_ui.html#comment-9729</link>
		<dc:creator>Aran</dc:creator>
		<pubDate>Tue, 14 Oct 2008 18:21:57 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/10/new-adobe-xd-pub-thoughts-on-cs4-ui.html#comment-9729</guid>
		<description><![CDATA[I am also curious as to some of the decisions taken by the XD team.
If you look a the source of the page, it is great that it is using swfobject (even if it is the old v1.5), which gives the potential for indexable alternate content for users without Flash / search engines, but the team just has a generic get flash player message in there rather than any article content.
How does the site content get indexed when all of the article data is held in external XML files, and there seems to be no sitemap.xml file for Googlebots etc to follow?
]]></description>
		<content:encoded><![CDATA[<p>I am also curious as to some of the decisions taken by the XD team.<br />
If you look a the source of the page, it is great that it is using swfobject (even if it is the old v1.5), which gives the potential for indexable alternate content for users without Flash / search engines, but the team just has a generic get flash player message in there rather than any article content.<br />
How does the site content get indexed when all of the article data is held in external XML files, and there seems to be no sitemap.xml file for Googlebots etc to follow?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://blogs.adobe.com/jnack/2008/10/new_adobe_xd_pub_thoughts_on_cs4_ui.html#comment-9728</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Tue, 14 Oct 2008 18:20:12 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/10/new-adobe-xd-pub-thoughts-on-cs4-ui.html#comment-9728</guid>
		<description><![CDATA[Hey love the blog.
&lt;i&gt;[Thanks.  --J.]&lt;/i&gt;
I am going to vent for a quick moment.  I recall about a year ago the term User Experience (UX) gained some momentum and the community circled around that set of terms. You wrote the XD (Experience Design) team.  I am wondering, is this yet another redundant abbreviation that the community needs to deal with or, is there a difference between UX and XD, or maybe am I just behind the times a little bit?
&lt;i&gt;[AFAIK the terms are interchangeable.  --J.]&lt;/i&gt;
]]></description>
		<content:encoded><![CDATA[<p>Hey love the blog.<br />
<i>[Thanks.  --J.]</i><br />
I am going to vent for a quick moment.  I recall about a year ago the term User Experience (UX) gained some momentum and the community circled around that set of terms. You wrote the XD (Experience Design) team.  I am wondering, is this yet another redundant abbreviation that the community needs to deal with or, is there a difference between UX and XD, or maybe am I just behind the times a little bit?<br />
<i>[AFAIK the terms are interchangeable.  --J.]</i></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: imajez</title>
		<link>http://blogs.adobe.com/jnack/2008/10/new_adobe_xd_pub_thoughts_on_cs4_ui.html#comment-9727</link>
		<dc:creator>imajez</dc:creator>
		<pubDate>Tue, 14 Oct 2008 16:52:18 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/10/new-adobe-xd-pub-thoughts-on-cs4-ui.html#comment-9727</guid>
		<description><![CDATA[The website UI is a pain in posterior as you cannot scroll down apge with mouse, you have to drag slider down, not good.
&lt;i&gt;[Actually, I don&#039;t know whether it requires Flash Player 10 or not, but as long as you&#039;ve put focus onto the SWF, the scroll wheel works.  --J.]&lt;/i&gt;
As for &#039;me julies&#039; sounding like British slang - being kicked in the &#039;goolies&#039; is certainly very painful!
&lt;i&gt;[I think I&#039;m being influenced by &lt;a href=&quot;http://www.youtube.com/watch?v=TLEf8YzWV30&quot; rel=&quot;nofollow&quot;&gt;Ali G&lt;/a&gt; on this one.  --J.]&lt;/i&gt;
]]></description>
		<content:encoded><![CDATA[<p>The website UI is a pain in posterior as you cannot scroll down apge with mouse, you have to drag slider down, not good.<br />
<i>[Actually, I don't know whether it requires Flash Player 10 or not, but as long as you've put focus onto the SWF, the scroll wheel works.  --J.]</i><br />
As for &#8216;me julies&#8217; sounding like British slang &#8211; being kicked in the &#8216;goolies&#8217; is certainly very painful!<br />
<i>[I think I'm being influenced by <a href="http://www.youtube.com/watch?v=TLEf8YzWV30" rel="nofollow">Ali G</a> on this one.  --J.]</i></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Niklas</title>
		<link>http://blogs.adobe.com/jnack/2008/10/new_adobe_xd_pub_thoughts_on_cs4_ui.html#comment-9726</link>
		<dc:creator>Niklas</dc:creator>
		<pubDate>Tue, 14 Oct 2008 16:27:34 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/10/new-adobe-xd-pub-thoughts-on-cs4-ui.html#comment-9726</guid>
		<description><![CDATA[I wIll definitely follow the XD blog! And I really want to love it as well... But I am unable to open links in new windows or tabs, I can&#039;t see if a link opens a new window or not or even where it leads to. Zooming text does not work, neither can I hold down option-ctrl-D and hover over a word to get the definition of that word. Selected text does not honor my operating system settings, and so on... I am running Safari 3.1.2 on OSX 10.5.5. What is up with that?
]]></description>
		<content:encoded><![CDATA[<p>I wIll definitely follow the XD blog! And I really want to love it as well&#8230; But I am unable to open links in new windows or tabs, I can&#8217;t see if a link opens a new window or not or even where it leads to. Zooming text does not work, neither can I hold down option-ctrl-D and hover over a word to get the definition of that word. Selected text does not honor my operating system settings, and so on&#8230; I am running Safari 3.1.2 on OSX 10.5.5. What is up with that?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
