How to 'client-side include for secondary menu on page'

Question

Hi there.
The following page refers:
test page for early
draft
The linked page is in fact a DW CS3 tmp preview file, for
that reason the CSS has been pulled into the html file by DW, it
won't look that way in the eventual page file.
After lengthy battles with the Spry Horizontal menu, I
eventually resorted to Pop Menu Magic 2 (PPM2) to generate menus.
I'm very happy with the product (I'm not looking for PPM2 support,
but rather support pertaining to CSS-driven menu's in general
relating to caching). I started out with a single main navigation
menu, which was very comprehensive - but also very big (ito file
size). I was hoping to cache a part of the menu on the client-side
to reduce download times once the site visitor has downloaded the
first page in the site (where he enters the site is not
applicable). But that proved impossible (I think...).
I then followed some advice to break up my main navigation
menu, keep only the more important stuff in there and rather
distribute the lower levels of the main menu into their own
dedicated menus. From there the page linked above.
The main menu at the top is fine, no problem there. On the
left below the masthead I've created two menus, one above the other
(it displays as a single menu but the first menu ends above the
"Other tour lists" item). The first of these two menus contains the
bulk of the heavy navigation elements (±160kb of the total
page file size of 220kb). The div info that applies to this menu =
<div id="p7PMM_2" class="p7PMMv06">. I'd love to cache this
menu, either in full or the bulk thereof, on the client-side. That
is implement a client-side include. When a visitor first enters our
site the include file with the 160kb (secondary) menu gets
downloaded together with CSS stylesheets, etc. When the visitor
links through to a following page in our site, his machine
(client-side) dishes up the menu to that next page without having
to download it from our hosting server a second time.
Is this possible and how? Any and all suggestions will be
appreciated!
Our clients are mostly wealthy and thus probably (virtually)
all have high-speed broadband connections. I seriously doubt that
any of them are running dial-up connections. Thus this issue is not
going to sink our site. But I'd love to cut page file size if
possible.
Furthermore, I'm not too worried about the small portion of
visitors that may have their javascript disabled in their browsers.
The main navigation menu at the top of the page will still allow
them to navigate the site. Much the same goes for SEO.
I've tried one or two CSI javascripts and succeeded in
actually getting the relevant tags and contents inserted in the
html document, but the javascript would then 'break'. That is all
the coding and menu contents would be there, but the javascript
won't function (menu's won't pop / fly-out). I'm a little clueless
when it comes to Javascript, and many other things :-), but I
suspect that the Javascript in the include file does not get
called. If the Javascript is kept in the html file, the menu
content (elements) in the include file arrives in the html file
after the relevant script has been called and doesn't get
rendered??
Once again any help / suggestions will be appreciated!

Answer 1

> But that proved impossible (I
> think...).
Even without doing anything on your part, the images, the
CSS, and the
javascript is already cached client-side. You cannot cache
any of the
structural code client-side.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"afrilux" <[email protected]> wrote in
message
news:[email protected]...
> Hi there.
>
> The following page refers:
http://www.afrilux.co.za/test/1/dev2.htm
>
> The linked page is in fact a DW CS3 tmp preview file,
for that reason the
> CSS
> has been pulled into the html file by DW, it won't look
that way in the
> eventual page file.
>
> After lengthy battles with the Spry Horizontal menu, I
eventually resorted
> to
> Pop Menu Magic 2 (PPM2) to generate menus. I'm very
happy with the product
> (I'm
> not looking for PPM2 support, but rather support
pertaining to CSS-driven
> menu's in general relating to caching). I started out
with a single main
> navigation menu, which was very comprehensive - but also
very big (ito
> file
> size). I was hoping to cache a part of the menu on the
client-side to
> reduce
> download times once the site visitor has downloaded the
first page in the
> site
> (where he enters the site is not applicable). But that
proved impossible
> (I
> think...).
>
> I then followed some advice to break up my main
navigation menu, keep only
> the
> more important stuff in there and rather distribute the
lower levels of
> the
> main menu into their own dedicated menus. From there the
page linked
> above.
>
> The main menu at the top is fine, no problem there. On
the left below the
> masthead I've created two menus, one above the other (it
displays as a
> single
> menu but the first menu ends above the "Other tour
lists" item). The first
> of
> these two menus contains the bulk of the heavy
navigation elements (?160kb
> of
> the total page file size of 220kb). The div info that
applies to this menu
> =
> <div id="p7PMM_2" class="p7PMMv06">. I'd love to
cache this menu, either
> in
> full or the bulk thereof, on the client-side. That is
implement a
> client-side
> include. When a visitor first enters our site the
include file with the
> 160kb
> (secondary) menu gets downloaded together with CSS
stylesheets, etc. When
> the
> visitor links through to a following page in our site,
his machine
> (client-side) dishes up the menu to that next page
without having to
> download
> it from our hosting server a second time.
>
> Is this possible and how? Any and all suggestions will
be appreciated!
>
> Our clients are mostly wealthy and thus probably
(virtually) all have
> high-speed broadband connections. I seriously doubt that
any of them are
> running dial-up connections. Thus this issue is not
going to sink our
> site. But
> I'd love to cut page file size if possible.
>
> Furthermore, I'm not too worried about the small portion
of visitors that
> may
> have their javascript disabled in their browsers. The
main navigation menu
> at
> the top of the page will still allow them to navigate
the site. Much the
> same
> goes for SEO.
>
> I've tried one or two CSI javascripts and succeeded in
actually getting
> the
> relevant tags and contents inserted in the html
document, but the
> javascript
> would then 'break'. That is all the coding and menu
contents would be
> there,
> but the javascript won't function (menu's won't pop /
fly-out). I'm a
> little
> clueless when it comes to Javascript, and many other
things :-), but I
> suspect
> that the Javascript in the include file does not get
called. If the
> Javascript
> is kept in the html file, the menu content (elements) in
the include file
> arrives in the html file after the relevant script has
been called and
> doesn't
> get rendered??
>
> Once again any help / suggestions will be appreciated!
>
>