[thelist] quick ssi question

martin.p.burns at uk.pwcglobal.com martin.p.burns at uk.pwcglobal.com
Wed Dec 12 10:38:24 CST 2001


Memo from Martin P Burns of PricewaterhouseCoopers

-------------------- Start of message text --------------------



To:   thelist at lists.evolt.org
Subject:  [thelist] quick ssi question

>When using an include in an html document typically wouldn't you keep all
of
>the document structure out of the include?

><myinclude.inc>
><p>stuff and things, stuff and things</p>
></myinclude.inc>

>and then the parent html doc would control the presentation and
formatting?
>Is this correct?

You could do it that way - you can do one or both of:
1) Include the content into a template (nav etc)
2) Include the nav around the content

You can do both of course - have the 'page' as a simple container for
sub-objects, each of which is included in. This is typically how a Content
Management System works: a hierarchy of containers.

>what if I want to include and entire html doc that has embedded js in it,
>like a nav system?

Here's how you could do it (pseudo-code with SSIs expanded):

<header1.inc>
<html>
<head>
</header2.inc>

<page_specific_header.inc>
<title>my foo foo.</title>
<meta keywords="foo,bar">
</page_specific_header.inc>

<generic_header.inc>
<SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript">
<!--
stuff and things
//-->
</SCRIPT>
</head>
<body>
<generic_header.inc>

<generic_layout1.inc>
stuff - outer tables start or container divs
</generic_layout1.inc>

<nav_system.inc>
<!--
######
# probably with some kind of logic to produce page specific versions
# saying 'you are here'
######
-->
nav system with mouseovers
</nav_system.inc>

<generic_layout2.inc>
stuff - inner tables start or container divs
</generic_layout2.inc>

<content.inc>
Your page's content
</content.inc>

<generic_layout_close.inc>
stuff - close all tables or container divs
</generic_layout_close.inc>


>isn't this just a call for frames?
Well you can replicate much of the advantages of frames using SSI,
and avoid pretty much all of the disadvantages. SSI is the way I'd
go.

>does anyone have an idea what the best way to approach such a thing is?
>Having the nav as an external separate document would be best methinks
which
>is why I though about includes.

Yep, sensible.

Cheers
Martin

>new riders also published jeffrey veen, both books I also
>recommend.
...who forgot (by his own admission) to put the evolt browser archive
in. There's a hand-annotated copy floating around in Buffalo with the
missing reference added by Veen.



--------------------- End of message text --------------------

This e-mail is sent by the above named in their
individual, non-business capacity and is not on
behalf of PricewaterhouseCoopers.

PricewaterhouseCoopers may monitor outgoing and incoming
e-mails and other telecommunications on its e-mail and
telecommunications systems.
----------------------------------------------------------------
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material.  Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited.   If you received
this in error, please contact the sender and delete the material from any
computer.





More information about the thelist mailing list