Comments on: A bright future for Fireworks

By: dwayne

dwayne — Fri, 14 May 2010 01:09:59 +0000

I was just looking at a post about Fireworks and why it is still relevant. User said that for.png images you have alot more options for transparency. In Photoshop not so much.

By: Russ

Russ — Wed, 16 Apr 2008 05:59:27 +0000

When I go to Adobe’s home page I don’t even see it under their list of products. I have a hunch they are trying to figure out what to do with Fireworks, I like the product and hope it finds itself at least blended into some other product.

By: Cole

Cole — Sun, 13 Jan 2008 10:35:23 +0000

A year since this blog entry: look at Adobe’s website and product list now.
Do you see FIreworks promoted as a top tier product?
Adobe is burying Fireworks as well as making it an orphaned product by ONLY including it in the CS3 Web package and leaving it out of the Design Premium package.
Fireworks is not in the home page product list or even the initial Product page list. Looks buried to me.
[I just know that Adobe has plowed more resources and features into Fireworks than Macromedia had done in *years*. And I don't see signs of that slowing down. --J.]

By: Stephen R

Stephen R — Wed, 31 Jan 2007 21:20:55 +0000

Im very glad Fireworks is being improved, but I do not agree with the previous comment.
For creating web graphics/interface elements, Fireworks is great. It’s combination of vector/raster elements far outshines Photoshop’s “raster with a bit of vector kinda tacked on” approach. I dont expect ANY graphics tool to produce optimal (X)HTML/CSS, if it did, we (web designers) wouldn’t have a job.

By: Arthur Wait

Arthur Wait — Wed, 31 Jan 2007 16:21:54 +0000

Phew. I’m quite relieved. I’ve long used Photoshop and Illustrator for print work, but Fireworks is simply a much better tool for developing web graphics.
I can’t wait to see how the new FW pans out–from the Edge article, it sounds like Adobe is really taking it in the right direction.

By: Steve Constable

Steve Constable — Wed, 24 Jan 2007 10:20:24 +0000

Here’s the deal. CSS2 needs to be implemented into fireworks or else developers/designers like myself will simply have to code by hand and break images up in photoshop like days of old before fireworks. In the old days. The times they are changing.
I am asked to develop standards based CSS sites and that can’t be done in fireworks. Something has to give or else this software product will be used less and less.

By: Stephen Voisey

Stephen Voisey — Mon, 11 Dec 2006 21:46:11 +0000

I remember Alan Musselman from the beta for Fireworks 4 and MX I was on, and he’s a good chap, so good to see him at Adobe.
I’m pleased Fireworks has a future, as it is a very good application for building web designs, and this seems to be the way they are taking it. Perfect.
But my real hope for the next version is a fix to the frustrating rendering bugs that exist in the current version, then all will be well.