Image Hotspots

Hi folks,

I'm building a map that is divided into sections and I want visitors to my site to be able to access their local info by clicking the appropriate location on the map. I want the map on each page of the site to aid navigation. The image is currently in JPEG form and I've setup hotspot locations using FrontPage 2003 on the homepage. My question is whether I'd need create the hotspots on every page that I put the image on? Is there any way to save the hotspot locations so I can just import the image to each page without having to re-setup the hotspots?

Cheers,
Marc.

I'm no FrontPage expert, but what I would try would be this .....

Open a new page, setup the map and hotspots, then save the page as "dummy" or some other name. Or if you already have it set up on your Homepage, re-save the Homepage under the "dummy" name.

Then every time you want to create a new page with the map on, open up the "dummy" page - add what ever text you want on this page, then "save as" it under the page name you want to create.

Just a thought ..................

Or ..............

Does FrontPage 2003 still allow shared borders ? In which case consider putting the map in the border.

Edited by deleted (Mon 18-May-09 13:12:17)

Hi eebdsirhc,

thanks for the suggestion. My website is currently about 40 pages, so I'd need to do a lot of copy-and-pasting information from the current pages to the "dummy" template. Also, if I wanted to amend the image (to add or remove new hotspots) later on I'd need to re-do it for all the pages again.

>>Does FrontPage 2003 still allow shared borders ? In which case consider putting the map in the border.

Funny you should mention that, but I was looking at Shared Borders at the weekend. According to several tutorials I found online, FrontPage 2003 should support them, but no matter what I try, the option is greyed out in the menu. I also read a couple of posts suggesting that it generates a lot of questionable and sometimes buggy code. I had previously setup the site to use a frame set (and had the menu in a separate frame), but I had a number of problems with search engines bringing up just the main content page (and thus missing the link bar) and I found I had to add a link on every page to take the visitor back to the main frame set.

Cheers,
Marc.

Marc - Shared borders sounds like the solution.

I know FP2003 supports them, because of backward compatibilty, but was unsure if you could create them in FP2003 (because of all the problems they caused in earlier versions).

But I've just looked in my FrontPage 2003 Inside/Out manual, they are fully supported and there is a "tip" ..

If the shared border command is dimmed, choose Page Options from the Tools menu, and then click the Authoring tab. Then select the Shared Borders check box and click ok.

I don't have a copy of FP2003, so I can't check to see if this works or not.

I used to maintain a web site www.applebymagna.org.uk which was originally built in FP2000 and was very buggy on the shared borders, then later maintained in FP2003. I don't remember having any specific shared border problems with FP2003.

Good Luck.

Edited by deleted (Mon 18-May-09 17:17:05)

Hi eebdsirhc,

thanks for your help with this.

>>Shared borders sounds like the solution. If the shared border command is dimmed, choose Page Options from the Tools menu, and then click the Authoring tab. Then select the Shared Borders check box and click ok.

Thanks for the suggestion, but I've tried that (on two different installations) and neither enable the Shared Borders option on the Format menu. I'm wondering whether the page has to be of a certain format in order to use them (i.e. PHP, ASP etc) rather than a basic HTML format?

I've been playing around with inline frames this evening and think I may have hit upon a solution that works. I can add an inline frame to each page and link it directly to a page with only the menu buttons on; I should then only have to update the one page in order for it to show on all pages. Moreover, I'm hoping inline frames are more search engine friendly (?) as the frame is within the standard HTML page, rather than being part of a frame set. Although I guess it's still possible for someone to call up only the menu page, I think I can minimise the chances by leaving out the metatags in the head code.

Don't get me wrong, I like the sound of shared borders, but I'm wondering whether a single inline frame may also be a contender give that my copy of FP doesn't seem to want to let me play with SBs?

Cheers,
Marc.

Marc -

Pretty much exhausted my knowledge on this.

I have manipulated standard HTML pages with shared borders in FP2003. But all the pages had originally been created in FP2000. So strictly speaking I have never created a new web with shared borders in FP2003. But it must be possible -- somehow.

But if you have found a way round the problem ....................

Chris

Marc,

I have used FP 2003 to design a website and the shared border option was always available from the toolbar. As an alternative have you considered using a dynamic web template so that the map will automatically be shown on every linked page? Just a thought....

John

Hi eebdsirhc,

>>Pretty much exhausted my knowledge on this.

I appreciate your time and patience with this. I'm going to see how I get on with an inline frame and have a crack with the Dynamic Template that John suggested.

Cheers,
Marc.

Hi John,

thanks for your help. It's odd that the Shared Borders option is greyed out. I might try re-installing FP2003 in case something went a bit awry. I'll also take a look at the Dynamic Templates.

Cheers,
Marc.