On Tue, 4 Jul 1995, Randy Terbush wrote:
> I #include a bottom menu image that has a couple of relative URLs
> to provide a path to the directory above, and to access the search
> tool in that directory. It could be a real mess to symlink or copy
> the map file to every directory.
Yeah, okay, I see. When we have client-side imagemaps a la HTML 3, then
this won't be an issue, since the #include can happen to one common file
somewhere but the links in the <FIG> can all be relative to the current
document.
One final suggestion, and this isn't 100% relative but is close: let's
say the top-level subdirs are texas, california, and oregon, and the
common subdirs are cities, culture, and taxes. You'd create an imagemap
at the root level called state-attrs.map, say, which looks like this
rect cities [list of points]
rect culture [list of points]
rect taxes [list of points]
And on texas/index.html, you have the link made like this:
<a href="/state-attrs.map/texas/"><img src="/stateattrs.gif" ismap></a>
on california/index.html you have
<a href="/state-attrs.map/california/"><img src="/stateattrs.gif" ismap></a>
In other words, use the PATH_INFO variable to express context.
Now, obviously you want to be able to do one common <!--#include> for
every state's index.html, because you don't want to have to change every
file every time you change how imagemaps work. Well, why not have the
lines I suggested above created by a <!--#exec>? The script being
inlined could determine which page is calling it and select the state
appropriately.
Some suggestions....
Brian
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
brian@organic.com brian@hyperreal.com http://www.[hyperreal,organic].com/
|