<?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: Putting video inside the Photoshop UI</title>
	<atom:link href="http://blogs.adobe.com/jnack/2008/01/putting_video_inside_the_photoshop_ui.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blogs.adobe.com/jnack/2008/01/putting_video_inside_the_photoshop_ui.html</link>
	<description></description>
	<lastBuildDate>Mon, 20 May 2013 08:46:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Martin Briley</title>
		<link>http://blogs.adobe.com/jnack/2008/01/putting_video_inside_the_photoshop_ui.html#comment-6688</link>
		<dc:creator>Martin Briley</dc:creator>
		<pubDate>Thu, 27 Mar 2008 17:11:38 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/01/putting-video-inside-the-photoshop-ui.html#comment-6688</guid>
		<description><![CDATA[It&#039;s not that this feature doesn&#039;t have potential; but it shouldn&#039;t be necessary much of the time.  A well designed GUI does not require video to show you how to use it, yet the most basic tasks in Photoshop are often buried in obscurity.
&lt;i&gt;[Examples would be helpful.  In any case, Photoshop is used for an enormous variety of tasks.  Its tools and commands can be combined into an essentially unlimited number of combinations.  It&#039;s unrealistic to think that all of these would be self-evident through the GUI at a glance.  --J.]&lt;/i&gt;
And there should be a moratorium on new features until THE UPDATERS ARE FIXED once and for all.  Then again, that&#039;s a Mac-version-only problem, so we won&#039;t hold our breath...
&lt;i&gt;[No, it isn&#039;t Mac only.  The {series of profanities} installers and updaters are an embarrassment.  --J.]&lt;/i&gt;
]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s not that this feature doesn&#8217;t have potential; but it shouldn&#8217;t be necessary much of the time.  A well designed GUI does not require video to show you how to use it, yet the most basic tasks in Photoshop are often buried in obscurity.<br />
<i>[Examples would be helpful.  In any case, Photoshop is used for an enormous variety of tasks.  Its tools and commands can be combined into an essentially unlimited number of combinations.  It's unrealistic to think that all of these would be self-evident through the GUI at a glance.  --J.]</i><br />
And there should be a moratorium on new features until THE UPDATERS ARE FIXED once and for all.  Then again, that&#8217;s a Mac-version-only problem, so we won&#8217;t hold our breath&#8230;<br />
<i>[No, it isn't Mac only.  The {series of profanities} installers and updaters are an embarrassment.  --J.]</i></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: T. Schmidt</title>
		<link>http://blogs.adobe.com/jnack/2008/01/putting_video_inside_the_photoshop_ui.html#comment-6687</link>
		<dc:creator>T. Schmidt</dc:creator>
		<pubDate>Wed, 06 Feb 2008 20:37:17 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/01/putting-video-inside-the-photoshop-ui.html#comment-6687</guid>
		<description><![CDATA[In the prep guide it says you get a welcome kit, eventhough it&#039;s a re-certification?
]]></description>
		<content:encoded><![CDATA[<p>In the prep guide it says you get a welcome kit, eventhough it&#8217;s a re-certification?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: T. Schmidt</title>
		<link>http://blogs.adobe.com/jnack/2008/01/putting_video_inside_the_photoshop_ui.html#comment-6686</link>
		<dc:creator>T. Schmidt</dc:creator>
		<pubDate>Mon, 04 Feb 2008 16:23:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/01/putting-video-inside-the-photoshop-ui.html#comment-6686</guid>
		<description><![CDATA[The main problem with being new at Ps is that the &quot;Help Viewer&quot; isn&#039;t very well done, missing many terms Ps uses entirely. How bout working on that first?
&lt;i&gt;[We are.  --J.]&lt;/i&gt;
CS2&#039;s &quot;Help Center&quot; was at least speedier, automatically entering the searched term in the Cmd+F box, to help the user finding the actual content on a crowded page of the help text. Another example for Ps&#039;s declining usability. Put your videos in there and out of the app that&#039;s dear to us. Oh and what&#039;s up with deleting File&gt;Jump To?
&lt;i&gt;[We didn&#039;t want to keep throwing resources at testing integration with a discontinued app.  --J.]&lt;/i&gt;
Trying to make sure we can&#039;t use ImageReady CS2 with PsCS3 so we are forced to buy Fireworks for Rollovers, animated gifs and such? A sad development.
]]></description>
		<content:encoded><![CDATA[<p>The main problem with being new at Ps is that the &#8220;Help Viewer&#8221; isn&#8217;t very well done, missing many terms Ps uses entirely. How bout working on that first?<br />
<i>[We are.  --J.]</i><br />
CS2&#8242;s &#8220;Help Center&#8221; was at least speedier, automatically entering the searched term in the Cmd+F box, to help the user finding the actual content on a crowded page of the help text. Another example for Ps&#8217;s declining usability. Put your videos in there and out of the app that&#8217;s dear to us. Oh and what&#8217;s up with deleting File&gt;Jump To?<br />
<i>[We didn't want to keep throwing resources at testing integration with a discontinued app.  --J.]</i><br />
Trying to make sure we can&#8217;t use ImageReady CS2 with PsCS3 so we are forced to buy Fireworks for Rollovers, animated gifs and such? A sad development.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ann Shelbourne</title>
		<link>http://blogs.adobe.com/jnack/2008/01/putting_video_inside_the_photoshop_ui.html#comment-6685</link>
		<dc:creator>Ann Shelbourne</dc:creator>
		<pubDate>Mon, 04 Feb 2008 09:48:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/01/putting-video-inside-the-photoshop-ui.html#comment-6685</guid>
		<description><![CDATA[Brilliant, Jim!
That exactly encapsulates my worst nightmare and I am much relieved to see that John has no intention of taking us down that route.
[And he had better not have …!]
:)
]]></description>
		<content:encoded><![CDATA[<p>Brilliant, Jim!<br />
That exactly encapsulates my worst nightmare and I am much relieved to see that John has no intention of taking us down that route.<br />
[And he had better not have …!]<br />
:)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jimhere</title>
		<link>http://blogs.adobe.com/jnack/2008/01/putting_video_inside_the_photoshop_ui.html#comment-6684</link>
		<dc:creator>jimhere</dc:creator>
		<pubDate>Mon, 04 Feb 2008 07:52:14 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/01/putting-video-inside-the-photoshop-ui.html#comment-6684</guid>
		<description><![CDATA[I actually agree that it&#039;s be OK to have learner-videos somewhere. I just hope that Adobe pays saleries to &quot;healing Brush&quot; type efforts first.
I noticed that John replied to most of Anne S&#039;s points &lt;i&gt;except&lt;/i&gt; he was silent on
&lt;i&gt;...And if your plans include any thought of giving us a GUI that resembles Lightroom&#039;s in any way — just forget it right now!&lt;/i&gt;
so I figured I&#039;d see what it would look like.
I just had a baby,
&lt;i&gt;[Congrats!!  We&#039;re T-minus one month exactly.  --J.]&lt;/i&gt;
so I had some five-minute blocks over the weekend. I made this mockup of what I suspect PS wants to look like:
&lt;a href=&quot;http://homepage.mac.com/jimpogo/psLR/&quot; rel=&quot;nofollow&quot;&gt;&lt;a href=&quot;http://homepage.mac.com/jimpogo/psLR/&quot; rel=&quot;nofollow&quot;&gt;http://homepage.mac.com/jimpogo/psLR/&lt;/a&gt;&lt;/a&gt;
It&#039;s Flash so it stretches and clicking or mousing over things show my comments.
IS this the future, John?
(I prefer CS2 obviously)
&lt;i&gt;[Hah--that&#039;s pretty funny, Jim.
&lt;i&gt;Short answer: No, we&#039;re not going to take a very general, flexible application and start inserting steps where they don&#039;t exist today.  The PS and LR architectures are different, and PS isn&#039;t comprised of a series of modules.  We can, however, offer the ability to show functionality based on context.  We can make it far easier to say, &quot;Okay, Photoshop, I want to perform the following; show me just what I need to get the job done.&quot;  If people often feel overwhelmed &amp; want to know &quot;the right way&quot; to get things done, we need to take those concerns seriously.  That does not mean we have to tie the hands of people who like things as they are today.  It also doesn&#039;t mean I&#039;ll be popping up in your toolbar! ;-P  --J.]&lt;/i&gt;&lt;/i&gt;
]]></description>
		<content:encoded><![CDATA[<p>I actually agree that it&#8217;s be OK to have learner-videos somewhere. I just hope that Adobe pays saleries to &#8220;healing Brush&#8221; type efforts first.<br />
I noticed that John replied to most of Anne S&#8217;s points <i>except</i> he was silent on<br />
<i>&#8230;And if your plans include any thought of giving us a GUI that resembles Lightroom&#8217;s in any way — just forget it right now!</i><br />
so I figured I&#8217;d see what it would look like.<br />
I just had a baby,<br />
<i>[Congrats!!  We're T-minus one month exactly.  --J.]</i><br />
so I had some five-minute blocks over the weekend. I made this mockup of what I suspect PS wants to look like:<br />
<a href="http://homepage.mac.com/jimpogo/psLR/" rel="nofollow"></a><a href="http://homepage.mac.com/jimpogo/psLR/" rel="nofollow">http://homepage.mac.com/jimpogo/psLR/</a><br />
It&#8217;s Flash so it stretches and clicking or mousing over things show my comments.<br />
IS this the future, John?<br />
(I prefer CS2 obviously)<br />
<i>[Hah--that's pretty funny, Jim.<br />
</i><i>Short answer: No, we're not going to take a very general, flexible application and start inserting steps where they don't exist today.  The PS and LR architectures are different, and PS isn't comprised of a series of modules.  We can, however, offer the ability to show functionality based on context.  We can make it far easier to say, "Okay, Photoshop, I want to perform the following; show me just what I need to get the job done."  If people often feel overwhelmed &amp; want to know "the right way" to get things done, we need to take those concerns seriously.  That does not mean we have to tie the hands of people who like things as they are today.  It also doesn't mean I'll be popping up in your toolbar! ;-P  --J.]</i></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: T. Schmidt</title>
		<link>http://blogs.adobe.com/jnack/2008/01/putting_video_inside_the_photoshop_ui.html#comment-6683</link>
		<dc:creator>T. Schmidt</dc:creator>
		<pubDate>Fri, 01 Feb 2008 06:04:41 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/01/putting-video-inside-the-photoshop-ui.html#comment-6683</guid>
		<description><![CDATA[Also want to add this:
1. Those happy with the new GUI, could you give concrete examples like us others do? I&#039;ve never met any of you in real live.
2. J, I&#039;d also like to put any appleness on my list, meaning I want to be able to turn transparent panels, grey area around the panels, shiney stuff, fading windows and other new planned clutter off. Give us some right to decide what we need, please. Pro tools don&#039;t have to look futuristic.
]]></description>
		<content:encoded><![CDATA[<p>Also want to add this:<br />
1. Those happy with the new GUI, could you give concrete examples like us others do? I&#8217;ve never met any of you in real live.<br />
2. J, I&#8217;d also like to put any appleness on my list, meaning I want to be able to turn transparent panels, grey area around the panels, shiney stuff, fading windows and other new planned clutter off. Give us some right to decide what we need, please. Pro tools don&#8217;t have to look futuristic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: T. Schmidt</title>
		<link>http://blogs.adobe.com/jnack/2008/01/putting_video_inside_the_photoshop_ui.html#comment-6682</link>
		<dc:creator>T. Schmidt</dc:creator>
		<pubDate>Fri, 01 Feb 2008 05:55:38 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/01/putting-video-inside-the-photoshop-ui.html#comment-6682</guid>
		<description><![CDATA[Phil, I agree with you, that Ps is not designed for one person and that&#039;s why I talk to other users constantly and you are an exception (one person, just like me).
J, the perfect way to make us all happy is to get a professional mode or CS2ish mode with the well, no icons, no pop ups (as a heavy user I can decide what I want, when I want it, don&#039;t need ANY pop ups), no additional Screen Mode. Then you could stuff all the help things into one newbie or learning mode but save us others lots of time.
As a heavy user I&#039;d like to see more customizability towards simplicity, meaning being able to turn all the junk off either at once or better yet separately (well on/off, icons on/off, etc.). This way you&#039;ll have a bigger chance to get your new ideas out as a proposul instead of a must.
Every keyboard shortcut should be customizeable in a pro mode (even shift tab for window switching). Every Screen Mode should be optional. Then I&#039;d only have to customize my workspace once and never worry about it again (which is the basic idea anyway).
The pro mode should be the standard mode of course.
]]></description>
		<content:encoded><![CDATA[<p>Phil, I agree with you, that Ps is not designed for one person and that&#8217;s why I talk to other users constantly and you are an exception (one person, just like me).<br />
J, the perfect way to make us all happy is to get a professional mode or CS2ish mode with the well, no icons, no pop ups (as a heavy user I can decide what I want, when I want it, don&#8217;t need ANY pop ups), no additional Screen Mode. Then you could stuff all the help things into one newbie or learning mode but save us others lots of time.<br />
As a heavy user I&#8217;d like to see more customizability towards simplicity, meaning being able to turn all the junk off either at once or better yet separately (well on/off, icons on/off, etc.). This way you&#8217;ll have a bigger chance to get your new ideas out as a proposul instead of a must.<br />
Every keyboard shortcut should be customizeable in a pro mode (even shift tab for window switching). Every Screen Mode should be optional. Then I&#8217;d only have to customize my workspace once and never worry about it again (which is the basic idea anyway).<br />
The pro mode should be the standard mode of course.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://blogs.adobe.com/jnack/2008/01/putting_video_inside_the_photoshop_ui.html#comment-6681</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Thu, 31 Jan 2008 22:42:39 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/01/putting-video-inside-the-photoshop-ui.html#comment-6681</guid>
		<description><![CDATA[The discussion derailed a bit! It&#039;s not about Photoshop UI, it&#039;s about Photoshop extensibility! :)
The video tutorial in Photoshop is just a commonly understandable exemple of what could be possible with this technology.
It maybe doesnt mean much to most of the users but it&#039;s really a desirable thing for third-party developpers... wich in the end could be developping tools that you will not be able to live without!
As a developper (and also a power user) working on complex project, it is one of my concern that the tools i create for our production needs are not too difficult and use the adequate UI controls for the task(who really likes to enter hexadecimal color in a field box instead of using color picker?). And a it&#039;s a real plus if i can integrate the tool seamlessly in the software (not everybody have  30&#039; screen).
For my own work, it&#039;s important that i&#039;m able to adress such need without having to go through heavy software developpement cycle (production is now.. not next year) developping a interface in flash is way easier than using ADM in the C++ SDK (or what&#039;s available with Javascript api). More than that, if the interface can be done in flash... the designer i&#039;m developping the tool for can help design the interface at his own taste! Now, it&#039;s interessing!:)
Sure, being able to do such thing (in flash) will not help very much with UI consistency: we know HOW CREATIVE interface designers can be with flash. Too much! But personnaly i think that anything is better than having to switch to desktop and have to double-click on a script! (having scripts in Menu or accesible in a script palette is already an improvement.. but is missing alot of flexibility).
Sure, you can already drive photoshop and have complex user interface by using Visual Basic or Cocoa environnement, but you only get another application OUTSIDE photoshop, just like bridge.
Having a palette (non-modal) in the software is way better and that is why i personnaly see this upcomming feature with great enthousiasm. I surely know what i could do with this!
It&#039;s true that there isnt alot of very high quality exemple available (production worthy) of what&#039;s possible with extensibility (aside from pluggins world).
But to give a exemple from flash world (flash extensibility), go have a look at Grant Skinner work: &lt;a href=&quot;http://www.gskinner.com/products/gProject/about.php.&quot; rel=&quot;nofollow&quot;&gt;http://www.gskinner.com/products/gProject/about.php.&lt;/a&gt; That  is showing a great concern on usability, design and also productivity. I also really wonder why such feature was not implemented in flash already!
As a last exemple, imagine you would have a project (in photoshop) involving documents with few hundreds layers. A search tool could be usefull, no?
What if you could have a developper do it for you in few days (or better download it from someone that did it before) instead of waiting for Adobe to do it (not like you want) in CS8?
There is alot that can be done already (scripted automation/Pluggin SDK had been there for years)... but there definitively a place for more. I almost dream of it.
And hopefully the tool that will be created (with better Photoshop extensibility) will bring back a smile to those that are not enjoying photoshop anymore! ah! ah! :)
]]></description>
		<content:encoded><![CDATA[<p>The discussion derailed a bit! It&#8217;s not about Photoshop UI, it&#8217;s about Photoshop extensibility! :)<br />
The video tutorial in Photoshop is just a commonly understandable exemple of what could be possible with this technology.<br />
It maybe doesnt mean much to most of the users but it&#8217;s really a desirable thing for third-party developpers&#8230; wich in the end could be developping tools that you will not be able to live without!<br />
As a developper (and also a power user) working on complex project, it is one of my concern that the tools i create for our production needs are not too difficult and use the adequate UI controls for the task(who really likes to enter hexadecimal color in a field box instead of using color picker?). And a it&#8217;s a real plus if i can integrate the tool seamlessly in the software (not everybody have  30&#8242; screen).<br />
For my own work, it&#8217;s important that i&#8217;m able to adress such need without having to go through heavy software developpement cycle (production is now.. not next year) developping a interface in flash is way easier than using ADM in the C++ SDK (or what&#8217;s available with Javascript api). More than that, if the interface can be done in flash&#8230; the designer i&#8217;m developping the tool for can help design the interface at his own taste! Now, it&#8217;s interessing!:)<br />
Sure, being able to do such thing (in flash) will not help very much with UI consistency: we know HOW CREATIVE interface designers can be with flash. Too much! But personnaly i think that anything is better than having to switch to desktop and have to double-click on a script! (having scripts in Menu or accesible in a script palette is already an improvement.. but is missing alot of flexibility).<br />
Sure, you can already drive photoshop and have complex user interface by using Visual Basic or Cocoa environnement, but you only get another application OUTSIDE photoshop, just like bridge.<br />
Having a palette (non-modal) in the software is way better and that is why i personnaly see this upcomming feature with great enthousiasm. I surely know what i could do with this!<br />
It&#8217;s true that there isnt alot of very high quality exemple available (production worthy) of what&#8217;s possible with extensibility (aside from pluggins world).<br />
But to give a exemple from flash world (flash extensibility), go have a look at Grant Skinner work: <a href="http://www.gskinner.com/products/gProject/about.php." rel="nofollow"></a><a href="http://www.gskinner.com/products/gProject/about.php" rel="nofollow">http://www.gskinner.com/products/gProject/about.php</a>. That  is showing a great concern on usability, design and also productivity. I also really wonder why such feature was not implemented in flash already!<br />
As a last exemple, imagine you would have a project (in photoshop) involving documents with few hundreds layers. A search tool could be usefull, no?<br />
What if you could have a developper do it for you in few days (or better download it from someone that did it before) instead of waiting for Adobe to do it (not like you want) in CS8?<br />
There is alot that can be done already (scripted automation/Pluggin SDK had been there for years)&#8230; but there definitively a place for more. I almost dream of it.<br />
And hopefully the tool that will be created (with better Photoshop extensibility) will bring back a smile to those that are not enjoying photoshop anymore! ah! ah! :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Troy Stein</title>
		<link>http://blogs.adobe.com/jnack/2008/01/putting_video_inside_the_photoshop_ui.html#comment-6680</link>
		<dc:creator>Troy Stein</dc:creator>
		<pubDate>Thu, 31 Jan 2008 19:21:04 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/01/putting-video-inside-the-photoshop-ui.html#comment-6680</guid>
		<description><![CDATA[News flash:  you and I may not be an average user.
Consider for a second that we may be different from the average user.  I am product manager at another software company. I see computer novices using pro software all the time.  They buy pro-level software because *they want to be* a pro.  Not because they are one.
I think John&#039;s idea is very well intended to help people become pros like you.   Yes a better UI might help them be even more pro-ficient.  But, given the size and resources of PS dev team, I think his team could do both.
I for one love the concept.  I think video (flash) communicates more clearly and precisely than text does.  If only I had an image or video to convey this message, then you could have saved all this time reading. ;-)
]]></description>
		<content:encoded><![CDATA[<p>News flash:  you and I may not be an average user.<br />
Consider for a second that we may be different from the average user.  I am product manager at another software company. I see computer novices using pro software all the time.  They buy pro-level software because *they want to be* a pro.  Not because they are one.<br />
I think John&#8217;s idea is very well intended to help people become pros like you.   Yes a better UI might help them be even more pro-ficient.  But, given the size and resources of PS dev team, I think his team could do both.<br />
I for one love the concept.  I think video (flash) communicates more clearly and precisely than text does.  If only I had an image or video to convey this message, then you could have saved all this time reading. ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ric Cohn</title>
		<link>http://blogs.adobe.com/jnack/2008/01/putting_video_inside_the_photoshop_ui.html#comment-6679</link>
		<dc:creator>Ric Cohn</dc:creator>
		<pubDate>Thu, 31 Jan 2008 15:14:49 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/01/putting-video-inside-the-photoshop-ui.html#comment-6679</guid>
		<description><![CDATA[I&#039;ve posted lengthy critiques of the new GUI on the Photoshop Feature Request site, so I won&#039;t repeat them here. I have also listed a few things I actually like about the new pallets (basically that they adjust themselves). I don&#039;t think it&#039;s impossible to improve on CS2, but I completely agree with those who complain that the new GUI is a time drag on many &quot;Photoshop-pro&quot; users. I have heard many complaints and very few Kudos from other professional photographers and retouchers that I have spoken about this with.
Before anyone gets bent out of shape because they don&#039;t hate the new GUI and don&#039;t consider themselves amateurs I&#039;ll qualify what I mean by &quot;pro&quot;. I&#039;m a commercial photographer and a retoucher. I frequently have to sit down at a new computer and start right in using Photoshop. I bring along a USB Drive with my Keyboard Shortcuts and some Actions and Workspaces to help me get around some of the problems with the GUI. It&#039;s not always possible to load these, and it would be better if the defaults for Photoshop hadn&#039;t been so badly broken. In a production environment I need to be fast and efficient so I can concentrate on what I&#039;m really trying to do which is make images. When a program slows me down (even a little) in doing something that is repeated many times in a day it&#039;s annoying. When it used to be better and gets worse it&#039;s very annoying! When problems are pointed out in a &quot;Beta&quot; stage and there&#039;s no chance of fixing things it makes you wonder what a Public Beta (and a Feature Request forum) are for. I&#039;m hoping the feedback I see here will be acted on. Thanks for hosting it.
]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve posted lengthy critiques of the new GUI on the Photoshop Feature Request site, so I won&#8217;t repeat them here. I have also listed a few things I actually like about the new pallets (basically that they adjust themselves). I don&#8217;t think it&#8217;s impossible to improve on CS2, but I completely agree with those who complain that the new GUI is a time drag on many &#8220;Photoshop-pro&#8221; users. I have heard many complaints and very few Kudos from other professional photographers and retouchers that I have spoken about this with.<br />
Before anyone gets bent out of shape because they don&#8217;t hate the new GUI and don&#8217;t consider themselves amateurs I&#8217;ll qualify what I mean by &#8220;pro&#8221;. I&#8217;m a commercial photographer and a retoucher. I frequently have to sit down at a new computer and start right in using Photoshop. I bring along a USB Drive with my Keyboard Shortcuts and some Actions and Workspaces to help me get around some of the problems with the GUI. It&#8217;s not always possible to load these, and it would be better if the defaults for Photoshop hadn&#8217;t been so badly broken. In a production environment I need to be fast and efficient so I can concentrate on what I&#8217;m really trying to do which is make images. When a program slows me down (even a little) in doing something that is repeated many times in a day it&#8217;s annoying. When it used to be better and gets worse it&#8217;s very annoying! When problems are pointed out in a &#8220;Beta&#8221; stage and there&#8217;s no chance of fixing things it makes you wonder what a Public Beta (and a Feature Request forum) are for. I&#8217;m hoping the feedback I see here will be acted on. Thanks for hosting it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Brown</title>
		<link>http://blogs.adobe.com/jnack/2008/01/putting_video_inside_the_photoshop_ui.html#comment-6678</link>
		<dc:creator>Phil Brown</dc:creator>
		<pubDate>Thu, 31 Jan 2008 14:58:15 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/01/putting-video-inside-the-photoshop-ui.html#comment-6678</guid>
		<description><![CDATA[T - I agree that you don&#039;t want to spend more time, but not everyone is spending more time.  I find my workflow improved, as do many other pros I know.  I&#039;m sure that&#039;s not the case for everyone, but neither is it true that things are worse across the board.
Sure, there&#039;s time spent learning new ways of doing things, but once learned, they are often better / faster / easier.  Sometimes they&#039;re not and that&#039;s worth making some noise about (for example, loss of sticky print settings under Windows, which was returned in the 10.0.1 update).
I can assure you that I use PS a lot, both for my full time job (3rd level technical related) and my part time (photography), but certainly not as much as some people (and probably not as much as you).
Once again, I think it needs stressing that this is not an app designed for an individual, but what John is fairly clearly saying is that they want to provide the ability for that to be the case - you will be able to work in various ways, with various preferences and options, and have them saved for you.  In effect, you&#039;d be running PS-T.Schmidt while Anne would have PS.Anne and I would have PS.Phil.
Surely that&#039;s worth doing?  The alternative is that they need to balance the wants and desires of all users and provide a single path.  When that happens, you typically have 2 choices - a general path that doesn&#039;t suit anyone too much, but isn&#039;t too horrible either, or a specific path that suits one group and another not at all.
It *must* be better to go the way of customisation and allowing users to choose their own path through the app, surely?
Anyway, I&#039;m taking up a too much of John&#039;s blog of late, so enough from me except to say: Jim, nice analogy - well said :-)
]]></description>
		<content:encoded><![CDATA[<p>T &#8211; I agree that you don&#8217;t want to spend more time, but not everyone is spending more time.  I find my workflow improved, as do many other pros I know.  I&#8217;m sure that&#8217;s not the case for everyone, but neither is it true that things are worse across the board.<br />
Sure, there&#8217;s time spent learning new ways of doing things, but once learned, they are often better / faster / easier.  Sometimes they&#8217;re not and that&#8217;s worth making some noise about (for example, loss of sticky print settings under Windows, which was returned in the 10.0.1 update).<br />
I can assure you that I use PS a lot, both for my full time job (3rd level technical related) and my part time (photography), but certainly not as much as some people (and probably not as much as you).<br />
Once again, I think it needs stressing that this is not an app designed for an individual, but what John is fairly clearly saying is that they want to provide the ability for that to be the case &#8211; you will be able to work in various ways, with various preferences and options, and have them saved for you.  In effect, you&#8217;d be running PS-T.Schmidt while Anne would have PS.Anne and I would have PS.Phil.<br />
Surely that&#8217;s worth doing?  The alternative is that they need to balance the wants and desires of all users and provide a single path.  When that happens, you typically have 2 choices &#8211; a general path that doesn&#8217;t suit anyone too much, but isn&#8217;t too horrible either, or a specific path that suits one group and another not at all.<br />
It *must* be better to go the way of customisation and allowing users to choose their own path through the app, surely?<br />
Anyway, I&#8217;m taking up a too much of John&#8217;s blog of late, so enough from me except to say: Jim, nice analogy &#8211; well said :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ann Shelbourne</title>
		<link>http://blogs.adobe.com/jnack/2008/01/putting_video_inside_the_photoshop_ui.html#comment-6677</link>
		<dc:creator>Ann Shelbourne</dc:creator>
		<pubDate>Thu, 31 Jan 2008 13:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/01/putting-video-inside-the-photoshop-ui.html#comment-6677</guid>
		<description><![CDATA[&gt;Meanwhile, the things that we really NEED to have addressed:
(like putting all of the palettes (except Curves) back to the way that they were in CS2;
&gt;[You can&#039;t just drag them out (so that they float, if that&#039;s what you want), then save a workspace? --J.]
I know that (and do so with Layers, History and Info) but what I would like to see is a return to the &quot;traffic lights&quot;
palette-closing  buttons of CS2 or the replacement of the badly designed minuscule palette-controls in the RHS top corners of CS3 palettes.
I also would like to see the return of the Well.
But the most irksome item to me for the way that I work is the design of the history palette. If it is really beyond the capabilities of your programmers to insert a second set of scrollers, please could the Snapshots have their own palette separately from the History States palette. (Obviously the extra Scroller would be the preferable solution.)
]]></description>
		<content:encoded><![CDATA[<p>&gt;Meanwhile, the things that we really NEED to have addressed:<br />
(like putting all of the palettes (except Curves) back to the way that they were in CS2;<br />
&gt;[You can't just drag them out (so that they float, if that's what you want), then save a workspace? --J.]<br />
I know that (and do so with Layers, History and Info) but what I would like to see is a return to the &#8220;traffic lights&#8221;<br />
palette-closing  buttons of CS2 or the replacement of the badly designed minuscule palette-controls in the RHS top corners of CS3 palettes.<br />
I also would like to see the return of the Well.<br />
But the most irksome item to me for the way that I work is the design of the history palette. If it is really beyond the capabilities of your programmers to insert a second set of scrollers, please could the Snapshots have their own palette separately from the History States palette. (Obviously the extra Scroller would be the preferable solution.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ann Shelbourne</title>
		<link>http://blogs.adobe.com/jnack/2008/01/putting_video_inside_the_photoshop_ui.html#comment-6676</link>
		<dc:creator>Ann Shelbourne</dc:creator>
		<pubDate>Thu, 31 Jan 2008 10:33:58 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/01/putting-video-inside-the-photoshop-ui.html#comment-6676</guid>
		<description><![CDATA[&gt;Trying to make it easier to use doesn&#039;t mean that Photoshop shouldn&#039;t also grow easier, however.&gt;
What I fear is that your attempts to &quot;make it easier to use&quot; is going to slow Photoshop down;
&lt;i&gt;[I hear you, and we take that concern very seriously.  --J.]&lt;/i&gt;
put road-blocks (like your abysmal &quot;Maximized Screen Mode&quot; in our way; and fill our hard drives with uncalled-for &quot;Bloat&quot; from built-in Flash tutorials.
&lt;i&gt;[This point bears repeating: I&#039;m talking about customizability.  The whole point is to let you bring forward what you care about while removing what you consider &quot;bloat&quot;--and to do so very, very easily.  --J.]&lt;/i&gt;
Meanwhile, the things that we really NEED to have addressed:
(like putting all of the palettes (except Curves) back to the way that they were in CS2;
&lt;i&gt;[You can&#039;t just drag them out (so that they float, if that&#039;s what you want), then save a workspace?  --J.]&lt;/i&gt;
allowing multiple selection of Paths and Channels;
and giving the History Palette that long-overdue second Scroller (so that States and Snapshots can be scrolled individually);
will continue to be ignored.
&lt;i&gt;[Believe it or not, things that seem simple (such as having two scrollers in History) frequently aren&#039;t.  That&#039;s not to say that they shouldn&#039;t happen, but sometimes we have to invest a fair bit in the underlying architecture in order to get there, and that&#039;s what we&#039;re doing.  --J.]&lt;/i&gt;
And if your plans include any thought of giving us a GUI that resembles Lightroom&#039;s in any way — just forget it right now!
Or give us a way to set our Prefs so that we NEVER have to endure: &quot;Maximized&quot; and its Panels;
a Lightroom-type GUI with dark palettes;
or Flash movie tutorials.
]]></description>
		<content:encoded><![CDATA[<p>&gt;Trying to make it easier to use doesn&#8217;t mean that Photoshop shouldn&#8217;t also grow easier, however.&gt;<br />
What I fear is that your attempts to &#8220;make it easier to use&#8221; is going to slow Photoshop down;<br />
<i>[I hear you, and we take that concern very seriously.  --J.]</i><br />
put road-blocks (like your abysmal &#8220;Maximized Screen Mode&#8221; in our way; and fill our hard drives with uncalled-for &#8220;Bloat&#8221; from built-in Flash tutorials.<br />
<i>[This point bears repeating: I'm talking about customizability.  The whole point is to let you bring forward what you care about while removing what you consider "bloat"--and to do so very, very easily.  --J.]</i><br />
Meanwhile, the things that we really NEED to have addressed:<br />
(like putting all of the palettes (except Curves) back to the way that they were in CS2;<br />
<i>[You can't just drag them out (so that they float, if that's what you want), then save a workspace?  --J.]</i><br />
allowing multiple selection of Paths and Channels;<br />
and giving the History Palette that long-overdue second Scroller (so that States and Snapshots can be scrolled individually);<br />
will continue to be ignored.<br />
<i>[Believe it or not, things that seem simple (such as having two scrollers in History) frequently aren't.  That's not to say that they shouldn't happen, but sometimes we have to invest a fair bit in the underlying architecture in order to get there, and that's what we're doing.  --J.]</i><br />
And if your plans include any thought of giving us a GUI that resembles Lightroom&#8217;s in any way — just forget it right now!<br />
Or give us a way to set our Prefs so that we NEVER have to endure: &#8220;Maximized&#8221; and its Panels;<br />
a Lightroom-type GUI with dark palettes;<br />
or Flash movie tutorials.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: T. Schmidt</title>
		<link>http://blogs.adobe.com/jnack/2008/01/putting_video_inside_the_photoshop_ui.html#comment-6675</link>
		<dc:creator>T. Schmidt</dc:creator>
		<pubDate>Thu, 31 Jan 2008 08:42:34 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/01/putting-video-inside-the-photoshop-ui.html#comment-6675</guid>
		<description><![CDATA[J, I understand that you THINK the new GUI makes Ps simpler but the problem is, that it doesn&#039;t. The one&#039;s who haven&#039;t used it, can&#039;t tell and the one&#039;s who&#039;ve used Ps lose lots of time getting around it.
Like already mentioned by others I get the impression that you are less of a Ps user and more of a business man and promoter (and you&#039;re probably really good at that).
&lt;i&gt;[I wouldn&#039;t necessarily agree with either assertion. ;-)  I started using Photoshop with v2.5 and spent four years using it professionally every day before I came to Adobe.  Since then it&#039;s true that I don&#039;t get to live in the app as I once did, but I try to carve out as much time as possible to use it (mainly for photography these days).  --J.]&lt;/i&gt;
Can you explain why you force us to use your beginner gimmicks, instead of putting them into a Basic mode?
&lt;i&gt;[I don&#039;t know what &quot;basic&quot; gimmicks we&#039;ve added.  --J.]&lt;/i&gt;
You asked for examples: The new Screen Mode, good for nothing, takes additional F hit to avoid. The Tool bar hiding the Ruler origin (0/0) which I need a lot, so I always have to tab it off. The icons, look cute but do nothing else than the Palette well did in a much better less cluttering way, now completely wasted room.
&lt;i&gt;[The design is a work in progress.  The move from palette well to consistent side-stashing of panels will become a clearer win over time.  I grant that there are currently pros and cons.  --J.]&lt;/i&gt;
Panels pop up WHILE drawing a selection line with the Polygonal lasso on both sides of the screen. Why would I want to use a panel WHILE I&#039;m drawing a line?
&lt;i&gt;[Good point.  We need to add a preference to suppress the auto-reveal of panels, and we should always suppress it while you&#039;re drawing.  --J.]&lt;/i&gt;
The curser then adds another symbol and so on and so on. It&#039;s not possible to compare images like it used to be, with one image in FS mode and one in Standard window mode. Why did you do all that (each)? Thanks.
&lt;i&gt;[I&#039;m typing this from the floor of the Vegas convention center and can&#039;t get into all the specifics right now.  I know a lot of work went into trying to balance consistency across the apps against each app&#039;s particular needs and history.  (We catch a beating in either direction.)  --J.]&lt;/i&gt;
Of course Smart Filters are highly appreciated but do I have to give up usability for the balance? Can&#039;t you understand that when you work with Spot Colors everyday for years and always hope for an upgrade or at leat the possibility to select more than one channel, that it&#039;s kind of strange to see so much effort going into gimmicks?
Lightroom is full of that nonsence with skinning and tatooing little Yin Yang symbols all over the app but please not Ps. Stuff that into Elements and Lightroom.
&lt;i&gt;[Would you feel better if I said that we&#039;re not going to devote time to putting any &quot;tramp stamps&quot; into PS? :-)  --J.]&lt;/i&gt;
]]></description>
		<content:encoded><![CDATA[<p>J, I understand that you THINK the new GUI makes Ps simpler but the problem is, that it doesn&#8217;t. The one&#8217;s who haven&#8217;t used it, can&#8217;t tell and the one&#8217;s who&#8217;ve used Ps lose lots of time getting around it.<br />
Like already mentioned by others I get the impression that you are less of a Ps user and more of a business man and promoter (and you&#8217;re probably really good at that).<br />
<i>[I wouldn't necessarily agree with either assertion. ;-)  I started using Photoshop with v2.5 and spent four years using it professionally every day before I came to Adobe.  Since then it's true that I don't get to live in the app as I once did, but I try to carve out as much time as possible to use it (mainly for photography these days).  --J.]</i><br />
Can you explain why you force us to use your beginner gimmicks, instead of putting them into a Basic mode?<br />
<i>[I don't know what "basic" gimmicks we've added.  --J.]</i><br />
You asked for examples: The new Screen Mode, good for nothing, takes additional F hit to avoid. The Tool bar hiding the Ruler origin (0/0) which I need a lot, so I always have to tab it off. The icons, look cute but do nothing else than the Palette well did in a much better less cluttering way, now completely wasted room.<br />
<i>[The design is a work in progress.  The move from palette well to consistent side-stashing of panels will become a clearer win over time.  I grant that there are currently pros and cons.  --J.]</i><br />
Panels pop up WHILE drawing a selection line with the Polygonal lasso on both sides of the screen. Why would I want to use a panel WHILE I&#8217;m drawing a line?<br />
<i>[Good point.  We need to add a preference to suppress the auto-reveal of panels, and we should always suppress it while you're drawing.  --J.]</i><br />
The curser then adds another symbol and so on and so on. It&#8217;s not possible to compare images like it used to be, with one image in FS mode and one in Standard window mode. Why did you do all that (each)? Thanks.<br />
<i>[I'm typing this from the floor of the Vegas convention center and can't get into all the specifics right now.  I know a lot of work went into trying to balance consistency across the apps against each app's particular needs and history.  (We catch a beating in either direction.)  --J.]</i><br />
Of course Smart Filters are highly appreciated but do I have to give up usability for the balance? Can&#8217;t you understand that when you work with Spot Colors everyday for years and always hope for an upgrade or at leat the possibility to select more than one channel, that it&#8217;s kind of strange to see so much effort going into gimmicks?<br />
Lightroom is full of that nonsence with skinning and tatooing little Yin Yang symbols all over the app but please not Ps. Stuff that into Elements and Lightroom.<br />
<i>[Would you feel better if I said that we're not going to devote time to putting any "tramp stamps" into PS? :-)  --J.]</i></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jimhere</title>
		<link>http://blogs.adobe.com/jnack/2008/01/putting_video_inside_the_photoshop_ui.html#comment-6674</link>
		<dc:creator>jimhere</dc:creator>
		<pubDate>Thu, 31 Jan 2008 06:40:24 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2008/01/putting-video-inside-the-photoshop-ui.html#comment-6674</guid>
		<description><![CDATA[Sorry about my tone, I suppose PS matters too much to me (what would my 20th century self have thought?). As Socrates would say, no one is a &lt;i&gt;complete&lt;/i&gt; Photoshop expert. John and Phil Brown are right -- If there are those who need the extra help, go for it. I (obviously) worry that work on image-editing tools would fall behind because people would be put on this project instead.
&#039;Philosopher&#039; is not a swipe (&lt;i&gt;someone&lt;/i&gt; has to think big). I don&#039;t work for a software company so I probably don&#039;t really know what a &#039;PM&#039; is. So I sometimes think John is loosing the trees for the sake of the forest (sorry about the cliche). Keep a little Aristotle in there with those other two Greek guys.
&lt;i&gt;[Don&#039;t worry; I&#039;m in here making out with the trees every day!  I do appreciate the follow up.  --J.]&lt;/i&gt;
Bust seriously -- I&#039;m not being sarcastic here -- what is the difference supposed to be between PS and PS Elements? I truly thought that Elements was for entry-level users.
&lt;i&gt;[Elements is for hobbyists who don&#039;t need or want the full power of Photoshop.  Trying to make it easier to use doesn&#039;t mean that Photoshop shouldn&#039;t also grow easier, however.  --J.]&lt;/i&gt;
]]></description>
		<content:encoded><![CDATA[<p>Sorry about my tone, I suppose PS matters too much to me (what would my 20th century self have thought?). As Socrates would say, no one is a <i>complete</i> Photoshop expert. John and Phil Brown are right &#8212; If there are those who need the extra help, go for it. I (obviously) worry that work on image-editing tools would fall behind because people would be put on this project instead.<br />
&#8216;Philosopher&#8217; is not a swipe (<i>someone</i> has to think big). I don&#8217;t work for a software company so I probably don&#8217;t really know what a &#8216;PM&#8217; is. So I sometimes think John is loosing the trees for the sake of the forest (sorry about the cliche). Keep a little Aristotle in there with those other two Greek guys.<br />
<i>[Don't worry; I'm in here making out with the trees every day!  I do appreciate the follow up.  --J.]</i><br />
Bust seriously &#8212; I&#8217;m not being sarcastic here &#8212; what is the difference supposed to be between PS and PS Elements? I truly thought that Elements was for entry-level users.<br />
<i>[Elements is for hobbyists who don't need or want the full power of Photoshop.  Trying to make it easier to use doesn't mean that Photoshop shouldn't also grow easier, however.  --J.]</i></p>
]]></content:encoded>
	</item>
</channel>
</rss>
