Honestly, the problem is NOT with the application (although both FW and PS
could be MUCH better with their slicing).
The issue is that most designers (who don't also know HTML) don't know the
best way to slice things. They'll just draw sliecs where they want main
images and let the app interpret
I've got a friend who builds web site templates in Fireworks for use
with a CMS that I built. Every time he builds a new template, I have to
fix the HTML to make the template so hat it is height flexible. As
is, the navigation gets all crazy and stuff.
The templates he generates are heavily
It's not particularly easy to fix them so I'm kinda wondering if any of
you fireworks users out there know how to get fireworks to generate HTML
that isn't quite so bass-ackwards.
I'm not a fireworks user so I can't really help him much.
He's using Fireworks MX 2004.
Fireworks can be
As far as the filenames, they are based off of a slice name. You can
rename the slices within FW and they will export with the desired name
after that.
M!ke
The templates he generates are heavily table oriented with those
obnoxious filenames (template_r2_c1.gif, etc).
]
615.370.1530 x737
--//-
-Original Message-
From: Rick Root [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 28, 2006 1:11 PM
To: CF-Talk
Subject: OT: Fireworks template flexibility
I've got a friend who builds web site templates in Fireworks for use
with a CMS that I built
Casey,
Am i reading you right : you are exporting the same png each time you want a
new element/layer? You can export each layer seperately. That should save
you some time..
But i could have miss read... its only been 1/4 cup of coffe since i woke up
:)
On 3/29/06, Casey Dougall [EMAIL
I do what I can to condense the process, get as many elements out of my
Slices as i can but that I mentioned before is what i'm using and it's
effective, but time entensive. I haven't been able to export layers without
adding whitespace around the layer in photoshop, haven't tried it in
fireworks
7 matches
Mail list logo
