Photoshop has no real corollary to Fireworks pages, so unfortunately
you're stuck, as far as I know. Out of curiosity, after doing all this
work in Fireworks WHY are you having to export to Photoshop? And why
would you want everything from a multi-page document dumped in to a
single file? I would think it would be an organizational nightmare to
Thanks for the response Jim.
The answer to your curiosity is simple. I wouldn't be exporting to PSD if I didn't have to ... but the developer building the site from my design file doesn't use Fireworks, only Photoshop.
Boggles the mind ... I know.
1 person found this helpful
Boggles the mind indeed . . . Best of luck Paul.
Community MX Partner -
Adobe Community Expert
Author - Lynda.com
Author: Peachpit Press
I ran into the same situation recently and wrote an extension that will take a multi-page document and export each page to it's own PSD file. I just submitted it to the Exchange last night, so it may take a few days to get up there. I've attached it here—hopefully it's helpful!
I ran into a similar situation recently and wrote an extension that will take a multi-page document and export each page to it's own PSD file. I just posted it to the Exchange last night, so it may take a few days to get up there. Look for it soon—hopefully it's helpful!
This sounds very promising:] Thanks Doug!
Can you try reattaching the extension? Your post doesn't include any links.
Great idea, thanks Doug... shame it's CS4 and above only, I have this exact problem but only have CS3.
Here's a link to the extension in case anybody needs it:
Thanks, Paul.You know, I didn't test in prior versions of FW, so it may well
work in CS3.
The exportPSD() command of the API has been available since FW 4, and I'm
not really relying on anything new in the CS4 API (as far as I know).
Have you tested in CS3?
If it works, let me know so I can update the description of the extension.
Glad it's (at least potentially) helpful!
It doesn't work I'm afraid - I tried.
Is it possible to re-export the extension (or however you do it) with different settings to allow < CS4 users to install it? To use an analogy, you can export a really simple Flash movie as requiring Flash 10 to play, even though there's technically nothing in there to stop an earlier version from playing it other than the export settings.
I actually think that might be the case.Since I created the SWF panel in
Flash CS4, it was published by default to Flash Player 10.
I need to find out if FW uses whatever the latest FP on your machine is or
if there's one bundled with the app.
If that's the case, I bet CS3 can only work with SWF panels from FP9.
Let me do some investigating and we'll see what happens...
Fantastic Doug, works a charm.
One thing I would suggest is a note just below the buttons that the psd's will be saved in a subfolder in the same location as the original png (or something similar).
Good call, Heath. Thanks.I'll add that in when I republish down to Flash
Player 9 (to see if everything works in CS3).
If I were to send you an updated version of this, published down to FP9, do
you think you could test it out in CS3?
Sure. Send to paul at clearleft dot com
hey Doug... did you ever manage to make this cs3 compatible?
Sorry, but I didn't have the time to continue looking into CS3 support.
This may be a hacky workaround, but one thing you could try in the meantime is to export pages to files as Fireworks PNGs.
Then open those individually outputted files and do a simple "Save As..." as a PSD.
I know that's not the best answer, but it may get you what you need until you're able to upgrade.
Let me know if that works out.