<?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: Feedback, please: Potential Web/drawing features in Photoshop</title>
	<atom:link href="http://blogs.adobe.com/jnack/2010/09/feedback-please-potential-webdrawing-features-in-photoshop.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blogs.adobe.com/jnack/2010/09/feedback-please-potential-webdrawing-features-in-photoshop.html</link>
	<description></description>
	<lastBuildDate>Wed, 19 Jun 2013 17:12:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Isabel</title>
		<link>http://blogs.adobe.com/jnack/2010/09/feedback-please-potential-webdrawing-features-in-photoshop.html#comment-42877</link>
		<dc:creator>Isabel</dc:creator>
		<pubDate>Sun, 01 Apr 2012 12:47:02 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=2774#comment-42877</guid>
		<description><![CDATA[Improve Fireworks! Care about your users, care for better tools and workflows, not about selling the most expensive tool to do everything, be creative!

For the sake of common sense, specialize tools instead of creating monsters. 
Why does Adobe keep promoting PS and hardly care about FW when it does anything a screen designer could dream about in the easiest, fastest and more intuitive way?

FW is the tool for screen design, and designers don&#039;t even know about its benefits, thank, in big part, to Adobe.

If ppl would realize how many good things using FW brings, Adobe would have to adopt it as its most beloved child, put some money and sell it as the best tool for the digital era, specially these days, with all the apps and devices.

Why not letting people know? 

@Jim Monaco - When u say:

 &quot;Why does it bother you that Photoshop is looking to offer its users more ways to interact with different kinds of graphical content? If Fw does everything you want and more…use it&quot; 

We can answer, that&#039;s what we do, and will keep on doing as long as it exists. That&#039;s why we worry... cause it smells like omnipotent monster PS will eat it.. sooner or later.. and that&#039;s simply absurd, but maybe not for an uncreative business that cares about making money, but not the best of the products.

Long life to common sense.]]></description>
		<content:encoded><![CDATA[<p>Improve Fireworks! Care about your users, care for better tools and workflows, not about selling the most expensive tool to do everything, be creative!</p>
<p>For the sake of common sense, specialize tools instead of creating monsters.<br />
Why does Adobe keep promoting PS and hardly care about FW when it does anything a screen designer could dream about in the easiest, fastest and more intuitive way?</p>
<p>FW is the tool for screen design, and designers don&#8217;t even know about its benefits, thank, in big part, to Adobe.</p>
<p>If ppl would realize how many good things using FW brings, Adobe would have to adopt it as its most beloved child, put some money and sell it as the best tool for the digital era, specially these days, with all the apps and devices.</p>
<p>Why not letting people know? </p>
<p>@Jim Monaco &#8211; When u say:</p>
<p> &#8220;Why does it bother you that Photoshop is looking to offer its users more ways to interact with different kinds of graphical content? If Fw does everything you want and more…use it&#8221; </p>
<p>We can answer, that&#8217;s what we do, and will keep on doing as long as it exists. That&#8217;s why we worry&#8230; cause it smells like omnipotent monster PS will eat it.. sooner or later.. and that&#8217;s simply absurd, but maybe not for an uncreative business that cares about making money, but not the best of the products.</p>
<p>Long life to common sense.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: D</title>
		<link>http://blogs.adobe.com/jnack/2010/09/feedback-please-potential-webdrawing-features-in-photoshop.html#comment-33701</link>
		<dc:creator>D</dc:creator>
		<pubDate>Thu, 31 Mar 2011 14:10:33 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=2774#comment-33701</guid>
		<description><![CDATA[Here&#039;s some brief things I could use, for web or otherwise. I&#039;m still on CS4, so if any of these are in CS5, don&#039;t be too venomous.

• Pixel accurate text layer distributing like illustrator has (I beg for this)
• Layer Styles for Groups
• Overlay Mode/Opacity/FX changes for multi-selected layers/groups
• Web-Style text rendering (based on browser if possible)
• Right click layer menu allows you to make it a background
• Break apart smart objects back into layers
• Tear Off Menus ala Autodesk Maya
• Global option to move shapes no less than 1 pixel when zoomed


btw, for you fireworks people, the reason some of us want things back in Photoshop is that we started out in web design using photoshop and imageready (and golive) for everything. Then Adobe swallowed Macromedia and they threw out the apps we had been using for years. Everyone I know just got pissed off and threw fireworks in the trash. It&#039;s nothing personal to you, but they might not see a wide adoption of fireworks when they look at the whole of the design world and cater more to the PS crowd.]]></description>
		<content:encoded><![CDATA[<p>Here&#8217;s some brief things I could use, for web or otherwise. I&#8217;m still on CS4, so if any of these are in CS5, don&#8217;t be too venomous.</p>
<p>• Pixel accurate text layer distributing like illustrator has (I beg for this)<br />
• Layer Styles for Groups<br />
• Overlay Mode/Opacity/FX changes for multi-selected layers/groups<br />
• Web-Style text rendering (based on browser if possible)<br />
• Right click layer menu allows you to make it a background<br />
• Break apart smart objects back into layers<br />
• Tear Off Menus ala Autodesk Maya<br />
• Global option to move shapes no less than 1 pixel when zoomed</p>
<p>btw, for you fireworks people, the reason some of us want things back in Photoshop is that we started out in web design using photoshop and imageready (and golive) for everything. Then Adobe swallowed Macromedia and they threw out the apps we had been using for years. Everyone I know just got pissed off and threw fireworks in the trash. It&#8217;s nothing personal to you, but they might not see a wide adoption of fireworks when they look at the whole of the design world and cater more to the PS crowd.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thiago Esser</title>
		<link>http://blogs.adobe.com/jnack/2010/09/feedback-please-potential-webdrawing-features-in-photoshop.html#comment-31030</link>
		<dc:creator>Thiago Esser</dc:creator>
		<pubDate>Mon, 27 Dec 2010 11:55:26 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=2774#comment-31030</guid>
		<description><![CDATA[These would be the best improvements for me, divided in three categories:

SIMPLE BUT EFFECTIVE
* Support dashed- and dotted-line strokes
* Preserve corner roundness when scaling rounded rectangles

MAKING LIFE EASIER
﻿* Enable panel-based editing of effects (instead of relying on a dialog box)

MAKING LIFE REALLY EASIER
* Support linked files (i.e. edit one file to update buttons, icons, etc. across multiple PSDs)]]></description>
		<content:encoded><![CDATA[<p>These would be the best improvements for me, divided in three categories:</p>
<p>SIMPLE BUT EFFECTIVE<br />
* Support dashed- and dotted-line strokes<br />
* Preserve corner roundness when scaling rounded rectangles</p>
<p>MAKING LIFE EASIER<br />
﻿* Enable panel-based editing of effects (instead of relying on a dialog box)</p>
<p>MAKING LIFE REALLY EASIER<br />
* Support linked files (i.e. edit one file to update buttons, icons, etc. across multiple PSDs)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ev149</title>
		<link>http://blogs.adobe.com/jnack/2010/09/feedback-please-potential-webdrawing-features-in-photoshop.html#comment-31024</link>
		<dc:creator>ev149</dc:creator>
		<pubDate>Mon, 27 Dec 2010 02:45:26 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=2774#comment-31024</guid>
		<description><![CDATA[In order from most important to least important:
7, 4, 6, 8, 3, 5, 1, 10, 2, 9]]></description>
		<content:encoded><![CDATA[<p>In order from most important to least important:<br />
7, 4, 6, 8, 3, 5, 1, 10, 2, 9</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PECourtejoie</title>
		<link>http://blogs.adobe.com/jnack/2010/09/feedback-please-potential-webdrawing-features-in-photoshop.html#comment-31000</link>
		<dc:creator>PECourtejoie</dc:creator>
		<pubDate>Sun, 26 Dec 2010 05:29:58 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=2774#comment-31000</guid>
		<description><![CDATA[I hope that I&#039;m not beating a dead horse, but I came over this thread in the U2U. http://forums.adobe.com/thread/668882?tstart=0

Excerpts: 
&quot;The automation, which made Photoshop such a great tool for rollovers, has been completely stripped from all recent versions.
 
With CS or CS2, I could set the save for web preferences, then easily create a single image with one layer and three states. Assign visibility for states then Save For Web a single time (2 clicks total) and get three files.
 
Now, I must save, alter visibility, save, alter visibility, save (totaling no less than 8 clicks) to end with the same resulting files.
 
If I needed to, say alter text on a button, one change and one save got me all new images for each state. Now..  three changes (one for each Layer comp) and 3 saves at a minimum are needed. So, in essence, all work was tripled.&quot;

&quot;This, combined with the lack of animated gif support, made and make CS4 and CS5 a major step backwards in terms of web production via Photoshop. Two simple features that reduced web production time by 20% or more...&quot;

&quot;The IR HTML was junk and I never used it and advised others to throw it away. What I would do is dump all the output except the images folder... that images folder was a fantastic timesaver. Where IR shined was multiple images saved for web via states in one fell swoop. States allowed one edit to be seen across all states.&quot;

&quot;All I really would like to see return is the Web Content panel from IR. No image maps, no HTML output, none of that. In fact, if the Layer Comp panel were simply beefed up to add the states options and when Save for Web was invoked there was an option to save all states from the layer comp, that would do it.
 
In fact... the ability to save multiple layer comps as individual files in the Save For Web dialog would do it as well. Looking at Illustrator... Save For Web there needs the ability to choose which artboard (or multiple artboards) to save in the Save for Web dialog. So, maybe the issue is more a need to improve the Save For Web dialog across Adobe apps rather than focus on internal application features.
 
That and the the ability to open an animated GIF and maintain both frames and transparency would bring CS6+ back to where CS2 was in terms of speeding workflow.&quot;]]></description>
		<content:encoded><![CDATA[<p>I hope that I&#8217;m not beating a dead horse, but I came over this thread in the U2U. <a href="http://forums.adobe.com/thread/668882?tstart=0" rel="nofollow">http://forums.adobe.com/thread/668882?tstart=0</a></p>
<p>Excerpts:<br />
&#8220;The automation, which made Photoshop such a great tool for rollovers, has been completely stripped from all recent versions.</p>
<p>With CS or CS2, I could set the save for web preferences, then easily create a single image with one layer and three states. Assign visibility for states then Save For Web a single time (2 clicks total) and get three files.</p>
<p>Now, I must save, alter visibility, save, alter visibility, save (totaling no less than 8 clicks) to end with the same resulting files.</p>
<p>If I needed to, say alter text on a button, one change and one save got me all new images for each state. Now..  three changes (one for each Layer comp) and 3 saves at a minimum are needed. So, in essence, all work was tripled.&#8221;</p>
<p>&#8220;This, combined with the lack of animated gif support, made and make CS4 and CS5 a major step backwards in terms of web production via Photoshop. Two simple features that reduced web production time by 20% or more&#8230;&#8221;</p>
<p>&#8220;The IR HTML was junk and I never used it and advised others to throw it away. What I would do is dump all the output except the images folder&#8230; that images folder was a fantastic timesaver. Where IR shined was multiple images saved for web via states in one fell swoop. States allowed one edit to be seen across all states.&#8221;</p>
<p>&#8220;All I really would like to see return is the Web Content panel from IR. No image maps, no HTML output, none of that. In fact, if the Layer Comp panel were simply beefed up to add the states options and when Save for Web was invoked there was an option to save all states from the layer comp, that would do it.</p>
<p>In fact&#8230; the ability to save multiple layer comps as individual files in the Save For Web dialog would do it as well. Looking at Illustrator&#8230; Save For Web there needs the ability to choose which artboard (or multiple artboards) to save in the Save for Web dialog. So, maybe the issue is more a need to improve the Save For Web dialog across Adobe apps rather than focus on internal application features.</p>
<p>That and the the ability to open an animated GIF and maintain both frames and transparency would bring CS6+ back to where CS2 was in terms of speeding workflow.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arnon Moscona</title>
		<link>http://blogs.adobe.com/jnack/2010/09/feedback-please-potential-webdrawing-features-in-photoshop.html#comment-23091</link>
		<dc:creator>Arnon Moscona</dc:creator>
		<pubDate>Mon, 27 Sep 2010 18:53:09 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=2774#comment-23091</guid>
		<description><![CDATA[Here are my top picks (ranked by importance):
* Export text &amp; graphical styles as CSS
* Support linked files (i.e. edit one file to update * buttons, icons, etc. across multiple PSDs)
* Support guide sets
* Support dashed- and dotted-line strokes
* Improve text rendering
* re-order effects
* duplicate effects
* Add/edit effects on multiple selected layers at once

Frankly, when it comes to shapes, I don&#039;t really &quot;get it&quot;. Wouldn&#039;t it make more sense to have better Illustrator integration instead of adding more and more vector functionality to Photoshop?. I&#039;d rather have &quot;Illustrator layers&quot;, and ideally a &quot;morphing ui&quot; that would switch to illustrator when you are editing an vector layer. Then photoshop would be able to use some of the illustrator objects directly (e.g. paths for stroke path etc., and maybe can continue having it&#039;s current vector capability, but when you want to do something more advanced you just right-click on a vector layer and say &quot;convert to to illustrator&quot; and go do you vector edits there.

I see no logic in duplicating too much functionality. It must come at a cost to the dev team that then cannot spend their time on improving the core (pixel) functionality of photoshop.

It would be more productive to think about illustrator and photoshop as two facets of one, well integrated product (rather than a &quot;suite&quot; or &quot;bundle&quot;. Make the sum greater than the two parts combined by making both products better aware of each other and make it easier for the user to &quot;live in one document&quot; and be focused on whet they are trying to do. Make it easier to switch back and forth between the two aspects in a seamless workflow.

All this constant tweaking of photoshop native vector capability just seems like one big distraction from where I stand...

Just my 2 cents...]]></description>
		<content:encoded><![CDATA[<p>Here are my top picks (ranked by importance):<br />
* Export text &amp; graphical styles as CSS<br />
* Support linked files (i.e. edit one file to update * buttons, icons, etc. across multiple PSDs)<br />
* Support guide sets<br />
* Support dashed- and dotted-line strokes<br />
* Improve text rendering<br />
* re-order effects<br />
* duplicate effects<br />
* Add/edit effects on multiple selected layers at once</p>
<p>Frankly, when it comes to shapes, I don&#8217;t really &#8220;get it&#8221;. Wouldn&#8217;t it make more sense to have better Illustrator integration instead of adding more and more vector functionality to Photoshop?. I&#8217;d rather have &#8220;Illustrator layers&#8221;, and ideally a &#8220;morphing ui&#8221; that would switch to illustrator when you are editing an vector layer. Then photoshop would be able to use some of the illustrator objects directly (e.g. paths for stroke path etc., and maybe can continue having it&#8217;s current vector capability, but when you want to do something more advanced you just right-click on a vector layer and say &#8220;convert to to illustrator&#8221; and go do you vector edits there.</p>
<p>I see no logic in duplicating too much functionality. It must come at a cost to the dev team that then cannot spend their time on improving the core (pixel) functionality of photoshop.</p>
<p>It would be more productive to think about illustrator and photoshop as two facets of one, well integrated product (rather than a &#8220;suite&#8221; or &#8220;bundle&#8221;. Make the sum greater than the two parts combined by making both products better aware of each other and make it easier for the user to &#8220;live in one document&#8221; and be focused on whet they are trying to do. Make it easier to switch back and forth between the two aspects in a seamless workflow.</p>
<p>All this constant tweaking of photoshop native vector capability just seems like one big distraction from where I stand&#8230;</p>
<p>Just my 2 cents&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcu</title>
		<link>http://blogs.adobe.com/jnack/2010/09/feedback-please-potential-webdrawing-features-in-photoshop.html#comment-23048</link>
		<dc:creator>Marcu</dc:creator>
		<pubDate>Fri, 24 Sep 2010 09:26:38 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=2774#comment-23048</guid>
		<description><![CDATA[Just create one super suite that does them all. In other words put all adobe apps in a blender and put out one product call adobe suite that does it all. Then there will be not more nagging and arguing about what features should and shouldn&#039;t be there.]]></description>
		<content:encoded><![CDATA[<p>Just create one super suite that does them all. In other words put all adobe apps in a blender and put out one product call adobe suite that does it all. Then there will be not more nagging and arguing about what features should and shouldn&#8217;t be there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jasonshort</title>
		<link>http://blogs.adobe.com/jnack/2010/09/feedback-please-potential-webdrawing-features-in-photoshop.html#comment-23044</link>
		<dc:creator>Jasonshort</dc:creator>
		<pubDate>Fri, 24 Sep 2010 00:24:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=2774#comment-23044</guid>
		<description><![CDATA[Please bring back the OS X File Proxy in the title bar.]]></description>
		<content:encoded><![CDATA[<p>Please bring back the OS X File Proxy in the title bar.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mantas</title>
		<link>http://blogs.adobe.com/jnack/2010/09/feedback-please-potential-webdrawing-features-in-photoshop.html#comment-22976</link>
		<dc:creator>mantas</dc:creator>
		<pubDate>Tue, 21 Sep 2010 09:26:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=2774#comment-22976</guid>
		<description><![CDATA[I am surely coming too late to a discussion and possibly with &quot;off topic&quot;  suggestion. but thereis one UI thing i love in 3dmax which i peronaly think shuld be implimented in all programs, or in win/mac save us interface (not sure who is responsible for that &quot;save as&quot; table, operating system or program. but i would love to see a small bar showing not only the last seved location, but history of folders where one has saved files before. it helps when u have lots of documents opened and one u have to save to say c/work/newproject/
and a next shoud be saved under d/forweb/updates/
or whatever... i mean when u have to save files to different locations, u spend lots of time navigating folder trees in save as dialog box. this could be easily changed... i think? here i have some pictures to make point clearer:
http://3dideas.wordpress.com/2010/02/28/what-can-program-developers-learn-from-3d-max-interface/
best,
m.]]></description>
		<content:encoded><![CDATA[<p>I am surely coming too late to a discussion and possibly with &#8220;off topic&#8221;  suggestion. but thereis one UI thing i love in 3dmax which i peronaly think shuld be implimented in all programs, or in win/mac save us interface (not sure who is responsible for that &#8220;save as&#8221; table, operating system or program. but i would love to see a small bar showing not only the last seved location, but history of folders where one has saved files before. it helps when u have lots of documents opened and one u have to save to say c/work/newproject/<br />
and a next shoud be saved under d/forweb/updates/<br />
or whatever&#8230; i mean when u have to save files to different locations, u spend lots of time navigating folder trees in save as dialog box. this could be easily changed&#8230; i think? here i have some pictures to make point clearer:<br />
<a href="http://3dideas.wordpress.com/2010/02/28/what-can-program-developers-learn-from-3d-max-interface/" rel="nofollow">http://3dideas.wordpress.com/2010/02/28/what-can-program-developers-learn-from-3d-max-interface/</a><br />
best,<br />
m.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michel</title>
		<link>http://blogs.adobe.com/jnack/2010/09/feedback-please-potential-webdrawing-features-in-photoshop.html#comment-22927</link>
		<dc:creator>Michel</dc:creator>
		<pubDate>Mon, 20 Sep 2010 13:05:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=2774#comment-22927</guid>
		<description><![CDATA[You can do this today in Adobe Fireworks:

- Press Ctrl+F,
- Type name of the font you search for, then type name of font you&#039;d like to replace it with,
- Click &quot;Replace All&quot; and you&#039;re done!

This can be 3 seconds work, done in Fireworks, today -- you don&#039;t have to wait for PS CSNext to be able to do this font replacement!

@John &amp; Co: Don&#039;t you see you&#039;re trying to &quot;re-invent the wheel&quot; in Photoshop, while the perfect app for Web design -- Fireworks -- is sitting quietly in the corner and tries to get some attention from the part of Adobe? :)

Fireworks is not only great for Web design, but it can also create &lt;a href=&quot;http://www.smashingmagazine.com/2010/09/17/the-power-of-adobe-fireworks-what-can-you-achieve-with-it/&quot; rel=&quot;nofollow&quot;&gt;perfect screen graphics&lt;/a&gt;, and faster and better than Ps or Ai, combined!

And for this purpose, Fireworks doesn&#039;t have to copy features from Photoshop, Illustrator and InDesign -- on the contrary, I see that Ps Team is trying hard to copy almost all Web features from Fw and incorporate them in Ps! ;-)]]></description>
		<content:encoded><![CDATA[<p>You can do this today in Adobe Fireworks:</p>
<p>- Press Ctrl+F,<br />
- Type name of the font you search for, then type name of font you&#8217;d like to replace it with,<br />
- Click &#8220;Replace All&#8221; and you&#8217;re done!</p>
<p>This can be 3 seconds work, done in Fireworks, today &#8212; you don&#8217;t have to wait for PS CSNext to be able to do this font replacement!</p>
<p>@John &amp; Co: Don&#8217;t you see you&#8217;re trying to &#8220;re-invent the wheel&#8221; in Photoshop, while the perfect app for Web design &#8212; Fireworks &#8212; is sitting quietly in the corner and tries to get some attention from the part of Adobe? :)</p>
<p>Fireworks is not only great for Web design, but it can also create <a href="http://www.smashingmagazine.com/2010/09/17/the-power-of-adobe-fireworks-what-can-you-achieve-with-it/" rel="nofollow">perfect screen graphics</a>, and faster and better than Ps or Ai, combined!</p>
<p>And for this purpose, Fireworks doesn&#8217;t have to copy features from Photoshop, Illustrator and InDesign &#8212; on the contrary, I see that Ps Team is trying hard to copy almost all Web features from Fw and incorporate them in Ps! ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pedro Estarque</title>
		<link>http://blogs.adobe.com/jnack/2010/09/feedback-please-potential-webdrawing-features-in-photoshop.html#comment-22919</link>
		<dc:creator>Pedro Estarque</dc:creator>
		<pubDate>Mon, 20 Sep 2010 05:13:24 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=2774#comment-22919</guid>
		<description><![CDATA[As always, thanks for asking John. Just completed the survey.

Subpixel text rendering and preserving corner roundness when scaling are my top picks.]]></description>
		<content:encoded><![CDATA[<p>As always, thanks for asking John. Just completed the survey.</p>
<p>Subpixel text rendering and preserving corner roundness when scaling are my top picks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jase</title>
		<link>http://blogs.adobe.com/jnack/2010/09/feedback-please-potential-webdrawing-features-in-photoshop.html#comment-22913</link>
		<dc:creator>Jase</dc:creator>
		<pubDate>Sun, 19 Sep 2010 23:24:55 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=2774#comment-22913</guid>
		<description><![CDATA[All the points above are definitely something we have been waiting for to be updated. However, I would love to see some of the text functionality of InDesign and Illustrator passed along, glyphs panel, tabbed paragraphs (comd \) to enable easier bullets on paragraphs, paragraph styles and character styles would also be a huge time saver.]]></description>
		<content:encoded><![CDATA[<p>All the points above are definitely something we have been waiting for to be updated. However, I would love to see some of the text functionality of InDesign and Illustrator passed along, glyphs panel, tabbed paragraphs (comd \) to enable easier bullets on paragraphs, paragraph styles and character styles would also be a huge time saver.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Beardmore</title>
		<link>http://blogs.adobe.com/jnack/2010/09/feedback-please-potential-webdrawing-features-in-photoshop.html#comment-22895</link>
		<dc:creator>James Beardmore</dc:creator>
		<pubDate>Sun, 19 Sep 2010 14:08:25 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=2774#comment-22895</guid>
		<description><![CDATA[Text rendering should be top of the list IMO.  Thanks!]]></description>
		<content:encoded><![CDATA[<p>Text rendering should be top of the list IMO.  Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Shewmaker</title>
		<link>http://blogs.adobe.com/jnack/2010/09/feedback-please-potential-webdrawing-features-in-photoshop.html#comment-22875</link>
		<dc:creator>James Shewmaker</dc:creator>
		<pubDate>Sat, 18 Sep 2010 20:51:11 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=2774#comment-22875</guid>
		<description><![CDATA[FW does not produce files which are outside of the sRGB color space. Some of us want to be able to produce these things in other color spaces.

Can you understand that sRGB is not the WHOLE purpose of Photoshop?]]></description>
		<content:encoded><![CDATA[<p>FW does not produce files which are outside of the sRGB color space. Some of us want to be able to produce these things in other color spaces.</p>
<p>Can you understand that sRGB is not the WHOLE purpose of Photoshop?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Shewmaker</title>
		<link>http://blogs.adobe.com/jnack/2010/09/feedback-please-potential-webdrawing-features-in-photoshop.html#comment-22874</link>
		<dc:creator>James Shewmaker</dc:creator>
		<pubDate>Sat, 18 Sep 2010 20:47:47 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnack/?p=2774#comment-22874</guid>
		<description><![CDATA[Apparently you misunderstood what I wrote. 

Image Ready Was for RGB only.

I know what Image Ready Was. I still have a copy of Image Ready 7 if I were to ever want to use it.

I said that I wish that PS would QUIT focusing on Web Export and start focusing on Better Vector tools in the non-RGB Color Spaces.]]></description>
		<content:encoded><![CDATA[<p>Apparently you misunderstood what I wrote. </p>
<p>Image Ready Was for RGB only.</p>
<p>I know what Image Ready Was. I still have a copy of Image Ready 7 if I were to ever want to use it.</p>
<p>I said that I wish that PS would QUIT focusing on Web Export and start focusing on Better Vector tools in the non-RGB Color Spaces.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
