|
|
Posted by Spartanicus on 12/31/05 01:44
Len Philpot <len@philpot.org> wrote:
>> >How? (see ** below, though for the conditions)
>>
>> > ** That is, without scripting, SSI, etc.
>>
>> Again: preprocessor, S&R, building static files locally using a
>> database.
>
>Maybe I can approach it from the other end to clarify my constraints:
>How to do it with _only_ (X)HTML and CSS. How's that?
You say that you cannot figure out how to replicate the function of
frames and when you are told you reject it with an argument that amounts
to "but that's not how frames work". Frames are a fundamentally broken
concept, hence proper solutions should at best aim only to replace some
of the functionality of frames, *not* replicate the failures of the
frames concept.
>> >Single source Yes No **
>>
>> Frames using multiple source files.
>
>Let's see - I can have the same nav code repeated x times for x pages
>and have to manually update it each change, or I can (functionally)
>"import" it once for the nav frame and that's it.
The framed nav code is in a separate file: multiple source files.
>Seems simpler to me, aside from any other issues.
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.
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.
--
Spartanicus
Navigation:
[Reply to this message]
|