The highlighted portion is the
"ONLOAD" script, which you will also
need to paste into your new document.
3. Finally,
the easy part is copying and pasting the remaining script, table
and images. Go back to layout view in both of your documents.
In the "test1.html" document, you should see your images
with a yellow shield on top and bottom. Select everything, including
the shields, and copy it all. Then paste it wherever you want
in your destination document.
NOTE:
Preview the "test1.html" document in your browser before
you complete this last step. If the rollover shows broken images,
you're going to have to do a simple manual tweak, detailed below.
4. Further
problems?
Now, if you go ahead and preview your page, you might see that
in all states besides Normal, you're getting broken images. This
is because Dreamweaver's file management system sometimes doesn't
recognize relative image links inside JavaScripts created by ImageReady.
This is easy enough to fix.
In your Code
view, you will see something like this: ONMOUSEOVER="changeImages('test1_03',
'rollover1slices/test1_03-over.gif' . The part that's relative
is the 'rollover1slices/test1_03-over.gif' . So all you have to
do is perform a find/replace for 'rollover1slices/ . In my case,
my directory structure requires me to go up two levels in the
directory, then into the images/ directory before I can get to
the rollover1slices/ directory. So, in my find/replace dialog,
I look for 'rollover1slices/ and replace it with '../../images/rollover1slices/
. (The little "../" tells the browser to go up one directory.
If you need to go up more than one directory, you can just add
in additional ones, such as "../../" for two directories,
"../../../" for three directories, etc.)
Dreamweaver's Find/Replace
You need to
do this again because some of the code will use single quotes,
while other parts will use double quotes. So, open up the find/replace
dialog again, and change the single quotes to double quotes, leaving
everything else the same. Then click Replace All.
Final thoughts
So why all the trouble? If you use Dreamweaver, why not just use
Fireworks? And if you use ImageReady, why not just use GoLive?
Well, that's not the way it always works out. Some people swear
by Fireworks and Dreamweaver. Others swear by GoLive and ImageReady.
But there's an awful large part of the population that likes ImageReady
and Dreamweaver. After all, if you prefer to do you animation
in ImageReady and your HTML in Dreamweaver, a little five-minute
conversion time isn't too much of a hassle.
Both Adobe
and Macromedia should work to make this a little bit easier on
the users. The burden will likely fall on Macromedia for two reasons.
First, Dreamweaver is highly extensible, so writing an importer
for ImageReady files shouldn't be too difficult. Second, practically
every designer in the world has ImageReady by virtue of the fact
that it's distributed free with Photoshop.
Neither company
should consider this an issue of caving in to the other. It's
simply a matter of making life easier on the user. And, at this
stage, the company that offers more import formats is likely to
come out ahead.
page
1,
2, 3, complete,
Home
