<?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: Photoshop + Fireworks: Where to from here?</title>
	<atom:link href="http://blogs.adobe.com/jnack/2006/02/photoshop_fireworks_where_to_from_here.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blogs.adobe.com/jnack/2006/02/photoshop_fireworks_where_to_from_here.html</link>
	<description></description>
	<lastBuildDate>Tue, 18 Jun 2013 07:08:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Re</title>
		<link>http://blogs.adobe.com/jnack/2006/02/photoshop_fireworks_where_to_from_here.html#comment-78580</link>
		<dc:creator>Re</dc:creator>
		<pubDate>Tue, 07 May 2013 14:38:32 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2006/02/photoshop-fireworks-where-to-from-here.html#comment-78580</guid>
		<description><![CDATA[05/06/2013 It&#039;s gone :(]]></description>
		<content:encoded><![CDATA[<p>05/06/2013 It&#8217;s gone :(</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LeoReis</title>
		<link>http://blogs.adobe.com/jnack/2006/02/photoshop_fireworks_where_to_from_here.html#comment-578</link>
		<dc:creator>LeoReis</dc:creator>
		<pubDate>Tue, 24 Jun 2008 11:03:24 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2006/02/photoshop-fireworks-where-to-from-here.html#comment-578</guid>
		<description><![CDATA[I LOVE FIREWORKS!!!
]]></description>
		<content:encoded><![CDATA[<p>I LOVE FIREWORKS!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chris harley</title>
		<link>http://blogs.adobe.com/jnack/2006/02/photoshop_fireworks_where_to_from_here.html#comment-577</link>
		<dc:creator>chris harley</dc:creator>
		<pubDate>Mon, 02 Jun 2008 08:15:53 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2006/02/photoshop-fireworks-where-to-from-here.html#comment-577</guid>
		<description><![CDATA[Quick note for &#039;Bob&#039; you are going about it the wrong way, use PPT&#039;s insert/image/photo library feature and your process will be vastly simplified.
]]></description>
		<content:encoded><![CDATA[<p>Quick note for &#8216;Bob&#8217; you are going about it the wrong way, use PPT&#8217;s insert/image/photo library feature and your process will be vastly simplified.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ricky Murphy</title>
		<link>http://blogs.adobe.com/jnack/2006/02/photoshop_fireworks_where_to_from_here.html#comment-576</link>
		<dc:creator>Ricky Murphy</dc:creator>
		<pubDate>Mon, 02 Jun 2008 00:29:13 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2006/02/photoshop-fireworks-where-to-from-here.html#comment-576</guid>
		<description><![CDATA[It&#039;s all about the tools we are used to working with. I have never tried Fireworks, and I am sure it&#039;s a fine program. For what I do, PhotoShop provides both the photographic and image control for the web while Illustrator provides my vector work. DreamWeaver has tight integration with Fireworks. My only wish is if DreamWeaver can have the option to have the same tight interface with PhotoShop.
Personally I would not like to see a single &quot;super application.&quot; Each of the programs listed in the comments so far do an excellent job for what they a designed so why change what already works well (aside from some added features we all would like to see).
]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s all about the tools we are used to working with. I have never tried Fireworks, and I am sure it&#8217;s a fine program. For what I do, PhotoShop provides both the photographic and image control for the web while Illustrator provides my vector work. DreamWeaver has tight integration with Fireworks. My only wish is if DreamWeaver can have the option to have the same tight interface with PhotoShop.<br />
Personally I would not like to see a single &#8220;super application.&#8221; Each of the programs listed in the comments so far do an excellent job for what they a designed so why change what already works well (aside from some added features we all would like to see).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob</title>
		<link>http://blogs.adobe.com/jnack/2006/02/photoshop_fireworks_where_to_from_here.html#comment-575</link>
		<dc:creator>Bob</dc:creator>
		<pubDate>Tue, 27 May 2008 10:51:30 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2006/02/photoshop-fireworks-where-to-from-here.html#comment-575</guid>
		<description><![CDATA[For PNGs which use Frames, provide an &quot;Export to PowerPoint&quot; feature whereby each frame is a single slide in a PPT deck.  This makes walk-throughs much easier.  Today we have to export &quot;frames to files&quot; and then create a PPT deck and import the images into that deck one-by-one... painful!
]]></description>
		<content:encoded><![CDATA[<p>For PNGs which use Frames, provide an &#8220;Export to PowerPoint&#8221; feature whereby each frame is a single slide in a PPT deck.  This makes walk-throughs much easier.  Today we have to export &#8220;frames to files&#8221; and then create a PPT deck and import the images into that deck one-by-one&#8230; painful!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luna</title>
		<link>http://blogs.adobe.com/jnack/2006/02/photoshop_fireworks_where_to_from_here.html#comment-574</link>
		<dc:creator>Luna</dc:creator>
		<pubDate>Tue, 13 May 2008 01:33:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2006/02/photoshop-fireworks-where-to-from-here.html#comment-574</guid>
		<description><![CDATA[I remember being introduced to Fireworks 3 in 2000. With no background in design, I only took 2 hours to familiarize myself with the tool and from then created alot of websites. It&#039;s the single best graphic application for anyone. Drawing is a breeze with Fireworks. Alot of similarity with Illustrator too. I find Illustrator easier to use and learn than Photoshop. Because it&#039;s hybrid raster vector app, I only need 1 software to fix all my graphic needs :)
]]></description>
		<content:encoded><![CDATA[<p>I remember being introduced to Fireworks 3 in 2000. With no background in design, I only took 2 hours to familiarize myself with the tool and from then created alot of websites. It&#8217;s the single best graphic application for anyone. Drawing is a breeze with Fireworks. Alot of similarity with Illustrator too. I find Illustrator easier to use and learn than Photoshop. Because it&#8217;s hybrid raster vector app, I only need 1 software to fix all my graphic needs :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: minik peri</title>
		<link>http://blogs.adobe.com/jnack/2006/02/photoshop_fireworks_where_to_from_here.html#comment-573</link>
		<dc:creator>minik peri</dc:creator>
		<pubDate>Fri, 28 Mar 2008 13:55:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2006/02/photoshop-fireworks-where-to-from-here.html#comment-573</guid>
		<description><![CDATA[&quot;Do we need to improve integration between Fireworks and Photoshop (e.g. better file format compatibility, Jump To), or does it work well enough? &quot; Definitely yes to this. when psd files opened with adobe Firework they must be editable. At least their color. it can be very usefull.
]]></description>
		<content:encoded><![CDATA[<p>&#8220;Do we need to improve integration between Fireworks and Photoshop (e.g. better file format compatibility, Jump To), or does it work well enough? &#8221; Definitely yes to this. when psd files opened with adobe Firework they must be editable. At least their color. it can be very usefull.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TheJist</title>
		<link>http://blogs.adobe.com/jnack/2006/02/photoshop_fireworks_where_to_from_here.html#comment-572</link>
		<dc:creator>TheJist</dc:creator>
		<pubDate>Mon, 04 Feb 2008 22:15:49 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2006/02/photoshop-fireworks-where-to-from-here.html#comment-572</guid>
		<description><![CDATA[There&#039;s a perfectly good reason why Photoshop is used by designers; because they don&#039;t have to (and shouldn&#039;t have to) put up with the difficulties of coding and implementing what they create. Designers tend to push graphics to the limit, while coders try and push the file-sizes back down. There definitely needs to be two different programs for these two parties, Photoshop for the designers, to use all the built in filters and brushes and minimize on their workload, and Fireworks for the simple interface and genius features that make outputting for the web so much easier. Over-complicating either of these programs would be a very  bad idea.
]]></description>
		<content:encoded><![CDATA[<p>There&#8217;s a perfectly good reason why Photoshop is used by designers; because they don&#8217;t have to (and shouldn&#8217;t have to) put up with the difficulties of coding and implementing what they create. Designers tend to push graphics to the limit, while coders try and push the file-sizes back down. There definitely needs to be two different programs for these two parties, Photoshop for the designers, to use all the built in filters and brushes and minimize on their workload, and Fireworks for the simple interface and genius features that make outputting for the web so much easier. Over-complicating either of these programs would be a very  bad idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: franzgoria</title>
		<link>http://blogs.adobe.com/jnack/2006/02/photoshop_fireworks_where_to_from_here.html#comment-571</link>
		<dc:creator>franzgoria</dc:creator>
		<pubDate>Fri, 01 Feb 2008 02:59:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2006/02/photoshop-fireworks-where-to-from-here.html#comment-571</guid>
		<description><![CDATA[excuse me david (david bricker) but if you are enable to use photoshop correctly does&#039;nt means photoshop don&#039;t work well..
I think it&#039;s better for you start to learn to use photoshop and then talk about it.
Also think that photoshop is the software most used by the most important webdesigner in the world.. so start to think about it.. Bye :)
]]></description>
		<content:encoded><![CDATA[<p>excuse me david (david bricker) but if you are enable to use photoshop correctly does&#8217;nt means photoshop don&#8217;t work well..<br />
I think it&#8217;s better for you start to learn to use photoshop and then talk about it.<br />
Also think that photoshop is the software most used by the most important webdesigner in the world.. so start to think about it.. Bye :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chad</title>
		<link>http://blogs.adobe.com/jnack/2006/02/photoshop_fireworks_where_to_from_here.html#comment-570</link>
		<dc:creator>Chad</dc:creator>
		<pubDate>Thu, 10 Jan 2008 08:17:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2006/02/photoshop-fireworks-where-to-from-here.html#comment-570</guid>
		<description><![CDATA[Hi John, this is just a comment to your editorial in my recent post. I agree that layers work well when painting, touching up, and otherwise working with photos or other artwork. This was the initial intention of Photoshop, but (IMO) the ever-growing mis-use of Photoshop (esp. using it for layout design) has caused Adobe to bloat and morph the software into a one-size-fits all solution. This solution is hardly such. Unfortunately, Photoshop is known as the killer graphics app. so all the wannabes get (steal) Photoshop and perpetuate the situation instead of choosing the right graphics program for the job.
Well, I certainly didn&#039;t intend this to become a PS bash session, and nor am I so down on PS. I think the last 7 or so years for PS growth in features and capabilities has been incredible.
I hope Adobe continues to innovate and I hope that Adobe realizes that FW is a different animal and deserves a permanent place in it&#039;s lineup. I just wish Adobe would give FW more prominence by putting it on the home page under products with the rest of its flagship software.
Adobe has to educate its users about FW&#039;s capabilities and that it is NOT a PS replacement, but rather a very powerful addition (or extension, if you will) to PS. Adobe has an incredible marketing engine that can make FW or break it.
thanx
chad
]]></description>
		<content:encoded><![CDATA[<p>Hi John, this is just a comment to your editorial in my recent post. I agree that layers work well when painting, touching up, and otherwise working with photos or other artwork. This was the initial intention of Photoshop, but (IMO) the ever-growing mis-use of Photoshop (esp. using it for layout design) has caused Adobe to bloat and morph the software into a one-size-fits all solution. This solution is hardly such. Unfortunately, Photoshop is known as the killer graphics app. so all the wannabes get (steal) Photoshop and perpetuate the situation instead of choosing the right graphics program for the job.<br />
Well, I certainly didn&#8217;t intend this to become a PS bash session, and nor am I so down on PS. I think the last 7 or so years for PS growth in features and capabilities has been incredible.<br />
I hope Adobe continues to innovate and I hope that Adobe realizes that FW is a different animal and deserves a permanent place in it&#8217;s lineup. I just wish Adobe would give FW more prominence by putting it on the home page under products with the rest of its flagship software.<br />
Adobe has to educate its users about FW&#8217;s capabilities and that it is NOT a PS replacement, but rather a very powerful addition (or extension, if you will) to PS. Adobe has an incredible marketing engine that can make FW or break it.<br />
thanx<br />
chad</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chad</title>
		<link>http://blogs.adobe.com/jnack/2006/02/photoshop_fireworks_where_to_from_here.html#comment-569</link>
		<dc:creator>Chad</dc:creator>
		<pubDate>Thu, 03 Jan 2008 12:58:42 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2006/02/photoshop-fireworks-where-to-from-here.html#comment-569</guid>
		<description><![CDATA[@Joey - AMEN!
You said so many of the things that I have been thinking for years. Especially the bit about PS becoming more like FW.
Ironically, however, much of this Object based layout (rather than Photoshop&#039;s clumsy layers) came more from Corel Photopaint and Deneba Canvas years before FW.
Those of us who &quot;get it&quot; realize that object based layout is superior to Photoshop&#039;s half-baked layers concept. Strangely, even Illustrator and InDesign are object-based. Why does Adobe continue to push layers?
&lt;i&gt;[If it were a simple question of one approach being better than the other, we&#039;d have long ago adopted the better method.  The challenge is that an object-based approach is great for some things and lousy for others; same goes for Photoshop-style layers.
&lt;i&gt;Sometimes (e.g. painting, retouching) you&#039;ll very much want layers that work in the way that Photoshop originally implemented them--large, clear sheets on which you can paint.  You almost certainly *don&#039;t* want PS to create a new layer/object every time you put down a paint stroke.  (That behavior is one of the downsides to After Effects-style vector painting, which is why we implemented video painting in PS; the approaches are complementary, not redundant.)
&lt;i&gt;There are obviously times when an object-based approach works better, and Photoshop has made changes that help you work in that way (e.g. optional auto-selection of clicked layers; multiple layer selection; layer grouping; etc.).
&lt;i&gt;One problem is that we have to set the defaults just one way, and some people never bother to try switching things on/off to find a way of working they might prefer.  That&#039;s one of the many reasons I keep emphasizing the desire to make Photoshop more easily &amp; radically customizable, so that with one click you could change many aspects of the app&#039;s environment and behaviors.  --J.]&lt;/i&gt;
I think we&#039;ll see Photoshop become more and more like FW. It&#039;s now all about everything being editable all the time (a luxury that FW users have enjoyed for years and PS users are just beginning to discover)!
I&#039;ve been using FW for web design since beta 1 and I use it every day. I still use Photoshop for what Photoshop is good for, image editing and graphic creation. But, for web design/layout and quick slick web graphics, FW can&#039;t be beat.&lt;/i&gt;&lt;/i&gt;&lt;/i&gt;
]]></description>
		<content:encoded><![CDATA[<p>@Joey &#8211; AMEN!<br />
You said so many of the things that I have been thinking for years. Especially the bit about PS becoming more like FW.<br />
Ironically, however, much of this Object based layout (rather than Photoshop&#8217;s clumsy layers) came more from Corel Photopaint and Deneba Canvas years before FW.<br />
Those of us who &#8220;get it&#8221; realize that object based layout is superior to Photoshop&#8217;s half-baked layers concept. Strangely, even Illustrator and InDesign are object-based. Why does Adobe continue to push layers?<br />
<i>[If it were a simple question of one approach being better than the other, we'd have long ago adopted the better method.  The challenge is that an object-based approach is great for some things and lousy for others; same goes for Photoshop-style layers.<br />
</i><i>Sometimes (e.g. painting, retouching) you'll very much want layers that work in the way that Photoshop originally implemented them--large, clear sheets on which you can paint.  You almost certainly *don't* want PS to create a new layer/object every time you put down a paint stroke.  (That behavior is one of the downsides to After Effects-style vector painting, which is why we implemented video painting in PS; the approaches are complementary, not redundant.)<br />
</i><i>There are obviously times when an object-based approach works better, and Photoshop has made changes that help you work in that way (e.g. optional auto-selection of clicked layers; multiple layer selection; layer grouping; etc.).<br />
</i><i>One problem is that we have to set the defaults just one way, and some people never bother to try switching things on/off to find a way of working they might prefer.  That's one of the many reasons I keep emphasizing the desire to make Photoshop more easily &amp; radically customizable, so that with one click you could change many aspects of the app's environment and behaviors.  --J.]</i><br />
I think we&#8217;ll see Photoshop become more and more like FW. It&#8217;s now all about everything being editable all the time (a luxury that FW users have enjoyed for years and PS users are just beginning to discover)!<br />
I&#8217;ve been using FW for web design since beta 1 and I use it every day. I still use Photoshop for what Photoshop is good for, image editing and graphic creation. But, for web design/layout and quick slick web graphics, FW can&#8217;t be beat.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joey</title>
		<link>http://blogs.adobe.com/jnack/2006/02/photoshop_fireworks_where_to_from_here.html#comment-568</link>
		<dc:creator>joey</dc:creator>
		<pubDate>Fri, 14 Dec 2007 06:45:40 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2006/02/photoshop-fireworks-where-to-from-here.html#comment-568</guid>
		<description><![CDATA[I use both extensively. Photoshop is waaaay better at the bitmap level.
Fireworks is superior for web work. Period.
Both programs cross-over to some degree.
I Think its funny thay PS, in all its power has been getting closer and closer to (copying) Fireworks workflow for years now. (ex: Vector drawing tools, Folders in the layers pallette, easier object selection...to name a few).  PS devotees have no clue where all these new features  came from.  (copying Fireworks)
PS (Photo Shop) as the name indicates was orginally a non-web design tool. Fireworks was created for web design explicitly. For that reason..Fireworks is better for web work.  I stress WORK here...not playing around with images and abstract design.
I wont hire web designers who only use Photoshop or only use Fireworks. I need talent who are nimble with both. NEWSFLASH : You don’t have to use one or the other!!! Most Fireworks people know this…most Photoshop people seem to be brainwashed…and frankly ignorant to what FW can do.
Most print designers dont understand the concept of an &quot;object&quot; as it relates to software development...or library Symbols. I love Fireworks because it more closely resembles the OOP (Object Oriented Programming) model.
You can create a Menu, that is an object(symbol) that has other properties...like Buttons(Objects), that has properties(Text, Graphics, Gradients), that themselves have properties (Filters, etc...). And you can actually move things around and shared between files with little effort.
Photoshop has been faking web designer workflow for years…but showing and hiding and locking layers is hardley the way to group logical elements. Its silly really.
]]></description>
		<content:encoded><![CDATA[<p>I use both extensively. Photoshop is waaaay better at the bitmap level.<br />
Fireworks is superior for web work. Period.<br />
Both programs cross-over to some degree.<br />
I Think its funny thay PS, in all its power has been getting closer and closer to (copying) Fireworks workflow for years now. (ex: Vector drawing tools, Folders in the layers pallette, easier object selection&#8230;to name a few).  PS devotees have no clue where all these new features  came from.  (copying Fireworks)<br />
PS (Photo Shop) as the name indicates was orginally a non-web design tool. Fireworks was created for web design explicitly. For that reason..Fireworks is better for web work.  I stress WORK here&#8230;not playing around with images and abstract design.<br />
I wont hire web designers who only use Photoshop or only use Fireworks. I need talent who are nimble with both. NEWSFLASH : You don’t have to use one or the other!!! Most Fireworks people know this…most Photoshop people seem to be brainwashed…and frankly ignorant to what FW can do.<br />
Most print designers dont understand the concept of an &#8220;object&#8221; as it relates to software development&#8230;or library Symbols. I love Fireworks because it more closely resembles the OOP (Object Oriented Programming) model.<br />
You can create a Menu, that is an object(symbol) that has other properties&#8230;like Buttons(Objects), that has properties(Text, Graphics, Gradients), that themselves have properties (Filters, etc&#8230;). And you can actually move things around and shared between files with little effort.<br />
Photoshop has been faking web designer workflow for years…but showing and hiding and locking layers is hardley the way to group logical elements. Its silly really.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mart</title>
		<link>http://blogs.adobe.com/jnack/2006/02/photoshop_fireworks_where_to_from_here.html#comment-567</link>
		<dc:creator>Mart</dc:creator>
		<pubDate>Fri, 30 Nov 2007 08:20:31 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2006/02/photoshop-fireworks-where-to-from-here.html#comment-567</guid>
		<description><![CDATA[I don&#039;t like Fireworks at all. Since it is now part of CS package I tried to use it for website prototyping - both Illustrator and Photoshop lack in this area. But I found Fireworks very limited and clumsy to work with. I can work many times faster using both Illustrator and Photoshop even now than using Fireworks.
After reading the comments here, it seems obvious that there is need for program like Fireworks. But please, for those of us who already know how to use Illustrator, add few web oriented features to Illustrator too. Though learning may be little steep, Illustrator is much more powerful and easier to work with.
What I miss mostly in Illustrator is how text and graphic objetcs are aliased. There should be option for turning on/off aliasing for specific objects, layers etc.
Also stroke tool should mimic web browser css rendering in Web mode. And this is basically it! If these two things would be implemented I wouldn&#039;t even think about using another program for web work (apart from Photoshop of course).
]]></description>
		<content:encoded><![CDATA[<p>I don&#8217;t like Fireworks at all. Since it is now part of CS package I tried to use it for website prototyping &#8211; both Illustrator and Photoshop lack in this area. But I found Fireworks very limited and clumsy to work with. I can work many times faster using both Illustrator and Photoshop even now than using Fireworks.<br />
After reading the comments here, it seems obvious that there is need for program like Fireworks. But please, for those of us who already know how to use Illustrator, add few web oriented features to Illustrator too. Though learning may be little steep, Illustrator is much more powerful and easier to work with.<br />
What I miss mostly in Illustrator is how text and graphic objetcs are aliased. There should be option for turning on/off aliasing for specific objects, layers etc.<br />
Also stroke tool should mimic web browser css rendering in Web mode. And this is basically it! If these two things would be implemented I wouldn&#8217;t even think about using another program for web work (apart from Photoshop of course).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicolas Cohen</title>
		<link>http://blogs.adobe.com/jnack/2006/02/photoshop_fireworks_where_to_from_here.html#comment-566</link>
		<dc:creator>Nicolas Cohen</dc:creator>
		<pubDate>Thu, 25 Oct 2007 05:07:32 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2006/02/photoshop-fireworks-where-to-from-here.html#comment-566</guid>
		<description><![CDATA[Let Fireworks open photoshop and illustrator files, without braking layers or text boxes, or anything. Then we could receive artwork from print-based design studios (which typically produce design for a company before any web team is hired) without having to buy photoshop/illustrator/etc..
Photoshop&#039;s handling of undo/redo is great. The same with actions. I think we all came to understand it much better than fireworks automation system.
Add a &quot;tiled background&quot; tool to firworks, that allows to fill any solid shape with a tiled bg, thats editable doubliclicking (like a symbol), than when you slice it, it exports a gif or jpg that&#039;s usable as a tilable bg for any element in the website.
Memory handling in fireworks seems to freak out at the fourth hour of work with a 1000 x 1900 document that has 20 photos.
Selection in fireworks rocks, except for selection behind objects. Some hot key like right mouse button in photoshop, could be useful.
Let Symbols group into libraries. And let Libraries be independent from files.
So if i edit a button in the library, 30 fireworks files have the button updated. That would have saved us a ton of time last web app we designed.
If we could have some way to toggle layers on/off by clicking on some part of the design, fireworks could serve better when showcasing interaction design. Check out omnigraffle.
]]></description>
		<content:encoded><![CDATA[<p>Let Fireworks open photoshop and illustrator files, without braking layers or text boxes, or anything. Then we could receive artwork from print-based design studios (which typically produce design for a company before any web team is hired) without having to buy photoshop/illustrator/etc..<br />
Photoshop&#8217;s handling of undo/redo is great. The same with actions. I think we all came to understand it much better than fireworks automation system.<br />
Add a &#8220;tiled background&#8221; tool to firworks, that allows to fill any solid shape with a tiled bg, thats editable doubliclicking (like a symbol), than when you slice it, it exports a gif or jpg that&#8217;s usable as a tilable bg for any element in the website.<br />
Memory handling in fireworks seems to freak out at the fourth hour of work with a 1000 x 1900 document that has 20 photos.<br />
Selection in fireworks rocks, except for selection behind objects. Some hot key like right mouse button in photoshop, could be useful.<br />
Let Symbols group into libraries. And let Libraries be independent from files.<br />
So if i edit a button in the library, 30 fireworks files have the button updated. That would have saved us a ton of time last web app we designed.<br />
If we could have some way to toggle layers on/off by clicking on some part of the design, fireworks could serve better when showcasing interaction design. Check out omnigraffle.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: T</title>
		<link>http://blogs.adobe.com/jnack/2006/02/photoshop_fireworks_where_to_from_here.html#comment-565</link>
		<dc:creator>T</dc:creator>
		<pubDate>Tue, 04 Sep 2007 03:49:35 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.adobe.com/jnackdev/2006/02/photoshop-fireworks-where-to-from-here.html#comment-565</guid>
		<description><![CDATA[Hi, maybe you are intresting in fireworks extensions, I have one:
&lt;a href=&quot;http://textures.z7server.com/save_all_textures.php?type=2&quot; rel=&quot;nofollow&quot;&gt; Textures package for Fireworks &lt;/a&gt;
]]></description>
		<content:encoded><![CDATA[<p>Hi, maybe you are intresting in fireworks extensions, I have one:<br />
<a href="http://textures.z7server.com/save_all_textures.php?type=2" rel="nofollow"> Textures package for Fireworks </a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
