|
|
Posted by Spartanicus on 12/31/05 11:21
Len Philpot <len@philpot.org> wrote:
>> For the third time: preprocessor, S&R, building static files locally
>> using a database, only the last option is potentially more complicated
>> to use than using frames.
>
>And for the xth time, I don't have a database, preprocessor, SSI,
>scripting nor anything else available to me *at my ISP* (regardless of
>whatever I might install here locally).
All three mentioned solutions do not require any ISP support, they
work/run locally as per the constraint you previously stated.
>> Btw, it's bad form to link to the active (target) page itself, so a
>> navbar should change from page to page by omitting the link to the
>> (target) page itself.
>
>Ideally, yes, but not a major infraction. Once again, this would matter
>more if the nav panel changed from page to page. If it's static, then
>technically /none/ of the links should be there, since they'll all be
>redundant at some point in the experience. That would completely nullify
>the usabilty for the nav panel at all...
A Navbar should be coded for user convenience only, they should be
redundant in the sense that a site should be fully navigatable without
it. That however does not mean that it doesn't serve a function.
--
Spartanicus
Navigation:
[Reply to this message]
|