So, who's going to start the petition to make this open source?
The Future of Adobe Fireworks
21–30 of 81 posts
Re: The Future of Adobe Fireworks
#22I'm a bit confused that they kept Dreamweaver but killed off Fireworks. No web designer I know even uses Dreamweaver anymore, but plenty of people still use Fireworks. Odd decision by Adobe here.
I agree. I'm sure Dreamweaver has its set of dedicated, erm, beginner users, but the Edge family was essentially created to replace Dreamweaver.
Re: The Future of Adobe Fireworks
#23So, who's going to start the petition to make this open source?
Why would Adobe make Fireworks open source when they plan to continue selling and updating the last version?
"While we are not planning further feature development for Fireworks, we will continue to sell Fireworks CS6 as well as make it available as part of the Creative Cloud. We will provide security updates as necessary and may provide bug fixes. We plan to update Fireworks to support the next major releases of both Mac OS X and Windows."
Re: The Future of Adobe Fireworks
#24Does anyone know of an alternative that works as well with PNGs as Fireworks does? And runs under Windows.
Re: The Future of Adobe Fireworks
#25So, who's going to start the petition to make this open source?
Why would Adobe make Fireworks open source when they plan to continue selling and updating the last version? " While we are not planning further feature development for Fireworks, we will continue to sell Fireworks CS6 as well as make it available as part of the Creative Cloud. We will provide security updates as necessary and may provide bug fixes. We plan to update Fireworks to support the next major releases of bo…
No, I wasn't saying it would actually work ;)
Re: The Future of Adobe Fireworks
#26[deleted]
Re: The Future of Adobe Fireworks
#27I can't recommend Antetype enough as not so much a Fireworks replacement but rather a much better and different tool that makes screen design much more efficient and easy: http://antetype.com/
Re: The Future of Adobe Fireworks
#28"Error establishing a database connection"... Looks like hn can overload even adobe.com. Or at list there blog.
Re: The Future of Adobe Fireworks
#29Earlier quoted context omitted.
We just launched WebCode about a month ago (been selling http://www.paintcodeapp.com/ for more than a year). The two apps obviously share a lot of internals. We decided to make WebCode a separate app because it has an entirely different target audience.
Avid PaintCode user here, just learned about WebCode. Interestingly, more than once I wished I had the ability to export from PaintCode to something web with CSS or Canvas. Great to know there's now an app for that, but wouldn't it make sense to kinda also have it as additional functionality (maybe in-app purchase) for Paintcode?
Technically, this is entirely possible. We have developer builds which support both kinds of code generators in a single app. We're still considering this.
Re: The Future of Adobe Fireworks
#30My first copy of Fireworks I bought when it was still owned by Macromedia and it was wonderful; so powerful yet easy to use. It was my impression that Adobe never really "got" it, or knew how it should exist in their ecosystem as a sort-of competitor to their other products. It was sad watching it flounder, but I wonder what Adobe could've done differently.
Macromedia Fireworks MX 2004? Loved it, was my go-to image editor for a VERY long time.
I got started designing websites using FW MX 2004 before I graduated to writing CSS first. The ability to mockup designs and then use the slice export feature was great fun. I love Fireworks.