![]() The wish list IS read by Adobe (unlike this user-to-user forum) and is almost like a form of triage. You can help by reporting issues WITH details to the Adobe wishlist. They can't get to all of them in one go, unfortunately. They genuinely want to produce a solid product and do their best to address issues - legacy and new - in each release. The dev team for Fireworks is a dedicated - but small - team. For example, I know one user who has three identical Windows systems, yet only one of those systems is plagued with problems when using Fireworks. It can be hard to track down issues, too. I'm on a MacBook Pro, using Snow Leopard - have not upgraded to Lion yet. I am in the habit (not because of Fireworks) of saving files often, so I might be avoiding some of the issues mentioned here. Once in a while, FW tells me it can't save a file because it's in use elsewhere (and it's not in use elsewhere). I get the "occasional" hang, but Word crashes on me more often than FW. I honestly do not run into the glut of problems people seem to experience. You are creative professionals and shouldn't have to deal with wonky software getting in the way of your creativity, your workflow. I suggest that all of you, who are able, should start investigating your own alternatives to Fireworks. The developers of said programs are also very active in communicating with their users. The speed and responsiveness of these two programs alone is unbelievable at first when you come from a Fireworks background. For the most part though, I am using Sketch 2.0 for a good 80% of the work I typically do in Fireworks. I do not think that either is quite ready to replace Fireworks on my system yet, but they are almost there. Bohemian Software's Sketch 2.0 and Pixelmator 2.01 are going places. (At least Photoshop is 64-bit though.)Īlthough I won't be able to replace Photoshop and InDesign anytime in the near future, I am having spectacular results with some Fireworks alternatives. We're pretty much at the point where the Fireworks needs a rewrite anyway as it has become a bloated mess of half-complete marketing features, sort of like Photoshop. It has clear to me that Adobe is not going to allocate the resources necessary to clean up Fireworks. ![]() ![]() But for some reason I have continued using Fireworks despite its numerous flaws and neglect by Adobe. I love(d) Fireworks until Adobe started butchering and neglecting it. PlayOnLinux will finish the install, even though it crashed.I've been using Fireworks since Macromedia's first beta. POL_SetupWindow_message "$(eval_gettext 'NOTICE: If you get an error saying that the installation failed, wait at least 5 minutes before closing it. # Distribution used to test : Arch Linux 64-bit PlayOnLinux will finish the install, even though it crashed.')" "$TITLE" +POL_SetupWindow_message "$(eval_gettext 'NOTICE: If you get an error saying that the installation failed, wait at least 5 minutes before closing it. +POL_SetupWindow_browse "$(eval_gettext 'Please select $TITLE install file.')" "$TITLE" +POL_SetupWindow_presentation "$TITLE" "$EDITOR" "$GAME_URL" "$AUTHOR" "$PREFIX" +# Distribution used to test : Arch Linux 64-bit POL_Shortcut "Fireworks.exe" "$TITLE" "" "" "Graphics " POL_SetupWindow_browse "$(eval_gettext 'Please select $TITLE install file.')" "$TITLE" ![]() POL_SetupWindow_presentation "$TITLE" "$EDITOR" "$GAME_URL" "$AUTHOR" "$PREFIX" # Distribution used to test : Duzeru GNU/Linux 2.0 64 bit(Debian Jessie based)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |