I've built a navigation bar in FW CS3 with some nice looking buttons and pop-up
menus.
It previews perfectly in FW.
I then exported the .png file (indexgreg.png) as an .html
(indexgregexport.html) to Dreamweaver CS3 where I placed it in a new document.
It previews perfectly in DW.
BUT, when I upload the indexgregexport.html file to my web site, the pop-up
menus hold their links, but the main buttons lose their links and point to
numbered versions of the .html. (indexgregexport_1.html,
indexgregexport_2.html, etc.)
I must not be uploading all of the necessary files, but I can't figure out
what they are.
Here is the page to look at:
http://www.ferraripartsexchange.com/...regexport.html

This is really driving me crazy, not to mention wasting lots of my time!
And why is the title of the page indexgregexport.gif???
PLEASE, PLEASE !!!

Thanks-
Greg in New Orleans

BTW, I did upload the .css file, a folder with the button .gifs, and mm_css_menu.js
What am I missing?

Thx again-
Greg

I find it irritating that Adobe basically only SELLS extended support for its
products (a minimum of $175!). What happened to the one year free support
customers used to get after purchase?
I've already spent the money for the program, a copy of the user's manual (not
included with the software except under ), and many hours of my time
researching and trying to get this stuff to work.
I've been using Photoshop since version 2.0 and, I think, know my way around
the Adobe interface pretty well, but FWCS3 is completely UN-intuitive for me.
Also interesting is how FW experts (both in this forum and projectseven's)
tell me to find another program to build navigation bars.
How can Adobe advertise that its products are seamlessly integrated?

OK, that's it for my ranting today.
Report me, if you must.
Greg in New Orleans

geeceeart wrote:
> I find it irritating that Adobe basically only SELLS extended support for its
> products (a minimum of $175!). What happened to the one year free support
> customers used to get after purchase?
> I've already spent the money for the program, a copy of the user's manual (not
> included with the software except under ), and many hours of my time
> researching and trying to get this stuff to work.
> I've been using Photoshop since version 2.0 and, I think, know my way around
> the Adobe interface pretty well, but FWCS3 is completely UN-intuitive for me.
> Also interesting is how FW experts (both in this forum and projectseven's)
> tell me to find another program to build navigation bars.
> How can Adobe advertise that its products are seamlessly integrated?
>
> OK, that's it for my ranting today.
> Report me, if you must.
> Greg in New Orleans
>

The menus are easy to build but a pain to maintain, hence the other
recommendations. As far as I know, DW's suppport for the CSS version of
the menu's is not stellar, if present at all. IMO it is a feature that
should never have been incorporated in FW at all, but it did.

There is a good deal of integration - much better than in the past, but
there are always things to improve on.

A link to your original png file might be ful as well.

--
Jim Babbage - .:Community MX:. & .:Adobe Community Expert:.
http://www.communityMX.com/
CommunityMX - Free Resources:
http://www.communitymx.com/free.cfm
---
.:Adobe Community Expert for Fireworks:.
Adobe Community Expert
http://tinyurl.com/2a7dyp
---
See my work on Flickr
http://www.flickr.com/photos/jim_babbage/

OK, thanks Adobe Press for giving me the simple solution.
(paraphrasing the tutorial) "Don't bother to assign URL's in FireWorks. You'll
do that in Dreamweaver."
When the nav bar buttons are exported from FW, they lose their URL links (but,
oddly, the pop-up menus don't!). So, after placing the FW html into
Dreamweaver, highlight each button and assign the URL link in the DW Properties
panel.
It works!
So, why does FW have the URL link box in the Properties panel?
Maybe it works for other types of elements?
Whatever.
Sorry for the ranting earlier, but I didn't see this solution in the FW
printed manual, menu, or anywhere else.
Thanks Adobe Press!
g

geeceeart wrote:
> OK, thanks Adobe Press for giving me the simple solution.
> (paraphrasing the tutorial) "Don't bother to assign URL's in FireWorks. You'll
> do that in Dreamweaver."
> When the nav bar buttons are exported from FW, they lose their URL links (but,
> oddly, the pop-up menus don't!). So, after placing the FW html into
> Dreamweaver, highlight each button and assign the URL link in the DW Properties
> panel.
> It works!
> So, why does FW have the URL link box in the Properties panel?
> Maybe it works for other types of elements?
> Whatever.
> Sorry for the ranting earlier, but I didn't see this solution in the FW
> printed manual, menu, or anywhere else.
> Thanks Adobe Press!
> g
>
>

If you are creating click through mock ups, the urls can be quite
ful within FW. I can apply urls to hotspots or slices and they are
maintained on export if I choose to export html, which I will do for
mock ups. On production sites, I just deal with it in DW.

--
Jim Babbage - .:Community MX:. & .:Adobe Community Expert:.
http://www.communityMX.com/
CommunityMX - Free Resources:
http://www.communitymx.com/free.cfm
---
.:Adobe Community Expert for Fireworks:.
Adobe Community Expert
http://tinyurl.com/2a7dyp
---
See my work on Flickr
http://www.flickr.com/photos/jim_babbage/

[q]Originally posted by: geeceeart... I've been using
Photoshop since version 2.0 and, I think, know my way around the Adobe
interface pretty well, but FWCS3 is completely UN-intuitive for me.
Also interesting is how FW experts (both in this forum and projectseven's)
tell me to find another program to build navigation bars.
...Greg in New Orleans[/q]

Greg, I couldn't agree with you more. I've been with Photoshop since v.4 and
find these former Macromedia applications very unintuitive and clunky. The
files are not indexed well and are vague in their descriptions. I read
this forum string because CS3 Fireworks is not properly exporting URL
information.