On Sat, 9 Aug 2003 01:58:02 +1000, "Robert Mark Bram"
<relaxedrob@remove.this.optusnet.com.au> wrote:
[color=blue][color=green]
>> Any script which hides key navigation content in javascript (which is
>> not always enabled obviously) is generally a bad idea, a more sensible
>> approach is to transform an unordered list or something similar that[/color]
>
>An unordered list kept where?[/color]
Within the document, the problem with author once, see in multiple
URI's is a seperate one, you shouldn't combine them, since javascript
for content is simply too unreliable, so while javascript includes
might've been a solution the %age of clients where it won't work
(including key clients like google of course) makes it inefficient.
There's 2 obviousapproaches, the SSI/server generated one, where you
have each page served by a script on the website, including the
content, SSI is the simplest method of this and it's supported very
widely.
Certain webhosts don't support it, and I'd say go find another if
that's the case, however you might not always be able to do this, or
the site might be such high volume that you don't want the processor
hit (if this is genuinely the case you can probably get funding for
better hardware from somewhere - after all someone's happy to pay for
the bandwidth)
In that case though you can pre-process the documents to static HTML,
probably best to still use SSI for development (since you can run a
suitable webserver on your development box) then you can run a tool
when you publish which combines everything - the main cost is that you
need to upload everything after doing this (or generate on the server,
but that's unlikely if you've not got SSI on the server) So upload
costs are higher.
[color=blue]
> precisely the maintenance task I want to avoid with a
>script like this.[/color]
There are better solutions without the problem, a ciwa.site-design or
ciwa.cgi will probably be the place to ask if you need more help after
googling.
[color=blue]
>Well, if JavsScript is disabled the whole script is broken... visitors must
>have JavaScript turned on to access the example: to be honest I do not think
>this is an unrealistic expectation.[/color]
In the real world, I'm afraid it's very unrealistic to expect
javascript, Google especially would have trouble, running javascript
in a robot is tough, you have to make sure the javascript can't do
anything nasty to your poor little robot.
Jim.
--
comp.lang.javascript FAQ -
http://jibbering.com/faq/ 
