Ok, so, here's one solution:
If Adobe finally decides to use the Fireworks ".PNG" engine, they shouldn't have to introduce .FXG into the Fireworks product line, since the onus is on Flash Catalyst to port Fireworks, not the other way around.
Using the Fireworks engine, features such as "Pages", or perhaps even Fireworks's "States", would allow for more seamless “.PNG” porting into Catalyst. Also, doing so, would eliminate all those steps one has to take to merely generate states within Catalyst—saving UI designers time by giving them the option to simply make adjustments to the Catalyst timeline. Not only is this faster, but it makes more logical sense!
I am beginning to think Adobe’s in over their heads with this one.
I have to agree. Until Fireworks is fully supported and is the primary step in this process, this thing is parked. Designing UI's, apps etc. in PS and AI is simply awful.
Dude.. dont be a ******....
This isnt the senate floor. No need for the hostility. They couldve left us with the tools weve always had.
O, Photoshop lover undercover I see...
Well, agreed, but they also could lose business to competitor (fill in the blank), which actually provides the right solution. Don't be fooled; Adobe's agenda isn't merely in providing you with the correct amount of tools, it's to make money by coming up with various new platforms to spin.
It's one thing to develop a product, it's another to build a product that doesn't migrate...well, how should I say this--with your own product line?