<?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: Dr. Woohoo &amp; the future of the Suite platform</title>
	<atom:link href="http://blogs.adobe.com/jnack/2008/05/dr_woohoo_the_future_of_the_suite_platform.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blogs.adobe.com/jnack/2008/05/dr_woohoo_the_future_of_the_suite_platform.html</link>
	<description></description>
	<lastBuildDate>Sun, 19 May 2013 18:03:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Pat McKluskey</title>
		<link>http://blogs.adobe.com/jnack/2008/05/dr_woohoo_the_future_of_the_suite_platform.html#comment-7897</link>
		<dc:creator>Pat McKluskey</dc:creator>
		<pubDate>Sat, 12 Sep 2009 23:03:11 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/05/dr-woohoo-the-future-of-the-suite-platform.html#comment-7897</guid>
		<description><![CDATA[God I hate Adobe. Get your Flash player off my MAC!!!!! It&#039;s no wonder they don&#039;t want your junk on their iphones!
]]></description>
		<content:encoded><![CDATA[<p>God I hate Adobe. Get your Flash player off my MAC!!!!! It&#8217;s no wonder they don&#8217;t want your junk on their iphones!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hale</title>
		<link>http://blogs.adobe.com/jnack/2008/05/dr_woohoo_the_future_of_the_suite_platform.html#comment-7896</link>
		<dc:creator>Hale</dc:creator>
		<pubDate>Tue, 14 Oct 2008 23:55:28 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/05/dr-woohoo-the-future-of-the-suite-platform.html#comment-7896</guid>
		<description><![CDATA[&lt;blockquote&gt;On one side one of the more simple examples that Dr. Woohoo demoed at FITC is browsing Flickr images inside of the SWF pallet inside of Illustrator and then when the user selects an image the main colours from that image are then used to popular a Swatch pallet.&lt;/blockquote&gt;
Are you kidding me? Are we on candid camera or something? Please tell me you aren&#039;t serious.
]]></description>
		<content:encoded><![CDATA[<blockquote><p>On one side one of the more simple examples that Dr. Woohoo demoed at FITC is browsing Flickr images inside of the SWF pallet inside of Illustrator and then when the user selects an image the main colours from that image are then used to popular a Swatch pallet.</p></blockquote>
<p>Are you kidding me? Are we on candid camera or something? Please tell me you aren&#8217;t serious.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hale</title>
		<link>http://blogs.adobe.com/jnack/2008/05/dr_woohoo_the_future_of_the_suite_platform.html#comment-7895</link>
		<dc:creator>Hale</dc:creator>
		<pubDate>Tue, 14 Oct 2008 23:00:19 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/05/dr-woohoo-the-future-of-the-suite-platform.html#comment-7895</guid>
		<description><![CDATA[Dear Kenmore, you do a nice job of making a range that I’m able to reliably cook my food with every day. I’m very happy that you have come in to my home, found your place in the kitchen and have focused in on doing what you do best. Thank you so much for leaving the rest of the kitchen (and the house for that matter) alone and trusting the look, flow, feel and overall functionality of the place to those that know best, i.e., not you Kenmore, because as we established, you are the cooking expert! Thank you Kenmore for understanding that it would not make people very happy if your ranges were invited into our homes only to start trying to tell us that the structure and layout of the entire house wasn’t right for cooking tasks. Some ranges might think that the counters were in the wrong place, the sink by the wrong wall, the fridge in the wrong corner, the lights too dim, and the windows on the wrong side. The great news is that you don’t have to worry about any of this because we found the best minds in the world for figuring out all of that other stuff, so you can stick to doing what it is you’re good at! Thanks again Kenmore for not overstepping your welcome and trying to “fix” something that you have never been good at in the first place!
Dear Adobe, you do a decent job of offering image processing technology (once upon a time you did a great job, but that&#039;s another story for another day). I’m very happy that you have been installed on my system and that you have found your place in the pipeline and have focused in on doing what you do best. Thank you so much for leaving the rest of the system alone and trusting the look, flow, feel and overall functionality of the system to those that know best, i.e., not you Adobe, because as we established, you are the image processing expert! Thank you Adobe for understanding that it would not make people very happy if your software were installed onto our systems only to start trying to reinvent the look, feel, flow, and overall usability of our system, a system that has been honed by absolute experts to be consistent and reliable across a multitude of applications and not just your image processing capablities. So thanks again Adobe for not barging onto our systems and trying to disrupt and undo the refined user experience so carefully designed and crafted by our Operating System gurus, something that you have never been good at anyways, hence clearing the path for you to focus on what you do best, help users to process images!
]]></description>
		<content:encoded><![CDATA[<p>Dear Kenmore, you do a nice job of making a range that I’m able to reliably cook my food with every day. I’m very happy that you have come in to my home, found your place in the kitchen and have focused in on doing what you do best. Thank you so much for leaving the rest of the kitchen (and the house for that matter) alone and trusting the look, flow, feel and overall functionality of the place to those that know best, i.e., not you Kenmore, because as we established, you are the cooking expert! Thank you Kenmore for understanding that it would not make people very happy if your ranges were invited into our homes only to start trying to tell us that the structure and layout of the entire house wasn’t right for cooking tasks. Some ranges might think that the counters were in the wrong place, the sink by the wrong wall, the fridge in the wrong corner, the lights too dim, and the windows on the wrong side. The great news is that you don’t have to worry about any of this because we found the best minds in the world for figuring out all of that other stuff, so you can stick to doing what it is you’re good at! Thanks again Kenmore for not overstepping your welcome and trying to “fix” something that you have never been good at in the first place!<br />
Dear Adobe, you do a decent job of offering image processing technology (once upon a time you did a great job, but that&#8217;s another story for another day). I’m very happy that you have been installed on my system and that you have found your place in the pipeline and have focused in on doing what you do best. Thank you so much for leaving the rest of the system alone and trusting the look, flow, feel and overall functionality of the system to those that know best, i.e., not you Adobe, because as we established, you are the image processing expert! Thank you Adobe for understanding that it would not make people very happy if your software were installed onto our systems only to start trying to reinvent the look, feel, flow, and overall usability of our system, a system that has been honed by absolute experts to be consistent and reliable across a multitude of applications and not just your image processing capablities. So thanks again Adobe for not barging onto our systems and trying to disrupt and undo the refined user experience so carefully designed and crafted by our Operating System gurus, something that you have never been good at anyways, hence clearing the path for you to focus on what you do best, help users to process images!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Kindberg</title>
		<link>http://blogs.adobe.com/jnack/2008/05/dr_woohoo_the_future_of_the_suite_platform.html#comment-7894</link>
		<dc:creator>Tim Kindberg</dc:creator>
		<pubDate>Thu, 09 Oct 2008 06:34:11 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/05/dr-woohoo-the-future-of-the-suite-platform.html#comment-7894</guid>
		<description><![CDATA[Wow I can&#039;t read any more negative comments! What the heck is the matter with these people?! Complaining about how the tool gets harder and harder to use?!! Are you kidding me? Maybe its because you are getting more and more carpel tunnel in your wrist? Because CS2 was by far one of the biggest enhancements in usability with the new layers palette alone. Look at CS4 and truly tell me its totally backwards... seriously? The rotating and zooming is going to feel so naturally now, and the masks panel and adjustment panel, its all better. Why do you distrust Adobe so much? The company who gave you the tools you needed to eat that food on that plate that you are whining about so much? Everytime you open Photoshop it must be such a drag... &quot;Oh no I have to use Photoshop again, I&#039;m so unfamiliar with it and its so hard to use&quot;. I don&#039;t think so. Something tells me that if your anything like the thousands of other users out there, you open it up and zip around like a crazy person, with the efficiency of an ant army. Get it straight. I&#039;m not sure where you whiners come from but around here I never hear &quot;Well I think I am just gonna make this in GIMP/CorelDraw/etc because I just work better in that program.&quot;
]]></description>
		<content:encoded><![CDATA[<p>Wow I can&#8217;t read any more negative comments! What the heck is the matter with these people?! Complaining about how the tool gets harder and harder to use?!! Are you kidding me? Maybe its because you are getting more and more carpel tunnel in your wrist? Because CS2 was by far one of the biggest enhancements in usability with the new layers palette alone. Look at CS4 and truly tell me its totally backwards&#8230; seriously? The rotating and zooming is going to feel so naturally now, and the masks panel and adjustment panel, its all better. Why do you distrust Adobe so much? The company who gave you the tools you needed to eat that food on that plate that you are whining about so much? Everytime you open Photoshop it must be such a drag&#8230; &#8220;Oh no I have to use Photoshop again, I&#8217;m so unfamiliar with it and its so hard to use&#8221;. I don&#8217;t think so. Something tells me that if your anything like the thousands of other users out there, you open it up and zip around like a crazy person, with the efficiency of an ant army. Get it straight. I&#8217;m not sure where you whiners come from but around here I never hear &#8220;Well I think I am just gonna make this in GIMP/CorelDraw/etc because I just work better in that program.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Larissa Callahan</title>
		<link>http://blogs.adobe.com/jnack/2008/05/dr_woohoo_the_future_of_the_suite_platform.html#comment-7893</link>
		<dc:creator>Larissa Callahan</dc:creator>
		<pubDate>Fri, 26 Sep 2008 14:24:20 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/05/dr-woohoo-the-future-of-the-suite-platform.html#comment-7893</guid>
		<description><![CDATA[So help us all if Adobe starts throwing Flash UI crap all over Photoshop. The Flash Player for Mac is absolutely despicable, so if you put that junk in front of professionals prepare to reap the whirlwind Adobe!
&lt;i&gt;[You aren&#039;t familiar with what I have in mind.  Of course, that&#039;s never stopped people from commenting here.  --J.]&lt;/i&gt;
]]></description>
		<content:encoded><![CDATA[<p>So help us all if Adobe starts throwing Flash UI crap all over Photoshop. The Flash Player for Mac is absolutely despicable, so if you put that junk in front of professionals prepare to reap the whirlwind Adobe!<br />
<i>[You aren't familiar with what I have in mind.  Of course, that's never stopped people from commenting here.  --J.]</i></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Markus Selbach</title>
		<link>http://blogs.adobe.com/jnack/2008/05/dr_woohoo_the_future_of_the_suite_platform.html#comment-7892</link>
		<dc:creator>Markus Selbach</dc:creator>
		<pubDate>Sun, 01 Jun 2008 11:19:54 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/05/dr-woohoo-the-future-of-the-suite-platform.html#comment-7892</guid>
		<description><![CDATA[I&#039;m looking forward to the integration of SWF. As developer for productive workflows in our lab, I do a lot of ExtendScript programming. But I hate to code ScriptUI. So if the integration works properly I will be happy to give the gui-part of my work to a flash developer :), and put my focus to the funtionallity.
The vision of communication with our (photographer)-customers in their professional environment (photoshop, bridge) is very promising.
Regards,
Markus Selbach
Germany
]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m looking forward to the integration of SWF. As developer for productive workflows in our lab, I do a lot of ExtendScript programming. But I hate to code ScriptUI. So if the integration works properly I will be happy to give the gui-part of my work to a flash developer :), and put my focus to the funtionallity.<br />
The vision of communication with our (photographer)-customers in their professional environment (photoshop, bridge) is very promising.<br />
Regards,<br />
Markus Selbach<br />
Germany</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mofle</title>
		<link>http://blogs.adobe.com/jnack/2008/05/dr_woohoo_the_future_of_the_suite_platform.html#comment-7891</link>
		<dc:creator>mofle</dc:creator>
		<pubDate>Fri, 30 May 2008 15:49:42 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/05/dr-woohoo-the-future-of-the-suite-platform.html#comment-7891</guid>
		<description><![CDATA[Thank you, couldn&#039;t had said it better myself!
By the way, i just found Adobe on getsatisfaction.com/adobe
It&#039;s very good platform to communicate with users.
]]></description>
		<content:encoded><![CDATA[<p>Thank you, couldn&#8217;t had said it better myself!<br />
By the way, i just found Adobe on getsatisfaction.com/adobe<br />
It&#8217;s very good platform to communicate with users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://blogs.adobe.com/jnack/2008/05/dr_woohoo_the_future_of_the_suite_platform.html#comment-7890</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Sun, 25 May 2008 08:41:01 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/05/dr-woohoo-the-future-of-the-suite-platform.html#comment-7890</guid>
		<description><![CDATA[&quot;What if Adobe or any other developer...&quot;
This is not the time to start opening up the app again to 3rd party development, which gets dropped 3-4 versions down the line. We&#039;ve been through that with filters etc...often frivilous.
You need to add the work, not just leave the door open for developers to come and go as they please.
A much better use of resources would be to look at the UI complaints, and the workflow complaints, even those raised on your very own forums. Develop a proper feedback interface with your customer base, not a one person blog, an ignored feature request archive, a support forum without official Adobe presence, a beta test with feedback actually dismissed.
Actually issue point releases.
Of course, it might not make pretty PR, but then someone might have to think about market saturation...and to be honest the profile of Adobe in the UK looks after itself.
So, there is no answer as to why the display modes for 2 docs cant be held in different states in 2 docs?
Why is it when i create a layer with a selection active, it creates a layer mask, but when i create a group of layers it doesn&#039;t?
Why are the filters 13 years old? You can fill pages with the problems these have. Why can&#039;t we turn off the abonimable filter gallery?
Why cant i position the centre for a radial blur on the image, perhaps using guides? (so i can retain the point in the workflow...live filters dont cut it)
Why does lens flare still have a preview bug?
Why does export for paths randomly drop .ai extension for the past 5 versions?
Why does the crop tool try to autofill a nearest number when the dimensions are left blank?
Why does the warp tool lack all the features that its sister application AI have?
Why cant we make paths into guides and vice versa?
Why is there no scissors or boolean tools on paths?
Why does CM setting default to strip profiles?( as far as i remember)
Why on earth did Adobe make the airbrush a subset feature of the brush tool requiring more brush shapes to be saved?
Why can you select a brush on the flyout menu, but not the opacity? Why can you invoke and use it without the keyboard, but not close it without it?
Why did the link icon column on the palette have to go, what exactly did it interfere with on the new group feature?
Why does the new 3d lack the ability to alter lighting, and why was it even added?
Why does exposure in HDR work differently when open as compared to when saving?
Why do you think people are not hooping and hollaring with the general UI/capability thinking so far published?
As someone has said, it seems the original development ethos of old at Adobe on PS has gone or dropped behind the line. If you had some competition, this blog would be totally different.
]]></description>
		<content:encoded><![CDATA[<p>&#8220;What if Adobe or any other developer&#8230;&#8221;<br />
This is not the time to start opening up the app again to 3rd party development, which gets dropped 3-4 versions down the line. We&#8217;ve been through that with filters etc&#8230;often frivilous.<br />
You need to add the work, not just leave the door open for developers to come and go as they please.<br />
A much better use of resources would be to look at the UI complaints, and the workflow complaints, even those raised on your very own forums. Develop a proper feedback interface with your customer base, not a one person blog, an ignored feature request archive, a support forum without official Adobe presence, a beta test with feedback actually dismissed.<br />
Actually issue point releases.<br />
Of course, it might not make pretty PR, but then someone might have to think about market saturation&#8230;and to be honest the profile of Adobe in the UK looks after itself.<br />
So, there is no answer as to why the display modes for 2 docs cant be held in different states in 2 docs?<br />
Why is it when i create a layer with a selection active, it creates a layer mask, but when i create a group of layers it doesn&#8217;t?<br />
Why are the filters 13 years old? You can fill pages with the problems these have. Why can&#8217;t we turn off the abonimable filter gallery?<br />
Why cant i position the centre for a radial blur on the image, perhaps using guides? (so i can retain the point in the workflow&#8230;live filters dont cut it)<br />
Why does lens flare still have a preview bug?<br />
Why does export for paths randomly drop .ai extension for the past 5 versions?<br />
Why does the crop tool try to autofill a nearest number when the dimensions are left blank?<br />
Why does the warp tool lack all the features that its sister application AI have?<br />
Why cant we make paths into guides and vice versa?<br />
Why is there no scissors or boolean tools on paths?<br />
Why does CM setting default to strip profiles?( as far as i remember)<br />
Why on earth did Adobe make the airbrush a subset feature of the brush tool requiring more brush shapes to be saved?<br />
Why can you select a brush on the flyout menu, but not the opacity? Why can you invoke and use it without the keyboard, but not close it without it?<br />
Why did the link icon column on the palette have to go, what exactly did it interfere with on the new group feature?<br />
Why does the new 3d lack the ability to alter lighting, and why was it even added?<br />
Why does exposure in HDR work differently when open as compared to when saving?<br />
Why do you think people are not hooping and hollaring with the general UI/capability thinking so far published?<br />
As someone has said, it seems the original development ethos of old at Adobe on PS has gone or dropped behind the line. If you had some competition, this blog would be totally different.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Markus</title>
		<link>http://blogs.adobe.com/jnack/2008/05/dr_woohoo_the_future_of_the_suite_platform.html#comment-7889</link>
		<dc:creator>Markus</dc:creator>
		<pubDate>Sun, 25 May 2008 01:34:31 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/05/dr-woohoo-the-future-of-the-suite-platform.html#comment-7889</guid>
		<description><![CDATA[&gt;&quot;We didn&#039;t just shovel in a bunch of blinky new stuff in CS3: we went back and made a bunch of tweaks to things like Brightness/Contrast (now using a better algorithm without removing the old one), the way cloning and healing interact with adjustment layers (much more control), the way selections are feathered and modified (now in a 1-stop interactive dialog), the way you can select parts of the image (Quick Select), the way filters work (now optionally staying re-editable), the way raw files are processed (more control, Smart Object conversion) and more. Some of these things make it into a feature list; most don&#039;t. You will always be able to find examples of things that we haven&#039;t yet done, but saying that we&#039;re &quot;just ignoring the user requests&quot; is inaccurate. --J.&quot;
]]></description>
		<content:encoded><![CDATA[<p>&gt;&#8221;We didn&#8217;t just shovel in a bunch of blinky new stuff in CS3: we went back and made a bunch of tweaks to things like Brightness/Contrast (now using a better algorithm without removing the old one), the way cloning and healing interact with adjustment layers (much more control), the way selections are feathered and modified (now in a 1-stop interactive dialog), the way you can select parts of the image (Quick Select), the way filters work (now optionally staying re-editable), the way raw files are processed (more control, Smart Object conversion) and more. Some of these things make it into a feature list; most don&#8217;t. You will always be able to find examples of things that we haven&#8217;t yet done, but saying that we&#8217;re &#8220;just ignoring the user requests&#8221; is inaccurate. &#8211;J.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Brown</title>
		<link>http://blogs.adobe.com/jnack/2008/05/dr_woohoo_the_future_of_the_suite_platform.html#comment-7888</link>
		<dc:creator>Phil Brown</dc:creator>
		<pubDate>Sat, 24 May 2008 00:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/05/dr-woohoo-the-future-of-the-suite-platform.html#comment-7888</guid>
		<description><![CDATA[Honestly, Anne, you&#039;re one of very few &quot;professionals&quot; I know who has constant trouble with printing.  I&#039;ve tried to help you before here on John&#039;s blog but you pretty much refuse to take any advice.
In the last twelve months I&#039;ve printed hundreds of images for major exhibitions and awards for many of the country&#039;s top photographers and a number from overseas as well.  No problems.
There&#039;s no doubt there were and are things that needed attention, but 10.0.1 addressed most of those and Dave P. has posted some time back to indicate that work continues to improve printing.
So, in what way is Adobe ignoring printing given that it is already quite functional and effective and they are continue to work on it having already provided a dot release to address some known issues?
The fact that you are having problems when most users are not says clearly to me that you have an issue with either your workflow or your setup.  Fix that and you&#039;ll fix your problems, but until you&#039;re prepared to listen to what others have to say and suggest I doubt you&#039;ll get anywhere which is unfortuante.
]]></description>
		<content:encoded><![CDATA[<p>Honestly, Anne, you&#8217;re one of very few &#8220;professionals&#8221; I know who has constant trouble with printing.  I&#8217;ve tried to help you before here on John&#8217;s blog but you pretty much refuse to take any advice.<br />
In the last twelve months I&#8217;ve printed hundreds of images for major exhibitions and awards for many of the country&#8217;s top photographers and a number from overseas as well.  No problems.<br />
There&#8217;s no doubt there were and are things that needed attention, but 10.0.1 addressed most of those and Dave P. has posted some time back to indicate that work continues to improve printing.<br />
So, in what way is Adobe ignoring printing given that it is already quite functional and effective and they are continue to work on it having already provided a dot release to address some known issues?<br />
The fact that you are having problems when most users are not says clearly to me that you have an issue with either your workflow or your setup.  Fix that and you&#8217;ll fix your problems, but until you&#8217;re prepared to listen to what others have to say and suggest I doubt you&#8217;ll get anywhere which is unfortuante.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ann Shelbourne</title>
		<link>http://blogs.adobe.com/jnack/2008/05/dr_woohoo_the_future_of_the_suite_platform.html#comment-7887</link>
		<dc:creator>Ann Shelbourne</dc:creator>
		<pubDate>Fri, 23 May 2008 19:16:17 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/05/dr-woohoo-the-future-of-the-suite-platform.html#comment-7887</guid>
		<description><![CDATA[&gt;Why is it that people take the attitude of &quot;well, I don&#039;t want it, no one should want it&quot;?
You are missing the point:
Some of us would just like to be assured that our repeated Requests for the much needed improvement of EXISTING Features (and these same requests have repeatedly been made over numerous Photoshop &quot;cycles&quot; by many different users) will actually be addressed this time — BEFORE you allow yourselves the luxury of adding frivolous flashy frilly bits which may make you whoop with joy at your own cleverness but probably won&#039;t be particularly useful to too many of your customers on a day to day basis.
&lt;i&gt;[My colleagues frequently bemoan the constant whooping.  --J.]&lt;/i&gt;
In other words, please get the Basics right first this time; and concentrate on maintaining stability (with no snafus like the Print debacle of CS3!) — before you entertain yourselves playing with bells and whistles.
Seems a simple-enough request?
]]></description>
		<content:encoded><![CDATA[<p>&gt;Why is it that people take the attitude of &#8220;well, I don&#8217;t want it, no one should want it&#8221;?<br />
You are missing the point:<br />
Some of us would just like to be assured that our repeated Requests for the much needed improvement of EXISTING Features (and these same requests have repeatedly been made over numerous Photoshop &#8220;cycles&#8221; by many different users) will actually be addressed this time — BEFORE you allow yourselves the luxury of adding frivolous flashy frilly bits which may make you whoop with joy at your own cleverness but probably won&#8217;t be particularly useful to too many of your customers on a day to day basis.<br />
<i>[My colleagues frequently bemoan the constant whooping.  --J.]</i><br />
In other words, please get the Basics right first this time; and concentrate on maintaining stability (with no snafus like the Print debacle of CS3!) — before you entertain yourselves playing with bells and whistles.<br />
Seems a simple-enough request?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mofle</title>
		<link>http://blogs.adobe.com/jnack/2008/05/dr_woohoo_the_future_of_the_suite_platform.html#comment-7886</link>
		<dc:creator>mofle</dc:creator>
		<pubDate>Fri, 23 May 2008 14:42:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/05/dr-woohoo-the-future-of-the-suite-platform.html#comment-7886</guid>
		<description><![CDATA[Here is some tips i think a lot of user will agree on:
- More UI consistency and OS integration.
- Refresh all the old filters, dialogs, and panels.
&lt;i&gt;[Sorry, but those are unhelpfully broad (and thus unactionable) suggestions.  Do you really care about us improving Plastic Wrap or Sumi-e or Solarize?  No?  Then please tell me what you actually care about instead of saying &quot;boil the ocean.&quot;  --J.]&lt;/i&gt;
- Mac only:
Please take a look at these apps for UI inspiration.
Pixelmator (Photoshop)
Apple Aperture (Photoshop)
VectorDesigner (Illustrator)
Coda (Dreamweaver)
CSSEdit (Dreamweaver)
- Why not read the request forum once a while, and actually listening to the users. In the recent CS versions it feels you&#039;re just ignoring the user requests.
&lt;i&gt;[I don&#039;t know what to tell you.  Photoshop isn&#039;t perfect; Adobe isn&#039;t perfect; I&#039;m not perfect.  But on the whole, as I&#039;ve mentioned elsewhere in this thread, customers are telling us they&#039;re pretty happy--more so than they were in CS2.  We&#039;re not putting words in anyone&#039;s mouth.
&lt;i&gt;We didn&#039;t just shovel in a bunch of blinky new stuff in CS3: we went back and made a bunch of tweaks to things like Brightness/Contrast (now using a better algorithm without removing the old one), the way cloning and healing interact with adjustment layers (much more control), the way selections are feathered and modified (now in a 1-stop interactive dialog), the way you can select parts of the image (Quick Select), the way filters work (now optionally staying re-editable), the way raw files are processed (more control, Smart Object conversion) and more.  Some of these things make it into a feature list; most don&#039;t.  You will &lt;b&gt;always&lt;/b&gt; be able to find examples of things that we haven&#039;t yet done, but saying that we&#039;re &quot;just ignoring the user requests&quot; is inaccurate.  --J.]&lt;/i&gt;
- Maybe a little bit more creative app icons the next time?
- Mac only: It&#039;s 2008 and Adobe apps is still not using Cocoa, 64-bit on any app, or even planning on doing it in CS4.
&lt;i&gt;[Two questions: 1. Which company is shipping the first mainstream 64-bit Mac app?  Five letters, starts with &quot;A&quot;, isn&#039;t Apple...  2. Besides the recently imposed 64-bit differentiator, what functional benefits does converting from Carbon to Cocoa provide?  Please inform the Final Cut, Finder, and iTunes teams of your findings.  --J.]&lt;/i&gt;
- You should have an official request voting system, like this one: &lt;a href=&quot;http://suggestions.yahoo.com/?prop=Pipes&quot; rel=&quot;nofollow&quot;&gt;http://suggestions.yahoo.com/?prop=Pipes&lt;/a&gt;
- I&#039;m no expert, but using the graphics card to take some of the load off the processor seems like a really good idea. Core Image, OpenGL...
&lt;i&gt;[Have you been reading &lt;a href=&quot;http://blogs.adobe.com/jnack/2008/05/pixel_bender_no.html&quot; rel=&quot;nofollow&quot;&gt;anything on this blog&lt;/a&gt; besides this one post?  And by the way, saying &quot;use Core Image&quot; isn&#039;t helpful, as that&#039;s a particular implementation possibility that has pros and cons (as they all do).  It&#039;s much more helpful to speak in terms of problems you want solved (e.g. make image display, filters, etc. faster and smoother in Photoshop) and let us figure out the best way to get there.  --J.]&lt;/i&gt;
- Fireworks should really have it&#039;s own file formats, it annoying that it&#039;s using .png.
&lt;i&gt;[I don&#039;t know why you say so, but it doesn&#039;t really matter to me as that&#039;s far off topic from Photoshop.  --J.]&lt;/i&gt;
- Adobe could learn a lot from Indie developers, especially the ones developing for Mac.
- I must say that after working a lot in Coda, starting Dreamweaver just feels like bloatware deluxe. Keywords: OS integration, startup time, UI.
On the SWF panels discussion:
I think it&#039;s a great idea, but it has to be executed well. Before CS4 gets out we&#039;ll get the final version of Flash 10 that will help alot on UI and speed. But it&#039;s still up to you to do it right, don&#039;t do to the world what Microsoft did with Windows Vista. Please!
All this doesn&#039;t mean we don&#039;t appreciate all the hard work you guys are doing, it just feels like your heading in a slightly wrong direction.&lt;/i&gt;
]]></description>
		<content:encoded><![CDATA[<p>Here is some tips i think a lot of user will agree on:<br />
- More UI consistency and OS integration.<br />
- Refresh all the old filters, dialogs, and panels.<br />
<i>[Sorry, but those are unhelpfully broad (and thus unactionable) suggestions.  Do you really care about us improving Plastic Wrap or Sumi-e or Solarize?  No?  Then please tell me what you actually care about instead of saying "boil the ocean."  --J.]</i><br />
- Mac only:<br />
Please take a look at these apps for UI inspiration.<br />
Pixelmator (Photoshop)<br />
Apple Aperture (Photoshop)<br />
VectorDesigner (Illustrator)<br />
Coda (Dreamweaver)<br />
CSSEdit (Dreamweaver)<br />
- Why not read the request forum once a while, and actually listening to the users. In the recent CS versions it feels you&#8217;re just ignoring the user requests.<br />
<i>[I don't know what to tell you.  Photoshop isn't perfect; Adobe isn't perfect; I'm not perfect.  But on the whole, as I've mentioned elsewhere in this thread, customers are telling us they're pretty happy--more so than they were in CS2.  We're not putting words in anyone's mouth.<br />
</i><i>We didn't just shovel in a bunch of blinky new stuff in CS3: we went back and made a bunch of tweaks to things like Brightness/Contrast (now using a better algorithm without removing the old one), the way cloning and healing interact with adjustment layers (much more control), the way selections are feathered and modified (now in a 1-stop interactive dialog), the way you can select parts of the image (Quick Select), the way filters work (now optionally staying re-editable), the way raw files are processed (more control, Smart Object conversion) and more.  Some of these things make it into a feature list; most don't.  You will <b>always</b> be able to find examples of things that we haven't yet done, but saying that we're "just ignoring the user requests" is inaccurate.  --J.]</i><br />
- Maybe a little bit more creative app icons the next time?<br />
- Mac only: It&#8217;s 2008 and Adobe apps is still not using Cocoa, 64-bit on any app, or even planning on doing it in CS4.<br />
<i>[Two questions: 1. Which company is shipping the first mainstream 64-bit Mac app?  Five letters, starts with "A", isn't Apple...  2. Besides the recently imposed 64-bit differentiator, what functional benefits does converting from Carbon to Cocoa provide?  Please inform the Final Cut, Finder, and iTunes teams of your findings.  --J.]</i><br />
- You should have an official request voting system, like this one: <a href="http://suggestions.yahoo.com/?prop=Pipes" rel="nofollow">http://suggestions.yahoo.com/?prop=Pipes</a><br />
- I&#8217;m no expert, but using the graphics card to take some of the load off the processor seems like a really good idea. Core Image, OpenGL&#8230;<br />
<i>[Have you been reading <a href="http://blogs.adobe.com/jnack/2008/05/pixel_bender_no.html" rel="nofollow">anything on this blog</a> besides this one post?  And by the way, saying "use Core Image" isn't helpful, as that's a particular implementation possibility that has pros and cons (as they all do).  It's much more helpful to speak in terms of problems you want solved (e.g. make image display, filters, etc. faster and smoother in Photoshop) and let us figure out the best way to get there.  --J.]</i><br />
- Fireworks should really have it&#8217;s own file formats, it annoying that it&#8217;s using .png.<br />
<i>[I don't know why you say so, but it doesn't really matter to me as that's far off topic from Photoshop.  --J.]</i><br />
- Adobe could learn a lot from Indie developers, especially the ones developing for Mac.<br />
- I must say that after working a lot in Coda, starting Dreamweaver just feels like bloatware deluxe. Keywords: OS integration, startup time, UI.<br />
On the SWF panels discussion:<br />
I think it&#8217;s a great idea, but it has to be executed well. Before CS4 gets out we&#8217;ll get the final version of Flash 10 that will help alot on UI and speed. But it&#8217;s still up to you to do it right, don&#8217;t do to the world what Microsoft did with Windows Vista. Please!<br />
All this doesn&#8217;t mean we don&#8217;t appreciate all the hard work you guys are doing, it just feels like your heading in a slightly wrong direction.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: T. Schmidt</title>
		<link>http://blogs.adobe.com/jnack/2008/05/dr_woohoo_the_future_of_the_suite_platform.html#comment-7885</link>
		<dc:creator>T. Schmidt</dc:creator>
		<pubDate>Fri, 23 May 2008 09:16:16 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/05/dr-woohoo-the-future-of-the-suite-platform.html#comment-7885</guid>
		<description><![CDATA[&quot;What percentage do you think rated Photoshop a 6 or a 7?&quot; How about asking us how we rate the CS3 Gui compared to 7 and CS2? Go to the feature requests and solve the main problems, THEN think about &quot;interesting color pickers&quot;.
&lt;i&gt;[I&#039;ll share more details about interface plans soon.  In the meantime, thanks again for presuming that we&#039;re &lt;a href=&quot;http://blogs.adobe.com/jnack/2008/05/pixel_bender_no.html&quot; rel=&quot;nofollow&quot;&gt;doing nothing&lt;/a&gt; (nothing, I tell you!) to address the fundamentals of Photoshop.  It&#039;s such a drag to have my villainous mustache-twirling interrupted...  --J.]&lt;/i&gt;
]]></description>
		<content:encoded><![CDATA[<p>&#8220;What percentage do you think rated Photoshop a 6 or a 7?&#8221; How about asking us how we rate the CS3 Gui compared to 7 and CS2? Go to the feature requests and solve the main problems, THEN think about &#8220;interesting color pickers&#8221;.<br />
<i>[I'll share more details about interface plans soon.  In the meantime, thanks again for presuming that we're <a href="http://blogs.adobe.com/jnack/2008/05/pixel_bender_no.html" rel="nofollow">doing nothing</a> (nothing, I tell you!) to address the fundamentals of Photoshop.  It's such a drag to have my villainous mustache-twirling interrupted...  --J.]</i></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich</title>
		<link>http://blogs.adobe.com/jnack/2008/05/dr_woohoo_the_future_of_the_suite_platform.html#comment-7884</link>
		<dc:creator>Rich</dc:creator>
		<pubDate>Thu, 22 May 2008 23:10:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/05/dr-woohoo-the-future-of-the-suite-platform.html#comment-7884</guid>
		<description><![CDATA[Although I am not a huge fan of Flash, the non-modal panel extensibilty sounds promising. Combined with further improvements to scripting this could be quite useful. Scripting seems to have not kept up with the improvements in Photoshop (e.g. how do you figure out if  there are multiple layers selected as allowed in CS2 and higher)?
I think little details like scroll wheel functionality will play a large role in how this Flash idea will be accepted.
]]></description>
		<content:encoded><![CDATA[<p>Although I am not a huge fan of Flash, the non-modal panel extensibilty sounds promising. Combined with further improvements to scripting this could be quite useful. Scripting seems to have not kept up with the improvements in Photoshop (e.g. how do you figure out if  there are multiple layers selected as allowed in CS2 and higher)?<br />
I think little details like scroll wheel functionality will play a large role in how this Flash idea will be accepted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Brown</title>
		<link>http://blogs.adobe.com/jnack/2008/05/dr_woohoo_the_future_of_the_suite_platform.html#comment-7883</link>
		<dc:creator>Phil Brown</dc:creator>
		<pubDate>Thu, 22 May 2008 20:42:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/05/dr-woohoo-the-future-of-the-suite-platform.html#comment-7883</guid>
		<description><![CDATA[Right, Anne, and because YOU don&#039;t see the need for an improved colour picker that&#039;s the end of the discussion?
I keep forgetting that you&#039;re the only professional out there using Photoshop - the rest of us are hacks and part timers who contribute nothing.
Still double profiling your prints in order to &quot;fix&quot; your colour managed workflow?
Why is it that people take the attitude of &quot;well, I don&#039;t want it, no one should want it&quot;?
]]></description>
		<content:encoded><![CDATA[<p>Right, Anne, and because YOU don&#8217;t see the need for an improved colour picker that&#8217;s the end of the discussion?<br />
I keep forgetting that you&#8217;re the only professional out there using Photoshop &#8211; the rest of us are hacks and part timers who contribute nothing.<br />
Still double profiling your prints in order to &#8220;fix&#8221; your colour managed workflow?<br />
Why is it that people take the attitude of &#8220;well, I don&#8217;t want it, no one should want it&#8221;?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
