TwelvestoneDesign

import Fireworks into Illustrator and maintain editability?


Sign in

  • Waiting for Godot ( 730 k posts )
    Just conversation.
  • Thunder Dome ( 23 k posts )
    Photoshop Tennis and Collabs.
  • Photography ( 5.1 k posts )
    For all you shutterbugs, sh...
  • Flash ( 18 k posts )
    ActionScripting to tweens, ...
  • Front End ( 5.9 k posts )
    general front end design an...
  • Back End ( 9.7 k posts )
    serverside scripting, progr...
  • Projects and Theory ( 12 k posts )
    This forum is for discussio...
  • FAQ ( 269 posts )
    All those nagging questions...
  • Design ( 17 k posts )
    graphics & all aspects of g...
  • Purgatory ( 3.6 k posts )
    12stone Jail, feel free to ...
baron ruhstoff
 
2011-11-21

Can it be done? We have a FW file chock full of buttons with rounded corners and gradients that get reduced to static pngs.

Is editability even a word?

cfoley
 
2011-11-21

Hmmm I never have issues like that. Try opening the eps from fireworks, or using the file>import

CS5 or 4 will make all the difference I bet

Walt
 
2011-11-21

it is a word, yes... sorry I don't know about FW files off the top of my head

from what I've read, it sounds like Smart Objects and Placed Files... editable in their native app

http://rwillustrator.blogspot.com/2008/09/making-illustrator-and-fireworks-fit.html

arigato
 
2011-11-21

Agreed on smart objects & placed files. Fireworks never did play well with others.

Storm
 
2011-11-21

Even though FW has 'vector' tools, they don't draw vectors. But it can reinterpret what it sees on screen.....

From that article: Fireworks has a command in the Edit menu called Copy as Vectors.

I don't know what it does in Illustrator though.

Walt
 
2011-11-21

it appears that Fireworks CS5 has a Save As Illustrator8 option which seemed to be much better than exporting as PDF...

baron ruhstoff
 
2011-11-22

Ya, none of those will do what we need, sadly. "Save as" produces a bunch of janky jank and import/place still requires ultimately editing in FW. Thanks anyway, all!

Just for your personal edification, here's what we're working with: We're building an app in Air. Air was chosen to take advantage of local storage. The design team wants to have a lot of control throughout development, so the decision was made to use Adobe's Flash Catalyst. A craptastular decision, it turns out.

Adobe claims that Catalyst is meant to optimize the workflow from design to development and back again: design using your favorite tool (AI or FW) and easily import the source into Catalyst where you can convert the structured assets to existing AS classes. Catalyst generates the necessary MXML skin and BAM! you're good to go.

Or so they want you to believe.

It turns out that Catalyst isn't even half-baked. It's gooey raw dough.

Example for the designers: There are no text alignment options. Size and font, sure. But alignment? No.

Example for the developers: The code generated is one step above that of FrontPage. Make the smallest edit to the MXML - say, define scaleX for a component instance - and everything goes to shit.

On the plus side, it's forcing me to ramp up on Flex.

On the minus side, it's forcing me to ramp up on a language that I will likely never use again.

:(

/rant

Storm
 
2011-11-22

whooooo hoooooo!!!

nice rant!

Sorry, you must be a member to post to a conversation. Either log in or sign up to get involved.
TwelvestoneDesign

import Fireworks into Illustrator and maintain editability?