I think they would not publish a story showing that one of their products is completely unusable.
I think they would publish what mzetlitz just told here.
They published my story and more or less I was saying Adobe you suck... so ... hehe.. cross fingers
It is a good tip actually. I will do this, easter vacation is coming up and I will write a story or two.
While I find it hard to not be biased of late, my wish would be that Adobe does understand and meet the demand. They should rewrite the whole software, regardless. All this is no doubt due to code passed on from Macromedia.
Yes... and they should do this sooner the better...
Some years ago, Fw was not even considered by an overwhelming number of designers not wanting to get rid of their usual tools even if they were not suited to do what was needed unless you used workarounds, which btw is what one has to keep doing nowdays. Today, this number has dicreased thanks to the work some people outside Adobe is doing. (i.e Smashing Magazine)
I know, cause I do lots to get designers to use it, they absolutely love it when someone tells them how to do basic things as a starting point.
Most of the people get it in a few weeks, cause it's absolutely easy to use and cause people, once they see what FW can offer, want more. As it is normal. But we all would want to have it properly, not in the shape of an outdated piece of software maintained by people that absolutely love it, instead of Adobe itself.
Adobe is to blame for this mainly. Lazy designers no wanting changes of any kind are second... but far away from Adobe's bad work.
I know there are designers asking for things to be included in PS they do not even suspect they had for years in FW... and if a single designer tells me he prefers Photoshop cause he is used to it, I can just only think of laziness and bad practices for the sake of not leaving their comfort area.
Changes will arrive, sooner or later, despite Fireworks or whatever, and they will suffer double. No matter what your choice is, it is always a good idea to try new tools and see what's in there.
If people would have done this 15 years ago, we would not be now designing websites with a photo editing tool.
The most irritating thing is seeing how Adobe supports this idea... for the sake of money... I understand the money part... but there are much better ways than trying to sell us the idea that PS is the best and one and only tool.
I have an interesting find.
Typically I don't have a problem with Fireworks. But I figured I would leave this screenshot here showing what happens when you right click certain window panels and go to "settings".
Now, I'm not a software engineer or anything of the sort. I'm not sure if this even means Flash is integrated into Fireworks as part of the software. But I do know that Flash likes to make computers weak in the knees. I'm also pretty sure that both pieces of software probably need to be up to date in order to function properly.
I also want to leave this link here.
This forum is user to user but what I've been told the staff actually reads is this: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
I think everyone should be leaving a message. It costs nothing and it may help...being optimistic.
since lately Fireworks is worse than ever before.
I have just launched Fireworks and opened a file. The program does not even manage to render the work space properly. Instead I can reveal sections of the screen by moving my mouse cursor around.
I haven't performed even a single click yet, just a fresh application start and open document.
As you can see, my browser uses more memory than FW, which is dead at 350MB of memory usage.
How long do you insist to ignore this issue, Adobe?
I did. Never got any answer or feedback there. This thread is the most viewed thread here, so this issue should be top priority.
I believe your refresh issue is unrelated to the memory issues this thread is TRYING to address.
The issues raised on this thread are about "out of memory" errors, crashes with those same errors and inability to save files due to long use sessions creating "out of memory".
Whether the bug you have is a fireworks fault or not, I cannot say..... But it will likely get lost amongst the very different issues raised here. You should start another thread to try and see if anyone else has the same.....that way we have decent bug tallies on the forum..... If no one else replies with same, probably local issue.
I would suggest updating graphics drivers first to narrow it down. It does sound like a localized issue though. Pray it is, cause I wouldn't count on any bug fixes from Adobe!!!
Yes, fireworks uses Flash to display SOME of the panels and GUI elements. It isn't the cause of the issues however. I've built several plugins for fireworks and usin flash panels creates NO decernible memory increases or CPU usage. We aren't talking about a Interactive flash website with more vectors than common sense updating 1000 Tweens per frame.
Updating your flash has no effect on performance.... You can run Fireworks with NO flash installed.
This is a use to user forum. Please leave your bug report here:
>>> best joke ever!!! <<<
what should we report there, error they know since years?!?! cant be true!
aaaah, and i forgot, if you report or call them, u´ll get a "solved" mail back, doenst matter if the prob still exists.
they are just ignoring every prob in fireworks.
Adobe seems to be getting rid of Fireworks by letting it bleed to death. They never wanted Fireworks in the first place. They want us to just use Photoshop. Adobe bought Macromedia only for Flash and Dreamweaver. They handed Fireworks over to some small Indian development team with minimum funding and don't even bother to set any quality standards. It would be a bad decision to just bluntly pull the plug on Fireworks because the vast and loyal usergroup so they just bully us over tot Photoshop.
It's also not an option to sell Fireworks because it would be competition.
So eventually they did what I feared they would do after they bought Macromedia. They killed Fireworks but they're doing it slowly, sneaky and painfully.
I wish some smart, caring developer would make an alternative for Fireworks. Taking all it's top features (pages, symbols, shared libraries, vector editing, etc.) and build a modern tool specally for designing large, multi device webservices. These people would be my gods.
just count the number of people involved into this project by going to "About Fireworks" and compare with Photoshop...
There are some guys already doing it, and much better than Adobe, specially considering they are a very very small team:
Only mac though. However, I really hope they kick Adobe's as.s.. It is intolerable how clear it is they strive only for money and not for better tools. And still they blame the "all time Photoshop users not wiling to change tool" That is bullsht. No one I ever showed what Fireworks does, said "I'm not switching".
We need competence and they deserve some kicking in the as.s.
I will always recommned wherever I go not to use Photoshop for webdesing and avoiding Illustrator for anything not printable.
Ps: Oh, and by the way, Sketch is only 49,99$ (sometimes with special offers even less), great updates every month, and feature request that is actually taken into consideration in a short period of time.
Why the hell are we caring about this mega companies such as Adobe, bleeding us to misery and uncertainty?
Well every job has it's tool. Photoshop and Illustrator are both brilliant in their own field But it's really shortsighted and not of this time to think there's no need for specialised webdesign tools while they did put so much effort in a print layout tool like InDesign.
I tried Sketch really quick before but appaerently disliked it because I deleted it again. I'll give it another run. I dor really really really like Bohemiancoding's fontmanager 'Fontcase'. I've been using it from the first launch and I love it!
Today this happened:
I created a larger symbol (a recurring simple form) and the problem has started. I closed Fireworks, opened the document again, broke apart the symbol and the problem ceased to appear. So it's something with the symbols.
You could definitely be on to something.
I don't use symbols and I never have a problem with Fireworks.
How complex are your projects? Multi-state, multi-page with styles and all?
I typically have multiple pages with most of the styling complete by the time the mockup is finished. No states though, I do that kind of stuff when I design the sliding doors and/or sprites for my CSS.
I mostly lay out elements in Fireworks using grey boxes that are accurately scaled. I keep the elements labeled in their own folders with the bitmaps ungrouped (so I can cmd+click whenever I need to do something to multiple bitmaps), then I just collapse everything and grab what I need for the duration of the mockup process.
I have recently downloaded the subscription version of FwCS6 and have been having a TON of annoying issues like cursor nudge not working, select object impossible, randomly, selecting vector points.. nope.. using shift to select number of object.. nope all these are random and arbitrary and unrelated to system resources being used (according to CPU+RAM monitors. Gah!!!
Unfortunately Adobe decided to give up on their only interaction design product. I don't think we will ever receive an update to any of the horrible bugs plaguing this software.